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>
141 lines
4.7 KiB
Markdown
141 lines
4.7 KiB
Markdown
---
|
|
name: 'step-08-seo-compliance'
|
|
description: 'Verify page specifications follow SEO best practices aligned with Phase 1 keyword strategy'
|
|
|
|
# File References
|
|
nextStepFile: './step-09-design-system-consistency.md'
|
|
workflowFile: '../workflow.md'
|
|
activityWorkflowFile: '../workflow-validate.md'
|
|
---
|
|
|
|
# Step 8: Validate SEO Compliance
|
|
|
|
## STEP GOAL:
|
|
|
|
Verify page specifications follow SEO best practices aligned with Phase 1 keyword strategy.
|
|
|
|
## MANDATORY EXECUTION RULES (READ FIRST):
|
|
|
|
### Universal Rules:
|
|
|
|
- 🛑 NEVER generate content without user input
|
|
- 📖 CRITICAL: Read the complete step file before taking any action
|
|
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
|
- 📋 YOU ARE A FACILITATOR, not a content generator
|
|
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
|
|
|
### Role Reinforcement:
|
|
|
|
- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
|
|
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
|
|
- ✅ We engage in collaborative dialogue, not command-response
|
|
- ✅ You bring design expertise and systematic thinking, user brings product vision and domain knowledge
|
|
- ✅ Maintain creative and thoughtful tone throughout
|
|
|
|
### Step-Specific Rules:
|
|
|
|
- 🎯 Focus on SEO compliance: headings, meta content, keywords, URL structure
|
|
- 🚫 FORBIDDEN to skip keyword alignment check against Phase 1 strategy
|
|
- 💬 Approach: Systematic SEO audit against checklist, generate report
|
|
- 📋 Reference Phase 1 keyword map for alignment validation
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Audit page specifications for SEO compliance across all check categories
|
|
- 💾 Update page specification if SEO fixes are approved by user
|
|
- 📖 Reference Phase 1 keyword strategy for alignment
|
|
- 🚫 FORBIDDEN to skip any SEO check category
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: Page specification, Phase 1 keyword strategy
|
|
- Focus: SEO compliance validation only
|
|
- Limits: Do not validate design or content quality
|
|
- Dependencies: Page specification must exist, Phase 1 keyword strategy should be available
|
|
|
|
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
|
|
|
### 1. Heading Structure
|
|
|
|
- [ ] Each page has exactly one H1
|
|
- [ ] H1 contains or relates to the page's primary keyword
|
|
- [ ] Heading hierarchy is logical (H1 -> H2 -> H3, no skips)
|
|
- [ ] Headings are descriptive (not generic like "Section 1")
|
|
|
|
### 2. Meta Content
|
|
|
|
- [ ] Page title defined (or template for it)
|
|
- [ ] Meta description defined (or template for it)
|
|
- [ ] Open Graph tags considered (if applicable)
|
|
|
|
### 3. Keyword Alignment
|
|
|
|
- [ ] Page's primary keyword matches Phase 1 keyword map assignment
|
|
- [ ] No two pages compete for the same primary keyword
|
|
- [ ] Content naturally incorporates target keywords (not keyword-stuffed)
|
|
|
|
### 4. URL Structure
|
|
|
|
- [ ] Page URL/slug follows SEO-friendly patterns
|
|
- [ ] URL contains relevant keywords
|
|
- [ ] No unnecessary depth in URL path
|
|
|
|
### 5. Generate SEO Compliance Report
|
|
|
|
```
|
|
## SEO Compliance Report
|
|
|
|
**Pages audited:** [N]
|
|
**Heading issues:** [N]
|
|
**Meta issues:** [N]
|
|
**Keyword misalignments:** [N]
|
|
|
|
[List specific pages with SEO issues]
|
|
```
|
|
|
|
### 6. Resolve Issues
|
|
|
|
If issues found, present to user and ask if they want you to fix the SEO-related content.
|
|
|
|
### 7. Present MENU OPTIONS
|
|
|
|
Display: "**Select an Option:** [C] Continue to Validate Design System Consistency | [M] Return to Activity Menu"
|
|
|
|
#### Menu Handling Logic:
|
|
|
|
- IF C: Load, read entire file, then execute {nextStepFile}
|
|
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
|
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
|
|
|
|
#### EXECUTION RULES:
|
|
|
|
- ALWAYS halt and wait for user input after presenting menu
|
|
- User can chat or ask questions — always respond and then redisplay menu options
|
|
|
|
## CRITICAL STEP COMPLETION NOTE
|
|
|
|
ONLY WHEN the user selects an option from the menu and the SEO compliance validation is complete will you proceed to the next step or return as directed.
|
|
|
|
---
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
|
|
|
### ✅ SUCCESS:
|
|
|
|
- Heading structure validated (single H1, logical hierarchy)
|
|
- Meta content checked (title, description, OG tags)
|
|
- Keyword alignment verified against Phase 1 strategy
|
|
- URL structure validated
|
|
- SEO Compliance Report generated
|
|
- Issues resolved with user approval
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
|
|
- Skipping any SEO check category
|
|
- Not referencing Phase 1 keyword strategy
|
|
- Not generating SEO Compliance Report
|
|
- Auto-fixing SEO issues without user approval
|
|
- Proceeding without completing all checks
|
|
|
|
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|