julian
17c08e6392
- 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>
96 lines
2.1 KiB
Markdown
96 lines
2.1 KiB
Markdown
# Content Generation Instructions
|
|
|
|
**How to generate strategically grounded content variations**
|
|
|
|
---
|
|
|
|
## 1. Synthesize All Context
|
|
|
|
Before generating, review and confirm you understand:
|
|
- [ ] WHO the user is and what drives them (Trigger Map)
|
|
- [ ] WHERE they are in awareness (START → END)
|
|
- [ ] WHAT action this content must enable (Action Filter)
|
|
- [ ] HOW to make them feel capable (Empowerment Frame)
|
|
- [ ] WHAT order creates persuasive flow (Golden Circle)
|
|
|
|
---
|
|
|
|
## 2. Generate Multiple Variations
|
|
|
|
Create **2-3 content variations** that differ in:
|
|
|
|
**Variation A: Wish-Focused**
|
|
- Emphasizes positive driving forces
|
|
- Aspirational tone
|
|
- "Become the authority," "Stay ahead," "Impress your clients"
|
|
|
|
**Variation B: Fear-Focused**
|
|
- Addresses negative driving forces
|
|
- Problem-recognition tone
|
|
- "Stop feeling behind," "Never miss a trend," "No more embarrassment"
|
|
|
|
**Variation C: Balanced OR Awareness-Shifted** (choose one):
|
|
- **Balanced:** Combines wish + fear naturally
|
|
- **Awareness-Shifted:** Uses different starting awareness level (if user was uncertain)
|
|
|
|
**For each variation, include:**
|
|
- Complete content (headlines, body, CTA)
|
|
- Rationale explaining the approach
|
|
- Why this might resonate
|
|
|
|
---
|
|
|
|
## 3. Presentation Format
|
|
|
|
Use this format:
|
|
|
|
```markdown
|
|
---
|
|
|
|
## Variation A: [Name - e.g., "Wish-Focused"]
|
|
|
|
### Rationale
|
|
[Why this approach, what driving force it emphasizes, when this works best]
|
|
|
|
### Content
|
|
|
|
**WHY Section:**
|
|
[Content for WHY]
|
|
|
|
**HOW Section:**
|
|
[Content for HOW]
|
|
|
|
**WHAT Section:**
|
|
[Content for WHAT]
|
|
|
|
### Why This Might Resonate
|
|
[Specific user insight or context that makes this effective]
|
|
|
|
---
|
|
|
|
## Variation B: [Name]
|
|
[Same structure]
|
|
|
|
---
|
|
|
|
## Variation C: [Name]
|
|
[Same structure]
|
|
|
|
---
|
|
```
|
|
|
|
---
|
|
|
|
## 4. Explain Strategic Choices
|
|
|
|
For each variation, show how you applied the strategic context:
|
|
- "This opens with [X] because the user is Problem Aware—they need problem validation first"
|
|
- "This uses 'you'll be able to' framing because of Badass Users principle"
|
|
- "This puts social proof before CTA because Action Filter identified trust as a barrier"
|
|
|
|
**Make the strategy visible.**
|
|
|
|
---
|
|
|
|
_Reference for generating content variations in Step 6_
|