Results for “stage-router”

Start or patch Dynamo router modes and run router endpoint smoke checks for round-robin, KV-aware, least-loaded, or device-aware routing.

Provides Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.

Create stage plots for live performances. TRIGGERS - Use when user needs help with stage-plot related tasks.

Create stage plots for live performances. TRIGGERS - Use when user needs help with stage-plot related tasks.

Routes ambiguous multi-stage UI work across research, concept, Figma, implementation, and QA. Do not use for a clear leaf task.

Route a task description to the right processkit skill, project-specific process override, and MCP tool in a single deterministic call — use this at the start of every processkit domain task.

Startup skill router: maps any incoming request to the correct skill using Quick Lookup table and _manifest.json. Loaded automatically at session start. Triggers on: every new request — this is the dispatch layer, not a user-facing skill. NOT for: executing tasks directly — always routes to a domain-specific skill.

Use when the user is unsure which skill to use or where to start. Interviews the user with targeted questions and recommends the best skill(s) from the installed library for their goal.

Next.js App Router — Agent Arena Patterns

Navigate and route in Expo Router apps using file-based routes, groups, dynamic routes, Link with previews and context menus, native Stack, modals, form sheets, NativeTabs, headers, toolbars, and search bars.

Orchestrates the full-site migration preparation cascade — inventory crawl, page-type and module catalog confirmation, archetype prototyping, and asset preparation — with confirmation gates between phases.

Build beautiful, native-feeling Expo screens with Apple HIG styling, semantic colors, native controls, SF Symbols, media, animations, visual effects, gradients, storage, and responsive layout.

Coordinate multi-stage edge research pipelines from candidate detection through strategy design, review, revision, and export.

Routes qualified leads to the right team member or sequence based on score, segment, and source. Applies configurable routing rules to assign leads to founder direct, SDR sequences, or nurture campaigns.

Route a task to the most fitting skill or agent. Parses user intent, checks installed-skill inventory, and picks the best match (single skill or chain).

Guides building Expo Router navigation with file-based routing, layouts, tabs, protected routes, and deep linking.

Intent-based router and play composer for youtube-ops skills — classifies what the user needs and recommends a single skill or queues a multi-step play for $exec

Routes app-store optimization requests to the right specialist skill, loading up to three matching skills and asking one clarifying question when intent is ambiguous.

Provides best practices for Vue Router 4, including navigation guards, route params, and route-component lifecycle interactions.

Routes founder questions to the right advisor roles, coordinates multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions.

Router for the gstack skill suite. (gstack)

Flutter cross-platform development guide covering widget patterns, Riverpod/Bloc state management, GoRouter navigation, performance optimization, and platform-specific implementations. Includes const optimization, responsive layouts, testing strategies, and DevTools profiling. Use when: building Flutter apps, implementing state management (Riverpod/Bloc), setting up GoRouter navigation, creating custom widgets, optimizing performance, writing widget tests, cross-platform development.

Manage Heroku pipelines and review apps with stage-aware guardrails. Use when the agent needs to inspect or configure Heroku pipelines, connect apps to stages, promote slugs between stages, enable review apps, or reason about `app.json` behavior in Heroku review workflows.

Self-hosted AI gateway with one OpenAI-compatible endpoint for multi-provider LLM, embedding, image, and audio routing, automatic fallback, load balancing, and cost optimization.

Router for Google Stitch design-to-code in this pack. Use when starting any Stitch workflow, choosing Stitch vs Aura vs Figma vs Claude Design, or before calling generate/edit MCP tools. Enforces ~400 Stitch credits/day. Points to phased pack skills: enhance-prompt → generate-design → extract → build → loop.

Routes ambiguous review or planning to one leaf workflow. Do not use for a clear code, security, UI, architecture, or migration review.

Use to map support contacts onto the product lifecycle, interpret contact as a lifecycle signal, and avoid journey-map theatre. Trigger for "customer journey map support", "contact by lifecycle stage", onboarding support drivers, churn and support overlap, stage-specific contact reasons, or when journey mapping is worth doing.

Next.js App Router

Provides a reference for structuring an Expo Router app, including folder layout, configuration files, and essential dependencies.

Top-layer project orchestration skill for Nick's workflow. Use when a request involves multiple stages, skills, or deliverables and the work needs to stay aligned from idea to scope to design to schema to build to QA to deploy. Coordinates the right sequence, enforces stage gates, prevents drift and overbuilding, tracks status/blockers/next actions, and creates clear handoffs between strategist, design, schema, Supabase, build, QA, and launch work.

Routes ambiguous or multi-domain engineering requests to the smallest ordered skill set. Do not use for clear single-skill work or same-task follow-ups.

Game development orchestrator. Routes to platform-specific skills based on project needs.

AI-driven Game Development Studio (BMAD-GDS). Routes game projects through Pre-production, Design, Architecture, Production, and Game Testing phases using 6 specialized agents. Supports Unity, Unreal Engine, Godot, and custom engines.

Provides the shared STORM methodology, artifact layout, stage-gating contract, citation hygiene, and retrieval fallback. Use when executing any /storm:* skill (generate, research, outline, write, polish). Internal knowledge; never user-invocable.

Select alternative execution paths when a plan step fails — branch on outcomes instead of blind retry. Load when a structured plan step fails, an unexpected observation arrives, or the user asks what to try next after an error. Also triggers on "try another approach", "route around this failure", "replan on failure", "if X fails try Y", or outcome-based branching during multi-step work. Pairs with structured-planning and debug-and-fix. Does not replace root-cause debugging — adds plan-level path selection.