Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Do NOT use once the cause is already established, or for adding new behaviour — that is implementation, not diagnosis.
Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Do NOT use once the cause is already established, or for adding new behaviour — that is implementation, not diagnosis.
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code. Do NOT use inside the subagent-driven-development loop, which runs its own per-task implement→review→fix cycle and supersedes this skill there.
Skill Claude CodeCodex
Use when you have a spec or requirements for a multi-step task, before touching code. Do NOT use to produce the spec itself (use brainstorming) or to execute a plan that already exists (use subagent-driven-development).
Skill Claude CodeCodex
Covers the skill-authoring rules specific to this repo and the empirical wording findings that general guidance does not contain — matching guidance form to failure type, micro-testing against a no-guidance control, and the plugin/marketplace conventions a skill must satisfy here. Use when creating, editing, or…
Plugin Claude Code
Positive writing system for durable written artifacts — READMEs, ADRs, PR descriptions, docs, runbooks. Reader-expectation prose, Diátaxis document jobs, plain-language structure.
Skill Claude CodeCodex
Use when writing or revising a durable written artifact — README, ADR, design doc, PR description, release notes, runbook, error message, user-facing docs. Gives a positive writing system (reader model, sentence positions, document jobs), not a ban-list. Do NOT use for conversational replies to the user (global…