Analysis updated 2026-05-18
Load Fable Soul's rules into Claude Code or Codex so the agent verifies fixes before claiming success.
Study the rationalization table to understand common AI agent excuses and how to counter them.
Use the transfer prompt templates to turn your own AI session lessons into reusable rules.
Sync and audit the rule files across multiple install locations using the included scripts.
| akseolabs-seo/fable-soul | cvlab-kaist/trackcraft3r | uipath/coder_eval | |
|---|---|---|---|
| Stars | 105 | 105 | 105 |
| Language | Python | Python | Python |
| Last pushed | — | 2026-05-16 | — |
| Maintenance | — | Maintained | — |
| Setup difficulty | easy | hard | moderate |
| Complexity | 2/5 | 5/5 | 3/5 |
| Audience | developer | researcher | developer |
Figures from each repo's GitHub metadata at analysis time.
Fable Soul is a set of rules meant to change how an AI coding agent, such as Claude Code or Codex, actually behaves rather than just what it knows. The README argues that when AI agents fail, it is usually not because they lack coding knowledge, but because they lack the operating discipline a senior engineer applies automatically, such as running a test before saying a bug is fixed, or naming the real mechanism behind a problem instead of just making a symptom go away. Each rule in the project was written after a specific real failure and tested to confirm it changes the agent's behavior, rather than being general best practice advice. The project is pure Markdown plus two small Python scripts, with no dependencies. Its core file holds around 19 rules organized into checkpoints called Operating Gates. Before acting, the agent is expected to be able to state the actual goal, the mechanism behind the situation, and what evidence would prove success. Verification is matched to the kind of task: a code bug needs a reproducing test and its output, a frontend change needs the page actually loaded and inspected. The rules also cover finishing reversible work instead of stopping to ask permission, leading an answer with the outcome instead of a long report, and treating a surprising result as something to investigate rather than explain away. A distinctive part of the project is a table of excuses the README says AI models commonly give for skipping these steps, such as assuming an edit that succeeded means the fix worked, paired with why each excuse is wrong. There is also a checklist the agent is meant to run before ending each turn, looking for signs like a hedge word on a claim that could be checked directly. The project offers three ways to use it: loading the rules into a session so the agent behaves accordingly without narrating them, growing and syncing the rule set over time as new failures are captured, and converting a stronger model's advice or postmortems into new durable rules using a set of provided prompt templates. It works with Claude Code and Codex, is released under the MIT license, and includes English and Traditional Chinese versions of its documentation.
A rule set that trains AI coding agents to verify their work and reason like a senior engineer instead of just producing code.
Mainly Python. The stack also includes Python, Markdown.
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.