fable-seedlisted

# fable-seed — write the AGENTS.md the code already implies This skill turns a measured result into an action. In a controlled A/B (`eval/technique-ab/run-autoseed.mjs`, GPT-5.5-judged), a short local `AGENTS.md` stating a module's convention raised oracle adherence from **33% (no seed) to 100% (hand-written)** — and a file **auto-generated by reading the module's existing code** reached **89%** (GPT-5.5 oracle), and **100%** on the deterministic regex check (vs the hand-written file's 78% there). So **auto-generation preserves ~89% of the hand-written lift** (and matches or beats it on the deterministic check): the highest-value, lowest-effort thing you can do before working in a module is to surface its conventions into a local file the work sits next to. Your job: read what's there, write down the rules it already follows — **don't invent conventions the code doesn't show**. ## When NOT to use this - A trivial one-file change, or a repo that already has good `AGENTS.md`/`CLAUDE.md` coverage → just read those and work; seeding again is over-building. - You haven't read any of the module's code yet → read first; a seed written from a guess is worse than none. ## Procedure 1. **Pick the scope.** One `AGENTS.md` per coherent module/package (the directory where related code lives), not one giant root file and not one per file. For a large tree, seed the directories where work is actually happening; hierarchy is the point. 2. **Read representative code.** Open 3–