From wf-rituals
Red/green/refactor for a single acceptance criterion or feature unit, ending with a hard-rule branch-coverage audit. Write a failing test, write the minimum code to pass, refactor, then walk every reachable conditional branch and confirm an explicit test exercises it. Use during milestone implementation and inside `wf-patch` when the change touches logic.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wf-rituals:wf-tdd-cycleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A single iteration of test-first development for one acceptance criterion or one focused feature unit. Ends with a branch-coverage audit that is a **hard rule**, not a guideline.
A single iteration of test-first development for one acceptance criterion or one focused feature unit. Ends with a branch-coverage audit that is a hard rule, not a guideline.
wf-patch branch and the change touches logic (not pure config / dependency bumps).If you find yourself running wf-tdd-cycle for a config nudge, you don't need it.
MethodName_Scenario_ExpectedResult (or the language-idiomatic equivalent).Before declaring this cycle complete, you walk every reachable conditional branch in the diff and confirm an explicit test exercises each side. Saying "every branch covered" without performing the audit is the failure mode this rule exists to prevent.
if/else/switch/case/catch/?:/early-return/short-circuit, identify which test exercises each side.internal + InternalsVisibleTo, Rust pub(crate), Python _internal + explicit import, Java/Go package-private). Then write a direct test.null check on a value the type system guarantees non-null) are documented where the project records such things. Include the reason.A branch is reachable if any caller of the function — direct or transitive — can produce inputs that select it. The compiler can't prove unreachability for most defensive code. Default to reachable; require a written reason to call something unreachable.
Before declaring done, every new test passes:
wf-patch) is about to ask "commit?", the audit must already be complete.Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub 23min/ai-workflow-rituals --plugin wf-rituals