Claude Skills by TheMostlyGreat

Run comprehensive code audit for architecture, dead code, and test

Behavior-first feature development — use when building new

Use when the user wants to explore options, weigh approaches, or think through uncertainty before committing to a direction. Collaborative brainstorming and rubber ducking — divergence-first thinking partner.

Kill zombie dev servers and test processes. Use when ports are

Root cause debugging before fixes. Use when investigating bugs,

Extract tacit knowledge through non-obvious microquestions — things only the user knows that can't be found in code, docs, or research. Use when you're about to guess at intent, context, or constraints during SAFEWORD's understanding flow. Also use when user says 'ask me', 'what do you need to know', or when another skill (bdd, brainstorm, debug) needs user context before proceeding. Do NOT use for questions answerable by reading the codebase or searching the web.

Explore and debate options with fresh documentation and research before committing. Use when facing a real decision with multiple plausible approaches — library/framework choice, architecture call, API or schema design, algorithm selection, or any communication / strategy call where being wrong has cost. Enumerates relevant research domains, looks up current docs and evidence-based methods, weighs options on correctness and elegance, resists bloat. Do NOT use for divergent ideation (brainstor...

Run linters and formatters to fix code style issues. Use when

Deep code review with web research. Use when double-checking code

Improve code structure without changing behavior. Use when

Use when finishing spec.md before writing test-definitions.md, or

Use when completing a TDD step and wanting a quality check. Reviews test quality after RED, implementation correctness after GREEN, and scenario completeness after REFACTOR.

How to write good tests. Use when writing tests, improving test

**Purpose:** Context anchor to prevent LLM loops during complex work. Colocates all artifacts. **Creating a ticket:** Run `safeword ticket new <slug>` (optionally with `--type=patch|task|feature` and `--title="..."`). The CLI mints a 6-char Crockford Base32 ID, creates the folder atomically, and writes a starter ticket.md. **Do not scan the tickets directory and pick the next ID yourself** — that races between parallel sessions and silently collides across git branches. **Location:** `.safewo...

Verify ticket completion criteria — use when finishing a ticket,