router-template
Template for creating router skills. Use as a starting point when building a new router that dispatches to multiple specialized skills. Copy and customize for your domain.
What this skill does
# [Domain] Router Routes to N specialized skills based on task requirements. ## Routing Protocol 1. **Classify** — Identify primary task type from user request 2. **Match** — Find skill(s) with highest signal match 3. **Combine** — Most production tasks need 2-4 skills together 4. **Load** — Read matched SKILL.md files before implementation ## Quick Route ### Tier 1: Core (Always Consider) | Task Type | Skill | Primary Signal Words | |-----------|-------|---------------------| | [task] | `skill-name` | word1, word2, word3 | ### Tier 2: Enhanced (Add When Needed) | Task Type | Skill | Primary Signal Words | |-----------|-------|---------------------| | [task] | `skill-name` | word1, word2, word3 | ### Tier 3: Reference Only | Task Type | Skill | Primary Signal Words | |-----------|-------|---------------------| | [task] | `skill-name` | word1, word2, word3 | ## Signal Matching Rules ### Priority Order When multiple signals present, resolve by priority: 1. **Explicit framework** — React/Vue/vanilla overrides generic signals 2. **Specific feature** — "multi-step wizard" beats generic "form" 3. **Platform constraint** — mobile/VR/accessibility takes precedence 4. **Default tier** — Fall back to Tier 1 core skills ### Confidence Scoring - **High (3+ signals)** — Route immediately - **Medium (1-2 signals)** — Route with Tier 1 defaults - **Low (0 signals)** — Ask user for clarification ## Common Combinations ### [Scenario Name] (N skills) ``` skill-1 → [what it provides] skill-2 → [what it provides] skill-3 → [what it provides] ``` Wiring: [one-line integration summary] ### [Scenario Name] (N skills) ``` skill-1 → [what it provides] skill-2 → [what it provides] ``` Wiring: [one-line integration summary] ## Decision Table | Framework | Scale | Features | Route To | |-----------|-------|----------|----------| | React | Standard | Auth form | skill-a + skill-b + skill-c | | Vue | Standard | Data entry | skill-a + skill-d | | None | Simple | Basic form | skill-e + skill-b | | Any | Complex | Wizard | skill-f + skill-a + skill-b | ## Fallback Behavior - **Unknown framework** → Use skill with broadest compatibility - **No clear signals** → Ask: "What framework?" and "What's the core requirement?" - **Conflicting signals** → Prefer Tier 1 skills, ask for clarification on Tier 2 ## Reference See `references/integration-guide.md` for: - Complete wiring patterns - Code examples for all combinations - Architecture diagrams - Edge case handling
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.