What this prompt does
This prompt has the AI act as a senior product designer building a budget and savings goal tracker, and it bans financial jargon from any user-facing text. It specifies a monthly budget summary, per-category progress bars with a calm over-budget alert, savings goals with target amount and date, first-run states that teach setup, micro-copy guidelines, and accessibility notes. The [user] placeholder shapes the tone and teaching, and [platform_theme] keeps the visual direction consistent across screens.
The structure works because personal-finance UIs win or lose on clarity and tone, not chart density. By requiring plain-language micro-copy with concrete numbers and a friendly over-budget alert, the prompt steers the output away from scolding or jargon. The [stack] variable keeps the screen-by-screen spec mapped to your framework, and the explicit empty and first-run states ensure a brand-new user is taught how to set their first budget and goal instead of facing a blank screen. The at-a-glance on-track, close, or over status gives users a single signal they can read in a second, which matters more than a dense breakdown when someone is checking their spending on the move and only wants to know whether they are fine.
When to use it
- Designing a personal-finance or budgeting app for a non-technical
[user] - Building monthly budget tracking with per-category progress and over-budget alerts
- Adding savings goals with target dates and suggested contributions
- You need plain-language micro-copy guidelines, not jargon-heavy labels
- Teaching first-time budgeters through empty and first-run states
- Specifying a finance feature in a particular
[platform_theme]and[stack]
Example output
You get a screen-by-screen component spec with copy examples and the key states for each screen. The budget summary shows spent vs limit with an at-a-glance on-track / close / over status, category bars include the calm over-budget alert pattern, and the savings goals section lays out target amount, date, suggested contribution, and projected completion. The empty and first-run states are spelled out so a new account is never a blank wall.
Pro tips
- Set
[user]precisely; copy aimed at first-time budgeters reads very differently from copy for finance pros - Write the over-budget alert copy first via
[platform_theme]framing; if it sounds punitive the whole screen feels punitive - Use
[stack]matching your build so the component spec is directly actionable - Ask the model to include concrete example numbers in the micro-copy, since vague copy is the default failure mode
- Insist color is never the only signal in the status indicators; request an icon or label alongside
- If the first-run state is weak, ask it to expand how the user is guided to their very first budget and goal
