docs: update all documentation and add AI tooling configs
- Rewrite README.md with current architecture, features and stack - Update docs/API.md with all current endpoints (corporate, BI, client 360) - Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL - Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente) - Add docs/INDEX.md documentation index - Add PROJETO.md comprehensive project reference - Add BI-CCC-Implementation-Guide.md - Include AI agent configs (.claude, .agents, .gemini, _bmad) - Add netbird VPN configuration - Add status report Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
60
_bmad/wds/workflows/4-ux-design/workflow-validate.md
Normal file
60
_bmad/wds/workflows/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