Skill Claude Code
Create or update a project-local skill that lets agents drive and inspect a running interface. Use when an agent cannot directly verify changed app behavior, or when an existing verify skill may have drifted from the app.
Skill Claude CodeCodex
Explain why existing code or design has its current shape. Use for design rationale, tradeoffs, historical constraints, thresholds, and regressions tied to earlier decisions.
Skill Claude CodeCodex
Write or edit natural prose for emails, docs, proposals, PR descriptions, reviews, and messages. Remove generic AI phrasing while preserving meaning and audience fit.
Skill Claude CodeCodex
Create or update architecture decision records. Use when an important technical decision is made, changed, or needs recording after the fact.
Skill Claude Code
Audit existing code across every review dimension. Use for a read-only sweep of a project or path already on the default branch.
Skill Claude CodeCodex
Design or change a database schema. Use when adding or altering tables, columns, views, access rules, database functions, or migrations.
Skill Claude CodeCodex
Review a consequential call through an independent read from a different model. Use before a decision that is expensive to reverse, or before a document asserts facts.
Skill Claude CodeCodex
Create or update a skill in this repo, matching its conventions. Use when authoring a new skill or amending an existing one.
Skill Claude CodeCodex
Write tests that catch a named bug and are proven able to fail. Use when adding tests to existing code, pinning behavior before a refactor, or closing a gap a review or audit named.
Skill Claude CodeCodex
Write code whose types tell the truth — parsed boundaries, one empty value, exhaustive closed sets, coded errors — in the owner's stack for each language. Use when writing, changing or reviewing TypeScript, Rust, Python, Dart or shell, starting a project, or choosing a library.
Skill Claude Code
Review code against the owner's design rules and say directly what is wrong and what it should be instead; for a whole module, trace its bugs to the design that causes them and propose the smallest redesign, cuts first. Use on files, a diff or a module before accepting it, and instead of fixing a module's bugs one by…
Skill Claude Code
Run a refactor or a rewrite the owner's way — choose which the problem needs, then carry it out so the new design copies nothing from the old. Use when a module's design is wrong, after a design review proposes a redesign, or before a feature the current structure makes hard.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: