Constraint
One Screen Vow
remove setup friction and keep the whole job visible at once
Creative utility
Draw a constraint, a weird twist, and a launch ritual to turn a fuzzy idea into a tiny tool brief.
Privacy by default: your input stays in the browser. No account ceremony, no server confessional.
Project idea
Feed the deck a project idea, draw a constraint, a weird twist, and a launch ritual, then let the machine turn them into one compact brief.
Constraint
remove setup friction and keep the whole job visible at once
Twist
Frame the tool like a tiny prophecy rather than a sterile dashboard.
Ritual
Set a same-day launch deadline and keep the scope inside that fence.
Draw count: 0. Same cards, same brief. Only the draw changes the omen.
Generated brief
Three cards turned one fuzzy idea into a buildable brief with a little ritual around the edges.
Problem
Help makers with too many tabs open make progress on turn fuzzy product ideas into shippable tiny tool briefs, but obey one stubborn rule: remove setup friction and keep the whole job visible at once. Frame the tool like a tiny prophecy rather than a sterile dashboard.
Input
Use one primary input and at most one optional helper field. Aim the primary interaction at makers with too many tabs open, not at abstract personas.
Output
Return one clear result panel with one obvious next action. Shape the output as a fortune-note tone with plain-language usefulness underneath.
Delightful interaction
Give each result a short verdict that sounds mildly haunted but still practical. The result should feel slightly theatrical, but still useful enough to ship.
Launch ritual
Set a same-day launch deadline and keep the scope inside that fence. Publish one screenshot and one sentence explaining what tiny job the tool does. Do not add a second mode before the first mode feels alive.
How to use the omen
Keep the constraint card honest. It should make the tool smaller and sharper, not more impressive on paper.
Let the twist card shape the interaction, not the whole product. A little theater goes a long way.
Treat the ritual card like launch discipline. It tells you how to ship and what kind of proof to collect.
No. The cards, logic, and brief assembly all run locally in the browser.
A small, concrete job works best, for example rewrite weak CTAs, generate launch captions, or compare two drafts.
No. It is a forcing function for scope, interaction, and launch thinking. Keep what helps, redraw what does not.