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:
60
.agents/skills/wds-4-ux-design/workflow-validate.md
Normal file
60
.agents/skills/wds-4-ux-design/workflow-validate.md
Normal file
@@ -0,0 +1,60 @@
|
||||
---
|
||||
name: 'workflow-validate'
|
||||
description: 'Systematically audit page specifications for completeness, consistency, and quality.'
|
||||
---
|
||||
|
||||
# [V] Validate — Quality Audit
|
||||
|
||||
**Goal:** Systematically audit page specifications for completeness, consistency, and quality.
|
||||
|
||||
**When to use:** After completing page specifications, or at any point to check quality.
|
||||
|
||||
---
|
||||
|
||||
## INITIALIZATION
|
||||
|
||||
Read design log at `{output_folder}/_progress/00-design-log.md` before starting.
|
||||
|
||||
### Configuration Loading
|
||||
|
||||
1. Load project config
|
||||
2. Locate page specifications at `{output_folder}/C-UX-Scenarios/`
|
||||
3. Begin: Load and execute `./steps-v/step-01-page-metadata.md`
|
||||
|
||||
**Reference data:**
|
||||
- `./data/quality-guide.md`
|
||||
- `./data/validation-standards.md`
|
||||
- `./templates/diagnostic-report-template.md`
|
||||
|
||||
---
|
||||
|
||||
## Validation Sequence
|
||||
|
||||
Execute each step in order. Each step produces a section of the validation report.
|
||||
|
||||
| Step | Name | Validates |
|
||||
|------|------|-----------|
|
||||
| 01 | Page Metadata | Title, URL, purpose defined |
|
||||
| 02 | Navigation | Entry/exit points, breadcrumbs, nav items |
|
||||
| 03 | Page Overview | Overall structure and flow |
|
||||
| 04 | Page Sections | Each section complete and ordered |
|
||||
| 05 | Section Order | Logical progression |
|
||||
| 06 | Object Registry | All components registered |
|
||||
| 07 | Design System Separation | Components vs. page-specific |
|
||||
| 08 | SEO Compliance | Headings, meta, keyword alignment |
|
||||
| 09 | Design System Consistency | Cross-page component usage |
|
||||
| 10 | Final Validation | Overall quality assessment |
|
||||
|
||||
---
|
||||
|
||||
## Final Output
|
||||
|
||||
Save validation report to `{output_folder}/_progress/validation-report.md`
|
||||
|
||||
---
|
||||
|
||||
## AFTER COMPLETION
|
||||
|
||||
1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`:
|
||||
`### [date] — Validation: [N] pages audited, [results summary]`
|
||||
2. If issues found, suggest fixing them. If all pass, suggest next logical step from the adaptive dashboard
|
||||
Reference in New Issue
Block a user