Claude Code plugin installing the Fable Way working discipline: a Stop-hook calibration gate (done-claims must carry their evidence ledger), runner skills for scope/debug/review/verify/ship, and self-building per-project memory (.fable/). Built for Opus/Sonnet
Skill Claude CodeCodex
Use when behavior contradicts expectation — a bug, an unexplained error, a failing test, output that looks wrong, a fix that didn't hold — or when you're about to retry the same category of fix a second time, or work keeps failing or stalling. Also when the user says "debug this", "why is this happening", or "still…
Skill Claude CodeCodex
Use when a task carries real uncertainty — multi-step builds, debugging where the first theory may be wrong, research or analysis with claims to verify, anything touching data/APIs/files not yet opened, or work that will be handed off. Also when work keeps failing or stalling, before declaring anything done, or when…
Skill Claude CodeCodex
Use before trusting or shipping an answer, design, plan, analysis, or risky code change — when you are about to commit to it. Also when the user asks for a review, a red-team, a second opinion, or to check work adversarially. For pure code diffs, prefer a dedicated code-review command when the environment has one…
Skill Claude CodeCodex
Use at the start of a non-trivial task, or when the goal is fuzzy, the request is solution-shaped, or you cannot yet state in one sentence what "correct" will be checked against. Skip for trivial edits.
Skill Claude CodeCodex
Use when finishing a task — writing the final report or status, shipping a change, or handing off — to produce a calibrated done-claim and the docs that make the work reproducible by someone else.
Skill Claude CodeCodex
Use when the user asks for the fable status, overlay health, the calibration record, or what the method has been tracking in this workspace. Read-only report; changes nothing.
Skill Claude CodeCodex
Use when about to claim work is complete, fixed, passing, correct, or done — before committing, opening a PR, or moving to the next task. Also when a result looks good and you're tempted to move on, or a green signal came back suspiciously clean. If the environment ships a dedicated end-to-end verify skill for…