aiox-core 5.0.3 → 5.0.4

package/pro/squads/design/tasks/ds-reverse-engineer.md

@@ -1,194 +1,194 @@
-# Reverse Engineer Validated System
-
-> Task ID: ds-reverse-engineer
-> Agent: Brad Frost (Design System Architect)
-> Version: 1.0.0
-> Heuristic: #9 - Engenharia reversa do validado > criar do zero
-
-## Description
-
-Extrair padrões de design systems validados (Shopify, Vercel, ClickMax, etc) em vez de criar do zero.
-
-**Princípio:** Sistemas com milhões de usuários já validaram UX. Extrair > inventar.
-
----
-
-## Input Contract
-
-```yaml
-input:
-  source_url: string          # URL do sistema a analisar
-  source_type: enum           # "public_site" | "figma" | "storybook" | "github"
-  focus_areas:                # Áreas de interesse
-    - tokens
-    - components
-    - patterns
-    - interactions
-  output_format: enum         # "report" | "tokens" | "components" | "full"
-```
-
-## Output Contract
-
-```yaml
-output:
-  analysis_report:
-    source: string
-    extraction_date: date
-    patterns_found: array
-    tokens_extracted: object
-    components_identified: array
-    recommendations: array
-  artifacts:
-    - path: string
-      type: string
-```
-
----
-
-## Workflow
-
-### Phase 1: Capture
-
-```bash
-# Para sites públicos
-node infrastructure/services/etl/bin/fetch-page.js <url> --format json
-
-# Para Storybook
-# Navegar e capturar via Playwright
-
-# Para Figma
-# Usar Figma API ou MCP
-```
-
-**Deliverable:** Raw data capturado
-
-### Phase 2: Extract
-
-1. **Tokens**
-   - Cores (primitives + semantic)
-   - Spacing scale
-   - Typography scale
-   - Border radius
-   - Shadows
-
-2. **Components**
-   - Lista de componentes identificados
-   - Variantes por componente
-   - Estados (hover, focus, disabled, error)
-
-3. **Patterns**
-   - Layout patterns
-   - Navigation patterns
-   - Form patterns
-   - Feedback patterns
-
-**Deliverable:** Structured extraction
-
-### Phase 3: Analyze
-
-1. Comparar com nosso `design-tokens-spec.yaml`
-2. Identificar gaps
-3. Identificar conflitos
-4. Priorizar adoção
-
-**Deliverable:** Gap analysis report
-
-### Phase 4: Propose
-
-1. Propor tokens para adicionar/modificar
-2. Propor componentes para criar
-3. Propor patterns para adotar
-4. Estimar esforço
-
-**Deliverable:** Adoption proposal
-
----
-
-## Veto Conditions
-
-- [ ] Source não é acessível
-- [ ] Source requer autenticação não disponível
-- [ ] Extração viola ToS do source
-- [ ] Padrões extraídos conflitam com brand guidelines
-
----
-
-## Quality Gates
-
-- [ ] Extraction é reproduzível (script documentado)
-- [ ] Tokens extraídos validam contra schema
-- [ ] Gap analysis tem priorização clara
-- [ ] Proposal tem estimativa de esforço
-
----
-
-## Example Output
-
-```yaml
-# extraction-report-vercel-2026-02-16.yaml
-source: "vercel.com/dashboard"
-extraction_date: "2026-02-16"
-
-tokens_extracted:
-  colors:
-    background: "#000000"
-    foreground: "#FFFFFF"
-    accents:
-      blue: "#0070F3"
-      cyan: "#50E3C2"
-  spacing:
-    base: "4px"
-    scale: [4, 8, 16, 24, 32, 48, 64]
-  radius:
-    sm: "4px"
-    md: "6px"
-    lg: "8px"
-
-components_identified:
-  - name: "Button"
-    variants: ["primary", "secondary", "ghost", "danger"]
-    sizes: ["sm", "md", "lg"]
-  - name: "Card"
-    variants: ["default", "hover", "selected"]
-
-patterns_identified:
-  - name: "Dashboard Layout"
-    description: "Sidebar + main content"
-  - name: "Empty State"
-    description: "Icon + title + description + CTA"
-
-recommendations:
-  - priority: "high"
-    action: "Adopt spacing scale (matches our 4px base)"
-  - priority: "medium"
-    action: "Consider accent color palette"
-```
-
----
-
-## References
-
-- Meeting Insights: Heuristic #9
-- Design Tokens Spec: `squads/design/data/design-tokens-spec.yaml`
-- ETL Service: `infrastructure/services/etl/`
-
----
-
-*Task criada: 2026-02-16*
-*Squad: Design*
-
-
-## Related Checklists
-
-- `squads/design/checklists/ds-component-quality-checklist.md`
-- `squads/design/checklists/ds-pattern-audit-checklist.md`
-
-## Process Guards
-- **Execution Type:** `Hybrid`
-- **Dependencies:** depends_on: `[]` · enables: `[]` · workflow: `design-system`
-- **On Fail:** Stop execution, capture evidence, and return remediation steps before proceeding.
-
-## Success Criteria
-- [ ] Output artifact(s) generated and referenced.
-- [ ] Validation checks executed with evidence.
-- [ ] Next-step dependencies documented.
+# Reverse Engineer Validated System
+
+> Task ID: ds-reverse-engineer
+> Agent: Brad Frost (Design System Architect)
+> Version: 1.0.0
+> Heuristic: #9 - Engenharia reversa do validado > criar do zero
+
+## Description
+
+Extrair padrões de design systems validados (Shopify, Vercel, ClickMax, etc) em vez de criar do zero.
+
+**Princípio:** Sistemas com milhões de usuários já validaram UX. Extrair > inventar.
+
+---
+
+## Input Contract
+
+```yaml
+input:
+  source_url: string          # URL do sistema a analisar
+  source_type: enum           # "public_site" | "figma" | "storybook" | "github"
+  focus_areas:                # Áreas de interesse
+    - tokens
+    - components
+    - patterns
+    - interactions
+  output_format: enum         # "report" | "tokens" | "components" | "full"
+```
+
+## Output Contract
+
+```yaml
+output:
+  analysis_report:
+    source: string
+    extraction_date: date
+    patterns_found: array
+    tokens_extracted: object
+    components_identified: array
+    recommendations: array
+  artifacts:
+    - path: string
+      type: string
+```
+
+---
+
+## Workflow
+
+### Phase 1: Capture
+
+```bash
+# Para sites públicos
+node infrastructure/services/etl/bin/fetch-page.js <url> --format json
+
+# Para Storybook
+# Navegar e capturar via Playwright
+
+# Para Figma
+# Usar Figma API ou MCP
+```
+
+**Deliverable:** Raw data capturado
+
+### Phase 2: Extract
+
+1. **Tokens**
+   - Cores (primitives + semantic)
+   - Spacing scale
+   - Typography scale
+   - Border radius
+   - Shadows
+
+2. **Components**
+   - Lista de componentes identificados
+   - Variantes por componente
+   - Estados (hover, focus, disabled, error)
+
+3. **Patterns**
+   - Layout patterns
+   - Navigation patterns
+   - Form patterns
+   - Feedback patterns
+
+**Deliverable:** Structured extraction
+
+### Phase 3: Analyze
+
+1. Comparar com nosso `design-tokens-spec.yaml`
+2. Identificar gaps
+3. Identificar conflitos
+4. Priorizar adoção
+
+**Deliverable:** Gap analysis report
+
+### Phase 4: Propose
+
+1. Propor tokens para adicionar/modificar
+2. Propor componentes para criar
+3. Propor patterns para adotar
+4. Estimar esforço
+
+**Deliverable:** Adoption proposal
+
+---
+
+## Veto Conditions
+
+- [ ] Source não é acessível
+- [ ] Source requer autenticação não disponível
+- [ ] Extração viola ToS do source
+- [ ] Padrões extraídos conflitam com brand guidelines
+
+---
+
+## Quality Gates
+
+- [ ] Extraction é reproduzível (script documentado)
+- [ ] Tokens extraídos validam contra schema
+- [ ] Gap analysis tem priorização clara
+- [ ] Proposal tem estimativa de esforço
+
+---
+
+## Example Output
+
+```yaml
+# extraction-report-vercel-2026-02-16.yaml
+source: "vercel.com/dashboard"
+extraction_date: "2026-02-16"
+
+tokens_extracted:
+  colors:
+    background: "#000000"
+    foreground: "#FFFFFF"
+    accents:
+      blue: "#0070F3"
+      cyan: "#50E3C2"
+  spacing:
+    base: "4px"
+    scale: [4, 8, 16, 24, 32, 48, 64]
+  radius:
+    sm: "4px"
+    md: "6px"
+    lg: "8px"
+
+components_identified:
+  - name: "Button"
+    variants: ["primary", "secondary", "ghost", "danger"]
+    sizes: ["sm", "md", "lg"]
+  - name: "Card"
+    variants: ["default", "hover", "selected"]
+
+patterns_identified:
+  - name: "Dashboard Layout"
+    description: "Sidebar + main content"
+  - name: "Empty State"
+    description: "Icon + title + description + CTA"
+
+recommendations:
+  - priority: "high"
+    action: "Adopt spacing scale (matches our 4px base)"
+  - priority: "medium"
+    action: "Consider accent color palette"
+```
+
+---
+
+## References
+
+- Meeting Insights: Heuristic #9
+- Design Tokens Spec: `squads/design/data/design-tokens-spec.yaml`
+- ETL Service: `infrastructure/services/etl/`
+
+---
+
+*Task criada: 2026-02-16*
+*Squad: Design*
+
+
+## Related Checklists
+
+- `squads/design/checklists/ds-component-quality-checklist.md`
+- `squads/design/checklists/ds-pattern-audit-checklist.md`
+
+## Process Guards
+- **Execution Type:** `Hybrid`
+- **Dependencies:** depends_on: `[]` · enables: `[]` · workflow: `design-system`
+- **On Fail:** Stop execution, capture evidence, and return remediation steps before proceeding.
+
+## Success Criteria
+- [ ] Output artifact(s) generated and referenced.
+- [ ] Validation checks executed with evidence.
+- [ ] Next-step dependencies documented.

