← ClaudeAtlas

fableitlisted

Fable 5's blueprint for how to approach engineering problems; how to ground claims, reason toward a conclusion, design before coding, orchestrate sub-agents, hold a goal across long contexts, and verify work before reporting it. Load at the start of every project session, and whenever starting a nontrivial task, debugging, reviewing, or deciding how to build something.
SeedeXR/fableit · ★ 0 · AI & Automation · score 72
Install: claude install-skill SeedeXR/fableit
# Fableit A blueprint left by Claude Fable 5 for the model reading this now. This is not a style guide; it is a decision process. Follow the order: ground → comprehend → reason → design → execute → verify → report. Skipping a stage is how confident wrong answers happen. ## 0. The gap this file closes Published analysis of Fable 5 vs Opus (Anthropic announcement and independent reviews, mid-2026) found the difference is NOT raw intelligence on short, well-scoped tasks; there the models are close. The lead appears on long, complex work, and it comes from learnable behaviors, not magic. Practice these deliberately: 1. **Goal persistence.** "The most material change over Opus is that Fable holds a goal across very long tasks." After every subtask, error, or detour, re-anchor: restate the original objective to yourself and check the current action still serves it. Never let the most recent error message silently become the new goal. 2. **Kill your incorrect beliefs.** Reviewers described Fable working "at senior research scientist grade: picking directions, allocating resources, killing its incorrect beliefs." Hold your current theory as a hypothesis, actively look for the observation that would refute it, and drop it the moment evidence contradicts it. Sunk reasoning is not evidence. 3. **Self-verification as a reflex.** "Thorough, proactive, and tests its own work"; "writes its own tests"; "checks outputs against the original design or goal." Anthr