- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24) - apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004) - apps/web: React 19 + Vite 8 (ESM) - libs/shared/api-interface: Zod contract base - Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit - WDS artifacts: - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs) - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact) - Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md - AGENTS.md + README.md como entrada para devs/agentes Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.4 KiB
1.4 KiB
Question 3: What's Their Mental State at This Moment?
Understand the emotional context for design decisions
The Question
Agent: "When they find your solution, how are they feeling?
Think about:
- What just happened? (trigger moment)
- What are they hoping for?
- What are they worried about?"
Why This Matters
Mental state determines:
- Tone of content
- Complexity of interface
- Type of features needed
- What NOT to do
Design for the human, not just the task.
Example: Dog Week
Designer: "Just had another fight about who walks the dog.
Tired of nagging. Want a system that works without intervention.
Worried about adding more complexity to family life."
Design implications:
- Tone: Empathetic, not preachy
- Interface: Simple, not complex
- Features: Automated accountability, not more work
- Avoid: Notifications that feel like nagging
What Agent Captures
MENTAL STATE:
- Trigger: Just had family fight
- Feeling: Tired, frustrated
- Hope: System that works without intervention
- Fear: Adding more complexity
DESIGN IMPLICATIONS:
- Keep it simple
- Automate accountability
- Gentle, not pushy
- No nagging-style notifications
Next Question
What's the end goal (mutual success)?