mikestangdevs

mikestangdevs/craft-skills

Plugin Claude Code

Plugin marketplace listing 1 plugin: craft-skills.

mikestangdevs/craft-skills

Plugin Claude Code

Skills for code you'll have to live with. Two collections: craft (code that's understandable, named well, lean, loud about failure, and testable — without turning every edit into a rewrite) and rigor (claims you can believe — adversarial testing, full-suite banking, cited numbers, population sweeps, evidence-backed…

mikestangdevs/craft-skills

Instructions file

Instructions for mikestangdevs/craft-skills, covering claude.md, what this repo is, commands, architecture and bucket organization & governance.

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use when touching an existing file to make a change, so you leave it slightly cleaner than you found it without derailing into a giant refactor. Identifies small, safe, in-scope improvements adjacent to the change you're already making — a better name, a deleted dead line, an extracted helper, a clarified condition …

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use when a codebase feels heavy, when you suspect dead code, or before adding a feature to an area that's already cluttered. Finds and safely removes code that no longer earns its place — dead branches, unused exports, commented-out blocks, abandoned feature flags, speculative abstractions used once, and TODOs from a…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use before trusting, merging, or building on top of code you (or an agent) just wrote or are about to change. The agent explains the code back in plain language — what it does, why it exists, what breaks if it's wrong — and refuses to proceed until the mental model is confirmed. Use when a diff looks fine but nobody…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use before writing new code into an existing codebase — a new function, file, test, or feature in a repo that already has its own idioms. Reads the surrounding code first and matches its patterns (error style, test layout, naming casing, import conventions, file structure) instead of importing a generic house style.…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use when you spot a swallowed, vague, or context-losing error — an empty catch, a bare except: pass, catch (e) { console.log(e) } that then continues, throw new Error("something went wrong"), an error logged then ignored, or a caught exception that drops its cause. Makes failures loud and specific: each error says…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use when naming or renaming functions, variables, types, files, or modules — or when a code review keeps stumbling over confusing names. Forces names to reveal intent and role, kills generic names (data, handle, process, manager, util), and aligns vocabulary with the domain. Use when reading code feels harder than it…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use when you want to unit-test logic but can't without a database, network, clock, or a pile of mocks — or when a function fetches, computes, branches on policy, and writes all in one breath. Splits the decision (pure logic) from the action (I/O and side effects) along the natural seam, so the logic becomes testable…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use when a file is littered with comments that narrate what the code already says (// increment the counter), when load-bearing code has no explanation of why it exists, or when reviewing AI-generated code (agents pad output with narration and never record the why). Deletes comments that restate the code, keeps and…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use after completing any unit of work in a repo that has a real test suite — before starting the next task, compacting context, or declaring done. Runs the FULL suite (not just the tests near the change), in the background and parallelized when it's slow, and 'banks' a green state: honest pass/fail counts…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use before any context boundary — a context compaction, the end of a long session, a handoff to another agent or a future session — on multi-session work. Writes the resume state DOWN, outside the conversation: a working doc with what's done, what's in flight, the numbered remaining tasks in order, the standing…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use immediately after fixing a bug or improving a pattern in one place — before reporting done. Asks the question agents never ask themselves: 'did you do that anywhere else?' Enumerates the full population of sibling sites (other templates, scenarios, endpoints, components, fixtures, configs that share the same…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use the moment a real bug is found during any task — an audit, a review, a test wave, unrelated feature work — and the temptation appears to document it and move on. Defaults to fixing confirmed bugs in the current pass: a found bug is work surfaced, not work deferred. If a fix genuinely can't happen now (out of…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use whenever code contains a numeric constant, threshold, default, rate, capacity, tolerance, or coefficient — especially one the agent just introduced. Enforces the rule: every number is either derived (from real data or first principles, traceably) or cited (to a spec, datasheet, standard, or documented decision) …

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use at every 'are we ready?' moment — before declaring a task done, shipping, demoing, advancing to the next phase, or answering 'so everything works and we're good?'. Replaces vibes-based confidence ('should work now', 'looks good') with an explicit, evidence-backed go/no-go: what was verified and how, what was NOT…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use whenever code produces an output someone will read — a report, a metric, a chart, a calculation result, a dashboard value — and especially when a result is surprising, suspiciously clean, or just changed a lot. Treats every implausible number as guilty until root-caused: all-zeros, -0, a value at 1858% of its…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Use after building any feature, model, or fix that the team has to trust — before calling it done. Replaces smoke tests and tests-written-to-pass with an adversarial test wave: tests designed to BREAK the thing (invariants, conservation laws, edge regimes, reference cross-checks, hostile inputs), where findings are…

mikestangdevs/craft-skills

Skill Claude CodeCodex

Run once per repository to get the most out of the other craft skills (explain-back, name-things, delete-this, seams, loud-errors, boyscout, why-comments, fit-in). Scaffolds an optional shared CONTEXT.md — domain glossary, language/stack, conventions, and untouchables — that those skills read to match your project's…