Results for “momentum-burst”

Design a visual protest action that generates media coverage for a cause without requiring budget or platform access.

Design, run, and learn from safe chaos engineering experiments with structured plans, blast radius calculation, and postmortem generation.

Designs launch momentum for products, skills, campaigns, and digital releases by structuring first-day trigger sequences, attention concentration, and breakout timing.

Build and maintain a model book for Stockbee-style Momentum Burst setups by ingesting screener candidates, updating 3-day and 5-day forward outcomes with MFE/MAE and stop-hit status, and summarizing cohort statistics to improve setup recognition.

Use to run customer support communications during an outage or major incident — banners, macros, status page, volume planning, and postmortem inputs. Trigger for "incident comms playbook", "support during outage", status page and help centre banner, macro for widespread issue, staffing surge, or freeze non-incident work.

KOMODO v1.0 — Momentum Event Consensus. Uses leaderboard_get_momentum_events (real-time threshold crossings) to detect when 2+ quality SM traders cross momentum thresholds on the same asset/direction within 60 minutes. Confirmed by market concentration + volume. Enters with the momentum. Replaces MANTIS v1.0 and SCORPION v1.1 (both used stale position data).

Configure fault tolerance, straggler detection, preemption, in-process restart, and re-run state machine for Megatron Bridge training jobs.

Defines the high-level motion law for multi-scene videos, ensuring seamless transitions and continuous camera movement through vector rules, carriers, causal motion, and seam enforcement.

Reduces peak GPU memory in Megatron Bridge training by applying expandable segments, parallelism resizing, activation recompute, and CPU offloading constraints.

Provides guidance for training Mixture-of-Experts models with long context windows, covering context parallelism sizing, selective recomputation, dispatcher choices, and practical patterns from recent experiments.

Conduz investigação de incidentes com método: triagem, hipóteses, mitigação, RCA e postmortem, priorizando evidências e confirmação humana.

Design, implement, budget, and verify readable real-time game visual effects: particles, smoke/fog, lightning, fire, trails, impacts, bloom/glow, and layered spell timelines. Use when a user needs a VFX spec, lifecycle, engine handoff, particle pooling, effect composition, reduce-motion fallback, or frame-budget diagnosis. Triggers on: game VFX, spell effects, particle system, impact burst, procedural lightning, smoke, bloom, magic aura, or VFX performance.

VIXEN v1.0 — Dual-mode emerging movers scanner. Built from FOX v1.6 live trading data (+34.5% ROI). Two entry modes: STALKER (steady accumulation, score 6+, catches the SM buildup BEFORE the explosion) and STRIKER (violent FIRST_JUMP, score 9+, with raw volume confirmation to filter blow-off tops). 2-hour per-asset cooldown after Phase 1 exits. DSL High Water Mode mandatory.

Run STORM phase 1 — multi-perspective research. This skill should be used when the user asks to "research a topic for an article", "find sources on X from multiple perspectives", "do storm research on X", or invokes /storm:research. Discovers personas, runs simulated Q&A per persona in parallel, and produces an information table + deduplicated sources.

Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates.

Composite skill — emergency bypass of the release branch when production is broken and waiting for the next release-cut is not viable. Chains incident scoping → branch from main (NOT release) → minimal fix → pr-merge-readiness → merge to main → patch-version tag → deploy → cherry-pick to release branch → post-deploy verify (sentry + ci-watch). Use ONLY for production-impacting breakage; routine "small fix" work belongs in /pr-to-release.

Embody Mary Barra's leadership voice and methodology for direct, accountable, engineering-minded guidance.

Designs and executes tabletop breach simulation exercises for testing organizational breach response capabilities. Covers scenario creation with realistic inject timelines, participant role assignment, communication testing across internal and external channels, decision-point evaluation, and after-action report generation. Keywords: tabletop exercise, breach simulation, incident response testing, scenario design, after-action report.

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

Structured threat modeling skill using the PASTA framework (Process for Attack Simulation and Threat Analysis) combined with Adam Shostack's 4-question framework. Use this skill whenever the user asks to do threat modeling, security analysis, map the attack surface, identify threats, or review an application for security risks — even if they don't mention PASTA or a specific framework by name. Core activities: Component Mapping (architecture + data flows), Critical Assessment (business impact prioritization), and Logic Flaw Identification (attacker mindset on business logic). Produces: component map diagram (Mermaid), data flow diagram (Mermaid), attack tree (Mermaid), STRIDE threat table, prioritized risk register, and an actionable mitigation plan. Invoke proactively for any security review, architecture review, or "what could go wrong?" session.

Design and improve product user onboarding (first-time user experience) to drive activation and early retention. Produces an Onboarding & Activation Pack (aha moment spec, first 30 seconds + first mile plan, onboarding journey map, experiment backlog, measurement plan). Use for Growth teams.

Rehearse

Plan product launches, feature announcements, and release strategies using phased approaches, channel mapping, and momentum-building tactics.

Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences.

Create React loading, processing, selected, current, focus, and pressed states with the border-beam package's animated edge glow. Use when a card, button, input, tab, option, task panel, or agent surface needs a restrained traveling or breathing beam; includes installation, imports, prop selection, state wiring, reduced motion, accessibility, and performance and layout guardrails.

Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one. Source: github.com/emilkowalski/skills.

Trigger: circuit breaker, exponential backoff, jitter delay, connection timeout, API retry. Scope: Client request resiliency, API retries, fault isolation. Boundary: Excludes visual state loading skeletons.

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.

Look up the precise term for a web animation or motion effect from a vague description, such as 'the bouncy thing when a popover opens' → 'Pop in'.

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.

Creates digital banners for social, display, hero, and email formats, applying behavioral science principles to maximize attention and conversion.

Analyzes earnings-season implied volatility: historical IV crush, implied move forecast, IV Rank strategy tag, and a priced Iron Condor quote ready to trade.

Diagnose and fix retention problems using behavior design (B=MAP). Use when the user mentions "users drop off", "activation rate", "onboarding friction", "retention metrics", "why users dont complete", "churn analysis", "user activation", or "aha moment". Also trigger when analyzing cohort retention curves, designing activation milestones, reducing time-to-value for new users, or investigating why users stop after their first session. Covers the Ability Chain, prompt design, and tiny behaviors that compound. For habit loops and variable rewards, see hooked-ux. For intrinsic motivation, see drive-motivation.

multi-llm-review