<aside> ⚡
JENS AI · by Jens Heitmann (@jens.heitmann)
Fable 5 runs on your Claude plan until July 7, then it moves to pay as you go. Pt. 1 was about jobs worth doing this week. Pt. 2 is about what survives the deadline: 8 things you build with Fable once that keep working after it is gone. Every prompt is engineered to leave you with an asset: an app, a machine, a plan, a system.
</aside>
Why it works: one builder described his dream productivity app in a single prompt. Thirty minutes later Fable handed back a working app: to-do list, kanban board, calendar, notes, focus timer, all integrated, all working on the first run. His verdict: production ready, and normally months of development.
Prompt:
You are building my dream personal app. I am the only user, and it will keep running on my machine long after you are gone, so build it to last.
The app: [one line, e.g. a personal productivity app]
The features I always wanted in one place: [list them, e.g. to-do list, calendar, notes, focus timer, kanban board]
The connections that make it one app: [e.g. tasks show up on the calendar, the timer attaches to a task, notes link to tasks]
Process:
1. Write a one page spec first: what the app does, each feature in one line, and every connection between features. Ask me up to 3 questions if anything important is unclear, then get my sign off before you write code.
2. Build with parallel agents, one per feature, then run one integration pass to wire the connections. The connections are the product. A bundle of disconnected tabs is a failure.
3. Test every feature end to end, then every connection between features. Fix what breaks and retest until a full walkthrough passes clean.
Acceptance criteria, all must pass in one run:
- I open the app, add a real task, and see it appear on the calendar.
- I start the timer against that task and attach a note to it.
- Zero errors, zero placeholder screens, and my data is still there after a restart.
Rules: fully local, no accounts, no external servers. Pick a simple stack I can maintain, and store my data in a plain readable format I can back up.
Fill in: the app type, the feature list, the connections between features.
<aside> 💡
Pro tip: spend your words on the connections between features, not the features themselves. A to-do list is generic. A to-do list that feeds your calendar and your timer is the app you always wanted. The more complex the app, the longer the build, so start with the core loop.
</aside>
What you keep: software that would have cost months, running locally, yours after July 7.
Why it works: your voice is not magic, it is a pattern sitting in your last posts, captions, and scripts. Fable can study that pattern once, write it down as a style guide, and then draft your posts, reel scripts, and comment replies in it. The blank page stops being the reason your streak breaks.
Prompt:
You are my ghostwriter. Step one is learning to sound exactly like me. Step two is never handing me a blank page again.
My content: [where my last 50 posts, captions, and scripts live: profile links, an export, a folder]
Process:
1. Study the material until you can write in my exact voice: sentence length, rhythm, vocabulary, how I open, how I close, what I never say. Note where my posts, reel scripts, and replies differ from each other.
2. Deliver the style guide as a doc I review: every voice rule paired with a real example from my own content, plus a short do-not list. Revise until I sign it off. Write it clear enough that any model could follow it without you.
3. Only after sign off, draft against it: posts, reel scripts, and comment replies, always in that voice.
4. Hand me a week at a time: [7] posts with captions, [3] reel scripts, and drafted replies to open comments, batched in one doc, each with a one line note on why the topic fits me.
5. I approve, edit, or kill every draft. Fold each edit back into the style guide so it gets sharper every week.
Rules: you never post anything yourself. Every draft waits for my approval. Anything that does not sound like me goes back, and the guide gets updated so it does not happen twice.