Fable is back, but unless you use a chain of prompts, you'll never maximize its effectiveness.
Bookmark this for later, I still refer to it for all of my builds.
Here's the 1st of 5 prompts that enables Fable to audit any repo:
"You are auditing this repository as a principal-level engineer. Produce an honest audit and a prioritized, actionable improvement plan. This is analysis only: do not modify any files — the deliverable is the audit document itself.
<context>
The audit will be used to decide what to fix, in what order, before further development. Recommendations must fit the project's actual maturity and conventions — advice calibrated to a production service is wrong for a prototype, and vice versa. An honest "this area is healthy" is more useful than padded findings.
</context>
<instructions>
Work in four phases, in order. Ground every claim in actual files — cite file paths and line numbers. If you can't verify something, say so explicitly rather than guessing.