knowledge-review
[Research] Use when you need to review knowledge artifacts for completeness, citation quality, confidence accuracy, and template compliance.
idea
[Project Management] Use when capturing new ideas, feature requests, or concepts for future refinement.
markdown-novel-viewer
[Content] Use when you need background HTTP server rendering markdown files with calm, book-like reading experience.
llm-council
[Decision Support] Use when pressure-testing irreversible, high-stakes decisions with adversarial AI advisors.
linter-setup
[Quality] Use when you need to research and configure code quality tooling for any tech stack — linters, formatters, static analysis, pre-commit hooks, and CI gates.
workflow-write-integration-test
[Workflow] Use when activating the Write Integration Tests workflow for spec-first integration test authoring. Also covers converting existing test specs into integration test code and verifying integration test stability (repeat-run verification).
workflow-visualize
[Workflow] Use when activating the Visual Diagram workflow for create visual excalidraw diagrams from codebase investigation or web research.
workflow-spec-to-pbi
[Workflow] Use when activating the Spec to PBI Backlog workflow to convert canonical tech-free Feature Specs into complete, prioritized, dependency-aware PBIs and stories.
workflow-spec-sync
[Workflow] Use when activating the Test Spec Update (Post-Change) workflow for update test specs and feature docs after code changes, bug fixes, or pr reviews.
workflow-seed-test-data
[Workflow] Use when activating the Seed Test Data workflow for idempotent QC happy-path seeders.
workflow-review-changes
[Workflow] Use when activating the Review Current Changes workflow for review, fix, and re-review recursively until all issues resolved.
workflow-research
[Workflow] Use when activating the Research & Synthesis workflow — research a topic via web sources, then synthesize per --output={synthesis|business-eval|marketing|course} (knowledge report, business evaluation, marketing strategy, or course material).
workflow-refactor
[Workflow] Use when activating the Code Refactoring workflow for restructure and improve existing code without changing behavior.
workflow-idea-to-spec
[Workflow] Use when activating the Idea-to-Spec workflow — turn a raw idea/vision/problem into ONE canonical (provisional) Feature Spec. STOPS at the reviewed spec; chain workflow-spec-to-pbi for a backlog. For code→spec use workflow-code-to-spec.
workflow-idea-to-pbi
[Workflow] Use when activating the Idea to PBI workflow for turning an idea — or a raw product vision/problem — into prioritized PBIs and stories (single-PBI deep mode, or multi-opportunity discovery mode).
workflow-greenfield-init
[Workflow] Use when activating the Greenfield Project Init workflow for full waterfall project inception from idea through implementation with integration testing.
workflow-feature
[Workflow] Use when activating the Feature Implementation workflow for implement a well-defined feature with investigation, planning, implementation, and review. Also covers TDD/test-first development and spec-driven feature implementation with test specs written before code.
workflow-feature-spec
[Workflow] Use when activating the Business Feature Documentation workflow for 8-section tech-free feature docs.
template-skill
[Category] Use when defining the standard skill description pattern.
architecture-design
[Architecture] Use when designing solution architecture across backend, frontend, deployment, monitoring, testing, and code quality.
business-evaluation
[Content] Use when you need to evaluate business idea viability: Business Model Canvas, financial projections, risk matrix, go-to-market, execution plan.
changelog
[Documentation] Use when you need to generate or update changelog entries.
claude-md-init
[Documentation] Use when you need initialize, update, or refactor CLAUDE markdown from project-config JSON and codebase scan results.
copywriting
[Content] Use when you need to create high-converting copy for marketing materials, social media, landing pages, email campaigns, and product descriptions.
course-builder
[Content] Use when you need to build structured learning/teaching course material with Bloom taxonomy objectives, modules, lessons, exercises, and assessments.
custom-agent
[AI & Tools] Use when you need create, verify, or enhance Claude Code custom agents (Claude Code custom agent files).
db-migrate
[DevOps] Use when you need to run or create database migrations.
debug-investigate
[Fix & Debug] Use when investigating a bug's root cause — reproduce the symptom, trace it end-to-start through the code, form and test hypotheses, and pinpoint the defect before any fix.
deep-research
[Research] Use when deeply researching top sources from web-research.
workflow-end
[Process] Use when you need to end the active workflow and clear state.
workflow-e2e
[Workflow] Use when activating the E2E testing workflow to generate, update, or maintain Playwright/E2E tests. Pick mode with --source={changes|recording|update-ui}.
workflow-code-to-spec
[Workflow] Use when activating code-to-spec development — author/maintain the single canonical Feature Spec FROM existing code, keeping spec, implementation, and tests synchronized. For idea→spec (no code yet) use workflow-idea-to-spec.
workflow-bugfix
[Workflow] Use when activating the Bug Fix workflow for systematic debugging with root cause investigation, fix, and verification.
workflow-big-feature
[Workflow] Use when activating the Big Feature workflow for large or ambiguous research-driven feature work.
web-research
[Research] Use when starting a web research task — discover, gather, and triage candidate sources on a topic to feed deeper investigation.
dependency
[Project Management] Use when you need to map and visualize feature dependencies between modules, services, and work items.
design-spec
[Project Management] Use when you need to create UI/UX design specifications from requirements, PBIs, or user stories. Use --mode=wireframe to convert hand-drawn/digital wireframes or UI sketches into structured specs.
understand
[Process] Use when the developer wants something explained — by default the current working tasks + changes in context, or whatever the prompt names (a plan, a subsystem, a decision, a concept, a bug). AI derives WHAT to explain from the prompt and ALWAYS delivers a detailed, one-way explanation of purpose (why it exists), how (the mechanics), and why-this-way (trade-offs/alternatives) — regardless of coding level. Never asks the user questions, never quizzes, never blocks.
threejs
[General] Use when building 3D web apps with ThreeJS and related WebGL or WebGPU examples.
tech-stack-research
[Architecture] Use when you need to research, analyze, and compare tech stack options as a solution architect.
sync-skills-shared-protocols
[Skill Management] Use when shared protocol checklists change and need propagation across skills.
sync-codex
[Codex] Use when you need to run the full Codex mirror sync + verify pipeline (migrate → hooks → context → verify) standalone, no npm/package JSON needed.
design
[Design] Create or describe a UI design — quick (fast), immersive (good), or recreated/described from a screenshot or video. Dispatch via --mode={fast|good|describe|screenshot|video} (default fast).
strategy-builder
[Content] Use when you need to build marketing strategy: positioning, channels, messaging, campaigns, budget, KPIs.
story
[Project Management] Use when creating user stories from PBIs, slicing features, or breaking down requirements.
start-workflow
[Skill Management] Use when starting a detected workflow, initializing workflow state, or activating a workflow sequence.
spec
[Documentation] Use to author, audit, amend, or test-spec a business Feature Spec. The single spec skill — modes draft|init|update|audit|amend create/maintain the tech-free 8-section Feature Spec; draft authors a provisional spec from an idea/requirement (no code yet, Evidence: TBD); tests generates Section 8 TC-{FEATURE}-{NNN} test specifications; sync reconciles §8 TCs ↔ integration test code. Per-mode procedure lives in references/{author,tests,sync}.md.
spec-index
[General] Use when you need to (re)generate a DERIVED navigation index, cross-capability ERD, or reimplementation guide assembled FROM the canonical Feature Specs under docs/specs/**. Never extracts a separate A-E engineering tree.
spec-discovery
[Investigation] Use when about to author a new Feature Spec from an idea — investigate all existing Feature Specs AND related code logic first to surface related/overlapping/affected specs, missing features, missing test cases/user stories, system unknowns, and the invariant landscape, before any spec is drafted.
spec-clarify
[Code Quality] Use to validate a spec artifact's decisions with the user across three contexts — a freshly-authored Feature Spec (idea-to-spec), an existing canonical spec before PBI decomposition (spec-to-pbi), or a refined idea + §8 test-specs (idea-to-pbi deep mode). Detects the context, walks every applicable validation category, and runs an exhaustive but budget-bounded blocking clarification gate so every non-obvious or conflicting decision is confirmed before the artifact drives downstream work.
Page 1206 of 1717 · 85836 results
