reframe
25Skill Claude CodeCodex
Restate the problem off its forced framing. Use when a framing feels forced and every option inside it loses.
Skill Claude CodeCodex
Restate the problem off its forced framing. Use when a framing feels forced and every option inside it loses.
Skill Claude CodeCodex
Spawn agents and verify their output — route work, never do it. Use when the work splits into pieces agents can carry and the session should route and check, not execute.
Skill Claude CodeCodex
Decide the technical path once the ask is clear. Use when the WHAT is confirmed but more than one way to build it remains — architecture, technology, design.
Skill Claude CodeCodex
Restate the problem in a distant domain's terms. Use when a problem circles inside its own vocabulary.
Skill Claude CodeCodex
Define how unsupervised work is judged before it runs. Use when work will run without a human watching, optimizing toward something.
Skill Claude CodeCodex
Assemble cases from context, induce the widest sound rule. Use when a real case shows a class no rule yet decides, or a rule decides only the cases it came from.
Plugin Claude Code
A grab bag of hunches — experimental skills and plugin features tried here before they earn a place in hope or sound. Everything graduates or dies.
Skill Claude CodeCodex
Drop the jargon and speak plainly, from this message on.
Skill Claude CodeCodex
Shape output for a human working through agents. Use on every response, out to and including casual conversation, even when the user did not ask for brevity.
Skill Claude CodeCodex
Use when the user asks to explain or understand a code change, diff, branch, or PR — or to catch up on a change an agent built before reviewing or shipping it.
Skill Claude CodeCodex
Use when the user wants knowledge delivered to an audience — slides, a deck, a diagram, an explainer for others, teaching or talk material — or shares existing content that isn't getting through.
Skill Claude CodeCodex
Use when writing prose a human will read — docs, READMEs, PR descriptions, commit messages, code comments, chat replies, explanations. Not for code, identifiers, API names, error strings, or established technical terms.
Skill Claude CodeCodex
Grind on one goal concurrently in a Solo workspace.
Skill Claude CodeCodex
Use when the user wants to understand a system by interacting with it themselves — asks for a debugger, visualizer, simulator, stepper, playground, or command center as an aid to their own understanding — or when reading and explanation haven't built intuition for how something behaves. Not for user-facing product…
Plugin Claude Code
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.
Skill Claude CodeCodex
Use in a repo that has sound taste rules installed (a .claude/sound/ directory), before writing or editing code — at the start of a coding task, and again when the work reaches a surface it was not planned to touch.
Skill Claude CodeCodex
Use when reviewing a staged diff or a commit range for soundness against the project's taste rules, including a pre-commit pass or an explicit "sound review".
Skill Claude CodeCodex
Use when installing or refreshing sound taste rules in a project — an explicit "sound setup", starting work in a repo with no .claude/sound/, or a taste-not-defined nudge. Also use to re-run after a stack change (new framework, new package in a monorepo).