What this prompt does
This prompt generates a complete UI specification for a private mood and diary journal app — covering entry creation, calendar navigation, memory timelines, mood trend insights, and a gratitude jar. The template enforces an opinionated design philosophy from the start: warm paper textures, handwriting-inspired headers, and mood-based color accents. It is not neutral scaffolding — it actively steers the AI away from the five most common ways diary apps betray user trust: social sharing features, gamification of emotional expression, passive AI entry analysis without explicit consent, advertising, and unencrypted cloud sync. Those paths are closed off in the prompt body, so the AI cannot drift into them by default.
Gentle streaks are deliberately included — the Calendar section specifies a subtle ink-fill streak indicator as a motivation mechanic. What is blocked is turning emotional expression itself into a points or badge system, not habit continuity features.
The bracketed variables — [target_audience], [features], [privacy], and [framework] — anchor the output to a real product without rewriting the design rules each time. The eight numbered sections cover every core screen: daily prompt, journal entry, calendar, memories, insights, gratitude, privacy controls, and framework-specific code.
When to use it
- You are prototyping a mental health or wellness app and need a complete screen-by-screen UI map fast.
- You want to pitch a journaling app concept and need realistic, specific output rather than vague wireframe notes.
- You are building a React Native or Flutter MVP and need the journal entry and calendar screens with actual component structure.
- You are designing for a therapist-recommended journaling tool and need privacy-first defaults baked in from the start.
- You want to generate a gratitude or mindfulness app variant by swapping
[features]while keeping the core privacy model intact.
Example output
Target audience: adult professionals managing burnout
Framework: React Native
Journal Entry Screen (Evening Reflection)
- Header: "How did today feel?" (DM Serif, warm ivory #FAF7F2 bg)
- Mood selector: horizontal emoji row (😔 😐 🙂 😊 🤩), tap animates
with a gentle pulse, selected mood sets accent color for session
- Rich text body: 14px serif, 1.8 line-height, auto-saves every 10s
- Tag chips below body: [grateful] [anxious] [proud] [tired] — multi-select
- Photo attach: inline, max 3, stored locally encrypted
- Submit: "Seal today's entry" (no social share button anywhere)
Calendar View
- Month grid, each day dot colored by dominant mood emoji hue
- Tap day → slide-up card with entry preview, no public sharing option
- Streak counter shown as a subtle ink-fill bar, not a badge or number
Pro tips
- Set
[target_audience]with clinical or demographic specificity — "adults processing grief" produces substantially different tone, color temperature guidance, and prompt phrasing than "teenagers" or "adults with generalized anxiety." Run the same prompt with two different audiences side by side to see the divergence before committing to one direction. - Use
[privacy]to name your actual encryption approach (e.g., "local-only AES-256, optional encrypted backup to user's own cloud storage") — vague privacy input produces vague implementation notes that your developer cannot act on. - Pair the framework output with a design token prompt afterward: ask the AI to extract all colors, font sizes, and spacing values into a single token file so your actual codebase stays in sync with the generated spec.
- If you only need the gratitude section built out, pass a narrow
[features]value ("gratitude jar only, no mood tracking") — the anti-pattern block still holds, so you will not get social or gamification features bleeding in even with a stripped-down feature set. - The "On this day" memory feature requires date-aware logic in your app layer — flag this to your developer early. The prompt specifies the UX but will not wire up the date query automatically unless you ask in a follow-up.
