@johnnyheo: Fable and Sol tend to use a lot of jargon that's hard to understand on a first read, which slows me down a lot i've fou…
Summary
Johnny Heo shares a tip for improving user-facing explanations by adding a style rule to agent or Claude.md files to write clearly without jargon, and setting personality to none in .codex/config.toml.
View Cached Full Text
Cached at: 07/12/26, 12:56 PM
Fable and Sol tend to use a lot of jargon that’s hard to understand on a first read, which slows me down a lot
i’ve found incredible success adding the following to agents or claude.md
Write user-facing explanations in clear, concise language without reducing technical precision. Prefer concrete wording over unexplained jargon. Use established domain terminology when it is the most precise choice, and briefly define it when the intended audience may not know it. Preserve material evidence, constraints, tradeoffs, caveats, and uncertainty. Do not rewrite code, identifiers, commands, quoted text, or prescribed formats merely to satisfy this style rule.
and adding personality = “none” to ~/.codex/config.toml
Similar Articles
@PrajwalTomar_: Fable 5 PRO tip... Don't just read this field guide from the Claude Code team. Hand the whole thing to Fable and say: "…
A tip for Fable users: instead of just reading the Claude Code team's field guide, give the whole article to Fable and have it create a SKILL file so it automatically applies the techniques in future sessions without prompting.
Let Fable use its own judgement rather than dictating how it should work (2 minute read)
Practical tips for using AI coding tools like Fable and Opus: let them apply their own judgement instead of dictating behavior, and delegate smaller tasks to lower-power models via subagents to save tokens and improve efficiency.
@itsolelehmann: this is how you work *beautifully* with Fable. Thariq's point: when Fable gets something wrong, it's almost always beca…
A tweet shares nine practical techniques for working effectively with Fable, emphasizing upfront prompting to avoid mistakes, including blindspot passes, asking for options, and letting the AI ask clarifying questions.
Fable's judgement
A practical tip from Simon Willison: allow Claude Code's Fable model to use its own judgment for testing and delegate coding tasks to subagents running cheaper models, reducing token usage while maintaining quality.
@DeRonin_: i ran Fable 5 the whole day and still haven't touched my limits why? i stopped paying surgeon rates for small talk here…
A user shares a detailed workflow strategy for efficiently using multiple AI models (Fable, Opus, Codex, DeepSeek, GLM, Qwen, Kimi) by delegating tasks based on cost and capability, using a single CLAUDE.md routing table, and avoiding small talk to reduce token usage.