release-notes
[Git] Use when creating release notes from git history.
remotion
[User-Invoked] Use when you need create, update, or preview Remotion videos.
research
[Planning] Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.
review-architecture
[Code Quality] Use when reviewing architecture compliance for layers, messaging, service boundaries, CQRS, repos, and entity events.
review-changes
[Code Quality] Use when reviewing current changes, staged or unstaged diffs, or branch-to-branch diffs.
review-domain-entities
[DDD Quality] Use when you need to review domain entities and value objects for DDD design quality.
review-ui
[Code Quality] Use when reviewing UI/frontend changes for long-content overflow, responsive multi-screen layout, flex-vs-fixed sizing, z-index discipline, and SCSS/BEM styling quality.
scaffold
[Architecture] Use when scaffolding reusable OOP/SOLID project foundations before feature implementation.
scan-all
[Documentation] Use when you need orchestrate all reference doc scans in parallel.
scan-codebase-health
[Documentation] Use when you need to detect codebase health issues: unused exports, doc count-drift, orphan files, stale config references.
scan
[Documentation] Use when scanning the codebase to (re)generate ONE project-reference doc. Parameterized by `--target=<key>`: project-structure | backend-patterns | frontend-patterns | scss-styling | design-system | code-review-rules | domain-entities | feature-spec | docs-index | e2e-tests | integration-tests | seed-test-data | ui-system. Shared 4-phase scan engine; per-target detail lives in references/targets.md. `ui-system` is an orchestrator meta-target (`kind: orchestrator`) that runs the 3 UI child scans in parallel instead of the 4-phase engine.
scout
[Investigation] Use when quickly locating relevant files and affected areas across a large codebase.
security-review
[Code Quality] Use when you need to perform a security review or audit on any scope — application code (OWASP Top 10 2025), secrets exposure, dependency/supply-chain malware, third-party repository vetting before install, infrastructure/config, CI/CD pipeline, AI-agent risks, and host/VPS compromise detection.
seed-test-data
[Dev Data] Use when you need to implement or enhance test data seeders that simulate QC happy-path scenarios via application-layer commands.
sequential-thinking
[AI & Tools] Use when you need to apply structured, reflective problem-solving for complex tasks requiring multi-step analysis, revision capability, and hypothesis verification.
skill-creator
[Skill Management] Use when creating a new Claude Code skill, adding reference files or scripts to an existing skill, scanning/fixing invalid skill headers, or optimizing/packaging skills. Triggers on: create skill, new skill, add skill reference, add skill script, fix skill, validate skill, package skill.
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.
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-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
[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.
start-workflow
[Skill Management] Use when starting a detected workflow, initializing workflow state, or activating a workflow sequence.
story
[Project Management] Use when creating user stories from PBIs, slicing features, or breaking down requirements.
strategy-builder
[Content] Use when you need to build marketing strategy: positioning, channels, messaging, campaigns, budget, KPIs.
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.
sync-skills-shared-protocols
[Skill Management] Use when shared protocol checklists change and need propagation across skills.
tech-stack-research
[Architecture] Use when you need to research, analyze, and compare tech stack options as a solution architect.
test-ui
[Testing] Use when you need full-site QA audit (accessibility, performance, security, SEO) with visual reports.
test
[Testing] Use when you need to run tests locally and analyze the summary report.
threejs
[General] Use when building 3D web apps with ThreeJS and related WebGL or WebGPU examples.
ui-ux-pro-max
[Frontend] Use when designing beautiful or aesthetic interfaces with curated UI styles, palettes, fonts, charts, and stacks.
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.
watzup
[Utilities] Use when you need to review recent changes and wrap up the work.
web-design-guidelines
[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance, and UX best practices.
web-research
[Research] Use when starting a web research task — discover, gather, and triage candidate sources on a topic to feed deeper investigation.
webapp-testing
[Testing] Use when you need individual page/component testing with Python Playwright scripts.
why-review
[Code Quality] Use when reviewing rationale and change quality for plans, PBIs, commits, diffs, docs, specs, reports, or explicit artifacts.
workflow-big-feature
[Workflow] Use when activating the Big Feature workflow for large or ambiguous research-driven feature work.
workflow-bugfix
[Workflow] Use when activating the Bug Fix workflow for systematic debugging with root cause investigation, fix, and verification.
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-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-end
[Process] Use when you need to end the active workflow and clear state.
workflow-feature-spec
[Workflow] Use when activating the Business Feature Documentation workflow for 8-section tech-free feature docs.
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-greenfield-init
[Workflow] Use when activating the Greenfield Project Init workflow for full waterfall project inception from idea through implementation with integration testing.
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-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-refactor
[Workflow] Use when activating the Code Refactoring workflow for restructure and improve existing code without changing behavior.
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-review-changes
[Workflow] Use when activating the Review Current Changes workflow for review, fix, and re-review recursively until all issues resolved.
workflow-seed-test-data
[Workflow] Use when activating the Seed Test Data workflow for idempotent QC happy-path seeders.
Page 3 of 4 · 155 results