Claude Skills by MaxFabian25

Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

A relentless interview to sharpen a plan or design.

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.

Configure AGENTS.md and docs/agents. Use when this engineering skill pack lacks repo setup.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Teach the user a new skill or concept, within this workspace.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Move issues through a state machine of triage roles — categorise, reproduce, grill if needed, and write agent-ready briefs.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.