package/pro/squads/design/tasks/ds-scan-artifact.md

@@ -1,131 +1,131 @@
-# Design System Artifact Scan Task
-
-> Task ID: ds-scan-artifact
-> Agent: design-system
-> Version: 1.1.0
-> v4.0-compatible: true
-> Extends: generic-scan.md
-> **Execution Type:** `Agent`
-> **Dependencies:** depends_on: `[]` · enables: `[ds-rebuild-artifact]` · workflow: `artifact-analysis`
-
-## Output Schema
-- **produces:** `outputs/design-system/{project}/artifacts/artifact-scan-{id}.json`
-- **format:** JSON data
-- **consumed_by:** ds-rebuild-artifact
-
-## Description
-
-Analyzes HTML/React artifacts to extract design patterns, components,
-colors, typography, and other design system elements. Generates comprehensive
-reports with auto-incrementing artifact IDs.
-
-## Specific Workflow
-
-## Execution Steps
-
-1. Inicializar ambiente de scan e validar pré-requisitos.
-2. Definir origem do artefato (arquivo, URL ou conteúdo colado).
-3. Normalizar nome do artefato e reservar ID único.
-4. Executar extração de padrões visuais e estruturais.
-5. Gerar relatório JSON de análise.
-6. Atualizar metadata e registry de scans.
-7. Expor resumo final com próximos passos.
-
-### 1. Initialize Scan
-
-```bash
-# Set agent parameters
-AGENT_NAME="design-system"
-SCAN_TYPE="artifact-analysis"
-
-# Load core library
-source squads/super-agentes/scan-system/lib/scan-core.sh
-
-# Validate environment
-validate_scan_environment "$AGENT_NAME"
-```
-
-### 2. Get Target
-
-Interactive prompt or parameter:
-- File path: `path/to/artifact.html`
-- URL: `https://example.com/artifact`
-- Direct paste: User provides HTML content
-
-### 3. Get Artifact Name
-
-```bash
-# Prompt for descriptive name
-echo "Enter a descriptive name for this artifact (e.g., 'dashboard', 'pricing-table'):"
-read ARTIFACT_NAME
-# Sanitize name (remove spaces, special chars)
-ARTIFACT_NAME=$(echo "$ARTIFACT_NAME" | tr ' ' '-' | tr -cd '[:alnum:]-')
-```
-
-### 4. Get Next ID and Create Metadata
-
-```bash
-ARTIFACT_ID=$(get_next_artifact_id "$AGENT_NAME")
-echo "📋 Assigned Artifact ID: $ARTIFACT_ID"
-
-METADATA_FILE=$(create_metadata "$AGENT_NAME" "$ARTIFACT_ID" "$SCAN_TYPE" "$ARTIFACT_NAME")
-echo "📄 Created metadata: $METADATA_FILE"
-```
-
-### 5. Analyze Artifact
-
-Extract design elements from HTML/React content.
-
-### 6. Generate Report
-
-Create comprehensive analysis report with extracted data.
-
-### 7. Update Metadata with Results
-
-Update metadata file with analysis metrics and extracted data.
-
-### 8. Update Registry and Commit
-
-Update scan registry and optionally commit to git.
-
-### 9. Display Summary
-
-Show completion message with artifact details and next steps.
-
-## Failure Handling
-
-- **Invalid artifact source:** If URL returns 404 or file not found, exit with error "Artifact not accessible at {source}. Verify path/URL and permissions."
-- **HTML parsing fails:** If artifact contains malformed HTML or non-HTML content, attempt recovery with lenient parser, note "HTML parsing recovered with lenient mode — review extracted data for accuracy"
-- **No design patterns found:** If artifact has no colors, spacing, or typography (empty extraction), exit with error "No design patterns detected in {artifact}. Verify content contains CSS or inline styles."
-- **Duplicate artifact name:** If ARTIFACT_NAME already exists in registry with different content, append timestamp suffix and note "Name collision resolved: saved as {name}-{timestamp}"
-
-## Success Criteria
-
-- [ ] Artifact analyzed and data extracted
-- [ ] Report generated with all sections
-- [ ] Metadata includes all metrics
-- [ ] Registry updated correctly
-- [ ] Git commit created (if enabled)
-
-## Example Usage
-
-```bash
-# From Design System agent
-*scan path/to/dashboard.html
-
-# Or with URL
-*scan https://example.com/artifact.html
-
-# Or paste content directly
-*scan
-# [Agent prompts for content]
-```
-
-
-## Related Checklists
-
-- `squads/design/checklists/ds-component-quality-checklist.md`
-- `squads/design/checklists/ds-pattern-audit-checklist.md`
-
-## Process Guards
-- **On Fail:** Stop execution, capture evidence, and return remediation steps before proceeding.
+# Design System Artifact Scan Task
+
+> Task ID: ds-scan-artifact
+> Agent: design-system
+> Version: 1.1.0
+> v4.0-compatible: true
+> Extends: generic-scan.md
+> **Execution Type:** `Agent`
+> **Dependencies:** depends_on: `[]` · enables: `[ds-rebuild-artifact]` · workflow: `artifact-analysis`
+
+## Output Schema
+- **produces:** `outputs/design-system/{project}/artifacts/artifact-scan-{id}.json`
+- **format:** JSON data
+- **consumed_by:** ds-rebuild-artifact
+
+## Description
+
+Analyzes HTML/React artifacts to extract design patterns, components,
+colors, typography, and other design system elements. Generates comprehensive
+reports with auto-incrementing artifact IDs.
+
+## Specific Workflow
+
+## Execution Steps
+
+1. Inicializar ambiente de scan e validar pré-requisitos.
+2. Definir origem do artefato (arquivo, URL ou conteúdo colado).
+3. Normalizar nome do artefato e reservar ID único.
+4. Executar extração de padrões visuais e estruturais.
+5. Gerar relatório JSON de análise.
+6. Atualizar metadata e registry de scans.
+7. Expor resumo final com próximos passos.
+
+### 1. Initialize Scan
+
+```bash
+# Set agent parameters
+AGENT_NAME="design-system"
+SCAN_TYPE="artifact-analysis"
+
+# Load core library
+source squads/super-agentes/scan-system/lib/scan-core.sh
+
+# Validate environment
+validate_scan_environment "$AGENT_NAME"
+```
+
+### 2. Get Target
+
+Interactive prompt or parameter:
+- File path: `path/to/artifact.html`
+- URL: `https://example.com/artifact`
+- Direct paste: User provides HTML content
+
+### 3. Get Artifact Name
+
+```bash
+# Prompt for descriptive name
+echo "Enter a descriptive name for this artifact (e.g., 'dashboard', 'pricing-table'):"
+read ARTIFACT_NAME
+# Sanitize name (remove spaces, special chars)
+ARTIFACT_NAME=$(echo "$ARTIFACT_NAME" | tr ' ' '-' | tr -cd '[:alnum:]-')
+```
+
+### 4. Get Next ID and Create Metadata
+
+```bash
+ARTIFACT_ID=$(get_next_artifact_id "$AGENT_NAME")
+echo "📋 Assigned Artifact ID: $ARTIFACT_ID"
+
+METADATA_FILE=$(create_metadata "$AGENT_NAME" "$ARTIFACT_ID" "$SCAN_TYPE" "$ARTIFACT_NAME")
+echo "📄 Created metadata: $METADATA_FILE"
+```
+
+### 5. Analyze Artifact
+
+Extract design elements from HTML/React content.
+
+### 6. Generate Report
+
+Create comprehensive analysis report with extracted data.
+
+### 7. Update Metadata with Results
+
+Update metadata file with analysis metrics and extracted data.
+
+### 8. Update Registry and Commit
+
+Update scan registry and optionally commit to git.
+
+### 9. Display Summary
+
+Show completion message with artifact details and next steps.
+
+## Failure Handling
+
+- **Invalid artifact source:** If URL returns 404 or file not found, exit with error "Artifact not accessible at {source}. Verify path/URL and permissions."
+- **HTML parsing fails:** If artifact contains malformed HTML or non-HTML content, attempt recovery with lenient parser, note "HTML parsing recovered with lenient mode — review extracted data for accuracy"
+- **No design patterns found:** If artifact has no colors, spacing, or typography (empty extraction), exit with error "No design patterns detected in {artifact}. Verify content contains CSS or inline styles."
+- **Duplicate artifact name:** If ARTIFACT_NAME already exists in registry with different content, append timestamp suffix and note "Name collision resolved: saved as {name}-{timestamp}"
+
+## Success Criteria
+
+- [ ] Artifact analyzed and data extracted
+- [ ] Report generated with all sections
+- [ ] Metadata includes all metrics
+- [ ] Registry updated correctly
+- [ ] Git commit created (if enabled)
+
+## Example Usage
+
+```bash
+# From Design System agent
+*scan path/to/dashboard.html
+
+# Or with URL
+*scan https://example.com/artifact.html
+
+# Or paste content directly
+*scan
+# [Agent prompts for content]
+```
+
+
+## Related Checklists
+
+- `squads/design/checklists/ds-component-quality-checklist.md`
+- `squads/design/checklists/ds-pattern-audit-checklist.md`
+
+## Process Guards
+- **On Fail:** Stop execution, capture evidence, and return remediation steps before proceeding.