Produce module-level implementation plans for a NEW feature or application — markdown plan files in a per-feature folder, never code. Takes a free prompt, a *.md file, or a folder of *.md docs; cross-checks project docs against each other and against the code…
Produce module-level update plans for changing an existing feature or adding features to an existing system — markdown plan files, never code. Reuses plan-feat's discipline and adds what change requires: current-state reconnaissance, impact analysis with a…
End-to-end bug fix workflow, root cause first. Given a bug description, an error message, or a pasted stack trace, generates at least 3 distinct hypotheses for the cause before picking one (anchoring-bias gate), gathers evidence per hypothesis via the…
Generate an empty, strongly-typed code architecture (no implementation), with minimal comments that document behavior and relationships between modules.
Daily micro-refactoring. Each round is one small, behavior-preserving diff that raises code quality — deleting dead code, merging duplication into one generic helper, flattening control flow, purifying functions, fixing error paths, uniformizing names,…
Structured naming convention system for code identifiers. Use when naming or renaming variables, functions, methods, classes, files, DB tables/columns, routes, or CSS classes; when validating identifiers against a convention; or when the user mentions naming,…