Skill Claude Code
Use 100 to establish or refresh domain knowledge before project planning or feature design. Trigger it for prompts like "100", "domain knowledge", "domain research", "industry context", or when the project needs research-backed understanding of users, workflows, terminology, regulations, or differentiators.
Skill Claude CodeCodex
Use 101 to define the project's core product framing: problem, users, differentiation, and success criteria. Trigger it for prompts like "101", "project overview", "create project overview", or when a new product idea needs a structured foundation before architecture or feature work.
Skill Claude CodeCodex
Use 102 to define the system architecture, stack, major components, and testing approach. Trigger it for prompts like "102", "system architecture", "architecture doc", or "define the tech stack" when the project is ready for foundational technical decisions.
Skill Claude CodeCodex
Use 103 to define the conceptual data model: entities, relationships, and business rules. Trigger it for prompts like "103", "data model", "conceptual data model", "entity relationships", or when the team needs a shared domain model before implementation choices.
Skill Claude CodeCodex
Use 103.5 to define the conceptual data model as GraphQL SDL instead of markdown tables — entities, relationships, business rules, access rules, and data quality rules captured in a documentation-only schema that doubles as diagram source for an interactive visualizer. Trigger it for prompts like "103.5", "graphql…
Skill Claude CodeCodex
Use 104 to define the backend architecture, including API structure, service layering, data access, and security patterns. Trigger it for prompts like "104", "backend architecture", "API design", or "service layer" when backend patterns need to be specified before coding.
Skill Claude CodeCodex
Use 105 to define the frontend architecture: UI structure, component boundaries, state, and development patterns. Trigger it for prompts like "105", "frontend architecture", "component structure", or "state management" when frontend patterns need to be specified before UI design.
Skill Claude CodeCodex
Use 106 to establish the visual design system and UI strategy for a project. It covers the design philosophy, color system, typography, layout principles, and component visual language. Trigger it for prompts like "106", "ui design", "design system", "visual design", or "color palette" when the project needs a…
Skill Claude CodeCodex
Use 107 to define the UX architecture: navigation, interaction patterns, accessibility, error handling, and the page inventory. Trigger it for prompts like "107", "user experience", "navigation design", "interaction patterns", or "information architecture" before per-page design work begins.
Skill Claude Code
Use 108 to design a specific page or view in detail, including layout, mockup, interactions, and responsive behavior. Trigger it for prompts like "108", "page design", "wireframe", or "design the [page] page" when a single route or view needs a detailed design spec.
Skill Claude CodeCodex
Use 110 to define and prioritize the product's feature set as concise, reviewable slices. Trigger it for prompts like "110", "feature overview", "feature list", "feature backlog", or "what features should we build" after the main project framing is in place.
Skill Claude Code
Use 201 to create a concise high-level design for a specific feature. It produces the feature overview and end-to-end user journey without going into test or implementation detail. Trigger it for prompts like "201", "high-level design", "feature design", or "HLD" when a feature needs a short overview before specs or…
Skill Claude Code
Use 202 to write Gherkin behavior scenarios for a feature. It produces a structured specs.feature file with coverage sized to the task. Trigger it for prompts like "202", "test spec", "gherkin", "BDD scenarios", or "write specs" when the next step is defining behavior to test.
Skill Claude Code
Use 203 to produce a codebase-grounded implementation plan for a feature. It maps the needed file changes and explains how the implementation should fit the existing code. Trigger it for prompts like "203", "implementation design", "technical design", or "how do I build this" when overview and spec artifacts already…
Skill Claude Code
Use 204 to validate a feature's design artifacts before implementation begins. It reviews overview.md, specs.feature, and implementation.md for gaps, inconsistencies, and missed reuse. Trigger it for prompts like "204", "validate the feature", or "implementation readiness review" before coding starts.
Skill Claude Code
Use 301 to implement a substantial change through the main SpecFlow spec-driven workflow. It handles preparation, tests-first implementation, separate cleanup passes, and final validation. Trigger it for prompts like "301", "spec implementation", or "implement this feature" when the work is large enough to benefit…
Skill Claude Code
Use 302 to add or repair automated tests for behavior that already exists. Choose it when the missing work is test coverage, not broad production-code changes. Trigger it for prompts like "302", "test-only implementation", "write the tests", or "add E2E coverage".
Skill Claude Code
Use 401 to clean up an already-changed source scope or test scope without turning it into a broad rewrite. Trigger it for prompts like "401", "cleanup this change", "refactor the touched files", or "tidy the tests", and run it separately for source and test cleanup.
Skill Claude Code
Use 402 to investigate and correct a failing automated test by deciding whether the right fix is in the test, in production code, or in the expected behavior itself. Trigger it for prompts like "402", "fix this failing test", "is this a test issue or a product bug", or "triage the failing spec".
Skill Claude Code
Use 501 to explore a live site with a real, visible Chrome browser and log defects the way a QA analyst would: click through flows, judge what happens against what a reasonable user would expect, and record anything broken or unintuitive with clear repro steps. Trigger it for prompts like "501", "browser QA", "QA…
Skill Claude Code
Use 502 to work through the D11 exploratory defect backlog: for each targeted Active entry, dispatch it to 402-test-correction for reproduction, classification, and a real fix, update the entry's status from the outcome, commit the change, and finish by compacting the resolved history. Trigger it for prompts like…
Skill Claude Code
Use 900 to run a bounded review/apply-fix convergence cycle around a piece of work that already happened. It runs the Review and Apply-Fix roles in separate, isolated subagent contexts and repeats them until Review returns a clean verdict or a safety cap is hit. Trigger it for prompts like "900", "feedback loop"…
Skill Claude Code
Use 901 to run one feature end-to-end through SpecFlow's full pipeline as a single git-tracked run: high-level design, happy-path specs, scenario-by-scenario test-driven build-out validated and committed per module, cleanup, an optional expanded-coverage round, and a merge back to the base branch. Every design/spec…
Skill Claude Code
Create or refresh CLAUDE.md guidance — Claude Code's native project-memory file — so Claude can navigate a repository safely. Adds nested CLAUDE.md overlays or path-scoped .claude/rules/ only where a subtree or file pattern genuinely differs. Trigger it when project guidance is missing, stale, or needs local…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: