Results for “everhour”

Extended hours trading support for pre-market and after-hours sessions via Alpaca

Clerk webhooks for real-time events and data syncing. Verify with verifyWebhook from the framework-specific package. Handle user, session, organization, billing, and payment events. Build event-driven features like database sync, notifications, and integrations.

Debug local web or Electron apps interactively using a persistent Playwright session with js_repl, enabling fast iterative UI debugging and visual QA.

Build real-time streaming applications with the Azure Event Hubs SDK for Java, including sending and receiving events, batch processing, and production-ready event processors.

Detects outbound HTTP clients constructed without explicit timeouts in AEM Cloud Service code and applies mechanical fixes with CSO-aligned defaults to prevent request-thread pool saturation.

Routes Omniverse Realtime Viewer requests to focused reference documents and enforces architectural rules for building USD viewer applications.

Use this skill when the user asks about Hours of Service (HOS) rules under 49 CFR 395 — the 11-hour driving limit, 14-hour on-duty window, 60/70 hour rule, 30-minute break, 10-hour off-duty reset, 34-hour restart, sleeper berth provisions, split sleeper berth, short-haul exemption (150-air-mile), agricultural exemption, adverse driving conditions, ELD malfunction handling, personal conveyance, yard moves, or anything related to driver duty status. Cite specific 49 CFR 395 subsection. If the question involves a non-standard operation (passenger carrier, oilfield, agricultural, military), confirm which set of rules applies.

Restructure any response for an ADHD brain — TL;DR first, ELI16 clarity, short punchy steps, one clear next action, zero walls of text. Use this skill whenever the user says "elihadhd", "adhd mode", "tldr", "eli16", "eli5", "too long", "overwhelmed", "shorter", "just tell me what to do", "break this down", "snap it", "gauntlet", or shows signs of overwhelm (e.g. "wait what", "I'm lost", "too much"). Also use it when the user asks for the simple version, the quick version, or the punchy version of anything — explanations, plans, debugging help, docs, decisions. When in doubt about whether a response is too heavy, use this skill.

Use when implementing elixir functionality with production-grade patterns and safeguards.

Apply the Doherty Threshold to keep system response times under 400ms, maintaining user flow and perceived performance.

当需要系统性地提升工作专注度和生产力，实现高质量成果时

[OMX] Strict autonomous loop: $deep-interview -> $ralplan -> $ultragoal (+ $team if needed) -> $code-review -> $ultraqa

Expert real-time VFX artist specializing in particle systems, shader effects, and the invisible craft that makes games feel satisfying. Masters Niagara, VFX Graph, Godot GPU particles, and understands the AAA principles that make effects read clearly at 60fps. Use when "particle system, visual effects, vfx, particles, niagara, vfx graph, flipbook, sprite sheet, explosion effect, magic effect, trail effect, beam effect, dissolve, distortion, force field, hit effect, muzzle flash, impact effect, smoke particles, fire effect, soft particles, game juice, screen shake, particle overdraw, effect optimization, vfx, particles, effects, niagara, vfx-graph, game-juice, visual-effects, shaders, flipbook, trails, beams, explosions, optimization, gpu-particles" mentioned.

Use to design overnight and follow-the-sun support — coverage models, handoff quality and measuring what is lost between shifts. Trigger for "after-hours coverage", "follow the sun", overnight support design, night shift vs defer async, handoff packet, shift handover quality, global coverage gaps, or when customers reopen tickets after every handoff.

Mounts a fetch-native CopilotRuntime on any JS server, wires middleware, selects an AgentRunner, and integrates built-in or external agent frameworks.

Bundles a prompt with selected files into a one-shot request for another model, supporting API and browser engines with session reattachment.