whatisgithub

What is fable-soul?

akseolabs-seo/fable-soul — explained in plain English

Analysis updated 2026-05-18

105PythonAudience · developerComplexity · 2/5LicenseSetup · easy

In one sentence

A rule set that trains AI coding agents to verify their work and reason like a senior engineer instead of just producing code.

Mindmap

mindmap
  root((Fable Soul))
    What it does
      Judgment rules for AI agents
      Verify before claiming done
      Root cause before fixing
    Modules
      Operating gates
      Rationalization table
      Transfer prompts
    Tech stack
      Markdown rules
      Python sync scripts
    Audience
      Claude Code users
      Codex users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Load Fable Soul's rules into Claude Code or Codex so the agent verifies fixes before claiming success.

USE CASE 2

Study the rationalization table to understand common AI agent excuses and how to counter them.

USE CASE 3

Use the transfer prompt templates to turn your own AI session lessons into reusable rules.

USE CASE 4

Sync and audit the rule files across multiple install locations using the included scripts.

What is it built with?

PythonMarkdown

How does it compare?

akseolabs-seo/fable-soulcvlab-kaist/trackcraft3ruipath/coder_eval
Stars105105105
LanguagePythonPythonPython
Last pushed2026-05-16
MaintenanceMaintained
Setup difficultyeasyhardmoderate
Complexity2/55/53/5
Audiencedeveloperresearcherdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

So what is it?

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.

Copy-paste prompts

Prompt 1
Load the Fable Soul rules from soul.md into this coding session before we start.
Prompt 2
Use the Departing Principal prompt template to turn my repo's lessons into a skill library.
Prompt 3
Explain the Proof Contract rule and how it applies to verifying a frontend change.
Prompt 4
Help me run sync_soul.py to check my installed Fable Soul rules for drift.

Frequently asked questions

What is fable-soul?

A rule set that trains AI coding agents to verify their work and reason like a senior engineer instead of just producing code.

What language is fable-soul written in?

Mainly Python. The stack also includes Python, Markdown.

What license does fable-soul use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is fable-soul to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is fable-soul for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.