chore: initial monorepo scaffold + WDS Phase 1+2 artifacts
- 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>
This commit is contained in:
@@ -0,0 +1,52 @@
|
||||
# Tone of Voice Example: SaaS Onboarding Tool
|
||||
|
||||
**Context:** B2B SaaS for employee onboarding, target users are HR managers (stressed, overwhelmed, want to feel capable)
|
||||
|
||||
---
|
||||
|
||||
## Suggested Tone of Voice
|
||||
|
||||
### Tone Attributes
|
||||
|
||||
1. **Supportive & Reassuring**: HR managers are stressed about onboarding. Our tone should reduce anxiety, not add to it.
|
||||
2. **Professional but Warm**: B2B context requires professionalism, but warmth builds trust.
|
||||
3. **Clear & Concise**: Busy users need straightforward communication, no fluff.
|
||||
4. **Empowering**: Frame actions around user capability, not system features.
|
||||
|
||||
### Examples
|
||||
|
||||
**Error Message:**
|
||||
- ✅ "We couldn't find that email. Double-check for typos?"
|
||||
- ❌ "Error 404: User not found"
|
||||
|
||||
**Button Text:**
|
||||
- ✅ "Add your first employee"
|
||||
- ❌ "Create new record"
|
||||
|
||||
**Empty State:**
|
||||
- ✅ "Your onboarding dashboard is ready. Let's add your first employee to get started."
|
||||
- ❌ "No employees added yet"
|
||||
|
||||
**Success Message:**
|
||||
- ✅ "Perfect! Sarah's onboarding is set up. We'll send her the welcome email tomorrow at 9 AM."
|
||||
- ❌ "Employee record created successfully"
|
||||
|
||||
---
|
||||
|
||||
## Analysis
|
||||
|
||||
**Why This Tone Works:**
|
||||
- **Supportive**: "We couldn't find" (collaborative) vs "Error" (blaming)
|
||||
- **Professional but Warm**: Uses proper grammar but friendly language
|
||||
- **Clear**: Specific, actionable messages without jargon
|
||||
- **Empowering**: "Add your first employee" (user action) vs "Create new record" (system function)
|
||||
|
||||
**Alignment with User State:**
|
||||
- HR managers are stressed → Reassuring tone reduces anxiety
|
||||
- Want to feel capable → Empowering language focuses on their actions
|
||||
- Need efficiency → Clear, concise messaging respects their time
|
||||
- Professional context → Maintains appropriate formality with warmth
|
||||
|
||||
---
|
||||
|
||||
_Example demonstrating Tone of Voice definition for B2B SaaS product_
|
||||
Reference in New Issue
Block a user