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…
Skill Claude Code
Resolve a workflow's declared Required Inputs by checking existing project context first, then asking about only the inputs that remain unresolved — one question at a time, with a recommended answer, before the invoking workflow proceeds. Referenced by name from other skills' input validation steps (most of SpecFlow's…
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: