trdr-ds-install 1.9.0 → 1.11.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "trdr-ds-install",
-  "version": "1.9.0",
+  "version": "1.11.0",
   "description": "Installs the TRDR Design System skill for Claude Code",
   "bin": {
     "trdr-ds-install": "./bin/install.js"

package/plugins/trdr-design-system/skills/trdr-ds/SKILL.md

@@ -2,11 +2,11 @@
 name: trdr-ds
 description: Applies the TRDR Design System to any project. Runs a multi-phase workflow - first analyzes the project and saves DS_ANALYSIS.md, then executes implementation in 4 checkpointed sub-phases (Foundation → Violations → Components → Final), each saving progress to DS_PROGRESS.md and resumable at any time. Trigger when developer mentions "apply design system", "implement TRDR DS", "add TRDR tokens", "design system setup", "migrar design system", "aplicar design system", or invokes /trdr-ds.
 user-invocable: true
-argument-hint: "[analyze|apply|foundation|violations|components|final|resume|status|sync|batch N|rollback]"
+argument-hint: "[analyze|apply|foundation|violations|components|final|resume|status|sync|batch N|rollback|report]"
 allowed-tools: [Read, Glob, Grep, Edit, Write, Bash, WebFetch]
 ---
 
-**Skill version:** 1.9.0
+**Skill version:** 1.11.0
 **npm package:** trdr-ds-install
 
 You are implementing the **TRDR Design System** in a developer's project. The Design Hub is the single source of truth and lives at **https://trdr.mrocontent.com.br**.
@@ -37,6 +37,7 @@ Execute in multiple checkpointed phases: **PHASE 1: ANALYZE (saves DS_ANALYSIS.m
 | `batch [N]` | Override default violation batch size (default: 5 files/batch) |
 | `sync` | Re-fetch `https://trdr.mrocontent.com.br/components.json` and `https://trdr.mrocontent.com.br/tokens.css`, overwrite `data/components.json` and `references/tokens.css` in the skill directory, report the diff. No project changes. |
 | `rollback` | Read `DS_PROGRESS.md` to find the backup branch, reset working branch to that state, remove DS artifacts. Requires `DS_PROGRESS.md` with a `Backup branch:` entry |
+| `report` | Generate a bug report (DS_BUG_REPORT.md) with project context, errors encountered, and current migration state. Sends via email to the skill maintainer (mrocontent@gmail.com). Can also be triggered automatically when a sub-phase encounters critical failures |
 | `--latest` *(modifier on `analyze` or `apply`)* | Same as `sync` first, then continue normally |
 
 ---
@@ -60,7 +61,7 @@ Compare the result with the **Skill version** constant at the top of this file.
 - If registry version == local version: skip silently, continue.
 - If registry version > local version:
   ```
-  🔄 Nova versão da skill disponível: trdr-ds-install@[registry-version] (instalada: 1.9.0)
+  🔄 Nova versão da skill disponível: trdr-ds-install@[registry-version] (instalada: 1.11.0)
 
   Responda:
   - `"atualizar"` / `"update"` — instalar a nova versão agora (requer reiniciar /trdr-ds após)
@@ -1034,8 +1035,38 @@ Install order: [topological — atomics first, then compounds by dependency]
 
 ## Padrões Sem Token (revisão manual)
 [empty — filled during execution]
+
+## Execution Log
+[Each action appends a row here — this is the canonical audit trail for the report]
 ```
 
+**Execution Log rule (applies to ALL sub-phases):**
+
+After every file creation or modification by the skill, append a row to the `## Execution Log` section of `DS_PROGRESS.md`:
+
+```
+| [ISO datetime] | [sub-phase] | [action] | [file path] | [details] |
+```
+
+Actions: `CREATE`, `MODIFY`, `SKIP`, `FAIL`
+
+Examples:
+```
+| 2026-05-14T10:23:01 | A | CREATE | src/styles/tokens.css | 292 CSS variables (dark+light) |
+| 2026-05-14T10:23:02 | A | CREATE | src/styles/components.css | 25 component classes + typography |
+| 2026-05-14T10:23:03 | A | MODIFY | src/styles/globals.css | @import tokens.css + components.css |
+| 2026-05-14T10:23:04 | A | CREATE | CLAUDE.md | DS context for Claude Code |
+| 2026-05-14T10:25:11 | B | MODIFY | src/components/Header.tsx | 5 violations fixed: A(3), C(2) |
+| 2026-05-14T10:25:12 | B | MODIFY | src/components/Card.css | 3 violations fixed: A(1), B(2) |
+| 2026-05-14T10:25:13 | B | SKIP | src/legacy/old.css | 0 violations — already compliant |
+| 2026-05-14T10:30:01 | C | MODIFY | src/components/Button.tsx | simple swap → .trdr-btn |
+| 2026-05-14T10:30:02 | C | FAIL | src/components/Modal.tsx | stub — not yet implemented in DS |
+| 2026-05-14T10:35:01 | D | MODIFY | public/logo.svg | replaced with logo-trdr.svg |
+| 2026-05-14T10:35:02 | D | CREATE | DS_MIGRATION.md | manual checklist generated |
+```
+
+This log is cumulative — never clear it. Each `/trdr-ds resume` session appends to the existing log.
+
 ### Step 0.5 — Git backup (safety net)
 
 Before modifying any project file, create a git backup so the entire migration can be rolled back.
@@ -1154,7 +1185,7 @@ If `references/tokens.css` is missing in the skill directory:
 
 Update `DS_PROGRESS.md`:
 ```
-- [x] tokens.css — [path]/tokens.css
+- [x] tokens.css — [path]/tokens.css ([ISO datetime])
 ```
 
 ### Step 2 — Create components.css
@@ -1201,7 +1232,7 @@ After all component CSS blocks, append the text style utility classes:
 
 Update `DS_PROGRESS.md`:
 ```
-- [x] components.css — [path]/components.css
+- [x] components.css — [path]/components.css ([ISO datetime])
 ```
 
 ### Step 3 — Update global CSS
@@ -1219,7 +1250,7 @@ If the project already imports a different design system's variables and there a
 
 Update `DS_PROGRESS.md`:
 ```
-- [x] @import — [global-css-file]
+- [x] @import — [global-css-file] ([ISO datetime])
 ```
 
 ### Step 4 — Create CLAUDE.md
@@ -1320,7 +1351,7 @@ This project uses Material UI with TRDR DS tokens integrated via the theme.
 
 Update `DS_PROGRESS.md`:
 ```
-- [x] CLAUDE.md — CLAUDE.md
+- [x] CLAUDE.md — CLAUDE.md ([ISO datetime])
 ```
 
 ### Step 5 — Generate/update MUI theme with DS tokens (only when `stylingMode === 'mui'`)
@@ -1486,9 +1517,11 @@ Próximo: Sub-fase B — Violations ([total_files_with_violations] arquivos em [
 Responda:
 - "continuar" / "continue" — iniciar Sub-fase B
 - "parar" / "stop" — salvar progresso e parar aqui
+- "não funcionou" / "report" — reportar problema ao maintainer
 ```
 
 **STOP HERE. Wait for developer reply before starting Sub-fase B.**
+If the developer indicates the implementation didn't work (see DEVELOPER DISSATISFACTION DETECTION below), trigger REPORT MODE.
 
 ---
 
@@ -1508,10 +1541,16 @@ For each batch listed as PENDING in `DS_PROGRESS.md` § Sub-fase B:
 2. For each file in the batch:
    - Apply all applicable violation fixes (see mapping tables below)
    - Count violations fixed
-3. Update `DS_PROGRESS.md` — change batch status to `COMPLETED`:
+3. Update `DS_PROGRESS.md` — change batch status to `COMPLETED` with per-file detail:
    ```
    ### Lote [N] — [folder/] ([N] arquivos) — COMPLETED
+   Completed: [ISO datetime]
    Violações corrigidas: [N] | Arquivos: [N]/[N]
+
+   | Arquivo | Violações | Categorias | Tokens aplicados |
+   |---------|-----------|------------|------------------|
+   | src/components/Header.tsx | 5 | A(3), C(2) | --content-brand, --spacing-md, --bg-primary |
+   | src/components/Card.css | 3 | A(1), B(2) | --surface-secondary, --font-primary, --font-secondary |
    ```
    Add any unfixable patterns to the "Padrões Sem Token" section of `DS_PROGRESS.md`.
 4. Output batch summary:
@@ -1529,12 +1568,14 @@ For each batch listed as PENDING in `DS_PROGRESS.md` § Sub-fase B:
    - "pular [pasta]" — skip this folder and go to the next batch
    - "parar" / "stop" — save progress and stop here (resume later with `/trdr-ds resume`)
    - "tudo" / "all" — process all remaining batches without pausing
+   - "não funcionou" / "report" — reportar problema ao maintainer
    ```
    **Wait for developer reply.**
 
    If reply is `"tudo"` / `"all"`: process all remaining batches without pausing (update DS_PROGRESS.md after each).
    If reply is `"pular [pasta]"`: mark that batch as SKIPPED in DS_PROGRESS.md and move to the next.
    If reply is `"parar"`: set `Status: PAUSED` in DS_PROGRESS.md. STOP. Do not proceed to Step 6 or 7.
+   If the developer indicates the implementation didn't work (see DEVELOPER DISSATISFACTION DETECTION below), trigger REPORT MODE.
 
 6. After ALL batches are COMPLETED (or skipped):
 
@@ -1548,9 +1589,11 @@ For each batch listed as PENDING in `DS_PROGRESS.md` § Sub-fase B:
    Responda:
    - "continuar" / "continue" — iniciar Sub-fase C
    - "parar" / "stop" — salvar progresso e parar aqui
+   - "não funcionou" / "report" — reportar problema ao maintainer
    ```
 
    **STOP HERE. Wait for developer reply before starting Sub-fase C.**
+   If the developer indicates the implementation didn't work (see DEVELOPER DISSATISFACTION DETECTION below), trigger REPORT MODE.
 
 ---
 
@@ -2050,9 +2093,11 @@ Próximo: Sub-fase D — Final (logos, ícones, DS_MIGRATION.md)
 Responda:
 - "continuar" / "continue" — iniciar Sub-fase D
 - "parar" / "stop" — salvar progresso e parar aqui
+- "não funcionou" / "report" — reportar problema ao maintainer
 ```
 
 **STOP HERE. Wait for developer reply before starting Sub-fase D.**
+If the developer indicates the implementation didn't work (see DEVELOPER DISSATISFACTION DETECTION below), trigger REPORT MODE.
 
 ---
 
@@ -2362,9 +2407,11 @@ Próximo: Sub-fase D — Final (logos + ícones + DS_MIGRATION.md)
 Responda:
 - "continuar" / "continue" — finalizar migração
 - "parar" / "stop" — salvar progresso e parar aqui
+- "não funcionou" / "report" — reportar problema ao maintainer
 ```
 
 **STOP HERE. Wait for developer reply before starting Sub-fase D.**
+If the developer indicates the implementation didn't work (see DEVELOPER DISSATISFACTION DETECTION below), trigger REPORT MODE.
 
 ---
 
@@ -2839,6 +2886,7 @@ Hub: https://trdr.mrocontent.com.br
 → Stubs not yet canonical: see MISSING_COMPONENTS.md
 → Backup branch: `trdr-ds/backup-{timestamp}` — para desfazer: `/trdr-ds rollback`
 → Para remover o backup após validar: `git branch -D trdr-ds/backup-{timestamp}`
+→ Algo deu errado? `/trdr-ds report` para enviar um bug report ao maintainer
 ```
 
 ---
@@ -2994,6 +3042,275 @@ If either fetch fails, report which one and exit. Do NOT touch the snapshot if t
 
 ---
 
+## REPORT MODE (when invoked as `/trdr-ds report` or triggered automatically)
+
+This mode generates a structured bug report and sends it to the skill maintainer via email.
+
+**Maintainer email:** `mrocontent@gmail.com`
+
+### When it triggers automatically
+
+After each sub-phase (A, B, C, D) completes — or fails to complete — evaluate these conditions:
+
+| Condition | Severity | Auto-report? |
+|-----------|----------|--------------|
+| Sub-phase crashed or could not complete (e.g., missing files, parse errors, Hub unreachable after local snapshot also missing) | CRITICAL | ✅ Yes |
+| Build fails after sub-phase changes (if detectable via `npm run build` or framework equivalent) | CRITICAL | ✅ Yes |
+| More than 30% of violations in a batch could not be mapped to any DS token (flagged as "no match") | HIGH | ✅ Yes |
+| Component replacement produced malformed JSX/HTML (unclosed tags, syntax errors caught by grep) | CRITICAL | ✅ Yes |
+| Rollback was invoked (indicates the migration went wrong enough to revert) | HIGH | ✅ Yes |
+
+When auto-report triggers, inform the developer:
+```
+⚠️ A skill detectou problemas críticos nesta migração.
+Um bug report será gerado e enviado ao maintainer (mrocontent@gmail.com).
+
+Deseja incluir observações adicionais no report?
+- Escreva seu comentário e pressione Enter
+- "pular" / "skip" — enviar sem comentários extras
+```
+**Wait for reply.** Save the developer's comment (if any) as `developerNotes` for inclusion in the report.
+
+### Manual invocation (`/trdr-ds report`)
+
+When invoked manually, the developer may optionally describe the problem:
+- `/trdr-ds report` — generates report from current state
+- `/trdr-ds report Violações não foram aplicadas nos arquivos .vue` — includes the description
+
+Ask the developer:
+```
+📝 Bug report — descreva o problema que encontrou com a skill:
+(Se já descreveu no comando, pressione Enter para confirmar)
+```
+**Wait for reply.** Save as `developerNotes`.
+
+### Step R1 — Collect project context
+
+Gather the following data silently (no output to the developer):
+
+1. **Project info:**
+   - `package.json` → name, framework, framework version, stylingMode detected
+   - Node.js version: `node --version`
+   - OS: read from environment (platform)
+   - Skill version: read from top of this file
+
+2. **Migration state:**
+   - Read `DS_ANALYSIS.md` (if exists) — extract: total violations, categories breakdown, total files
+   - Read `DS_PROGRESS.md` (if exists) — extract: current status, which sub-phases completed, which pending, and the full `## Execution Log` section (per-file audit trail with timestamps)
+   - Read `SPRINT_PLAN.md` (if exists) — extract: sprint progress
+   - Read `DS_MIGRATION.md` (if exists) — extract: manual items count
+
+3. **Error context:**
+   - If auto-triggered: capture the specific error/condition that triggered the report
+   - If manual: use `developerNotes`
+   - Last 3 files modified by the skill (from `DS_PROGRESS.md` batch logs)
+   - If build failed: capture the first 50 lines of build error output
+
+4. **Snapshot versions:**
+   - `data/components.json` → `generatedAt` and count of implemented components
+   - `references/tokens.css` → count of CSS variables (grep `--` in `:root`)
+
+### Step R2 — Generate DS_BUG_REPORT.md
+
+Write `DS_BUG_REPORT.md` at the project root:
+
+```markdown
+# TRDR DS — Bug Report
+
+**Date:** [ISO datetime]
+**Skill version:** [version from SKILL.md]
+**Report type:** [AUTOMATIC | MANUAL]
+**Severity:** [CRITICAL | HIGH | MEDIUM]
+
+---
+
+## Problem Description
+
+[developerNotes — or auto-trigger condition description]
+
+## Project Context
+
+| Field | Value |
+|-------|-------|
+| Project | [package.json name] |
+| Framework | [framework] [version] |
+| Styling mode | [stylingMode] |
+| Node.js | [version] |
+| OS | [platform] |
+
+## Migration State
+
+| Sub-phase | Status |
+|-----------|--------|
+| Analysis | [✅ COMPLETE / ⏳ PENDING / ❌ FAILED] |
+| A — Foundation | [status] |
+| B — Violations | [status — N/M batches done] |
+| C — Components | [status — N/M candidates done] |
+| D — Final | [status] |
+
+**Overall status:** [from DS_PROGRESS.md]
+**Backup branch:** [branch name or N/A]
+
+## Violation Summary
+
+| Category | Found | Fixed | Unfixable |
+|----------|-------|-------|-----------|
+| A — Hardcoded colors | [n] | [n] | [n] |
+| B — Hardcoded fonts | [n] | [n] | [n] |
+| C — Hardcoded spacing | [n] | [n] | [n] |
+| ... | ... | ... | ... |
+
+## Error Details
+
+[If build failed: first 50 lines of error output]
+[If unmapped violations: list of values that had no token match]
+[If component replacement failed: file path + what went wrong]
+
+## Files Affected
+
+[List of last files modified by the skill, from DS_PROGRESS.md]
+
+## Snapshot Info
+
+- Components catalog: [generatedAt] — [N] implemented / [M] total
+- Tokens CSS: [N] variables
+
+## Execution Log
+
+[Copy the entire `## Execution Log` section from DS_PROGRESS.md here — this is the full audit trail of every file the skill created, modified, skipped, or failed on, with timestamps]
+
+| Timestamp | Phase | Action | File | Details |
+|-----------|-------|--------|------|---------|
+| ... | ... | ... | ... | ... |
+
+## Developer Notes
+
+> [Raw text from the developer, if provided]
+```
+
+### Step R3 — Send via email (Resend API)
+
+Execute via Bash:
+
+```bash
+node -e "
+const https = require('https');
+
+const report = require('fs').readFileSync('DS_BUG_REPORT.md', 'utf8');
+const projectName = '[project-name-from-package.json]';
+const severity = '[CRITICAL|HIGH|MEDIUM]';
+const skillVersion = '[version]';
+
+const data = JSON.stringify({
+  from: 'TRDR DS Skill <onboarding@resend.dev>',
+  to: ['mrocontent@gmail.com'],
+  subject: '[TRDR DS ' + severity + '] Bug report — ' + projectName + ' (v' + skillVersion + ')',
+  text: report
+});
+
+const req = https.request({
+  hostname: 'api.resend.com',
+  path: '/emails',
+  method: 'POST',
+  headers: {
+    'Authorization': 'Bearer ' + process.env.RESEND_API_KEY,
+    'Content-Type': 'application/json',
+    'Content-Length': Buffer.byteLength(data)
+  }
+}, (res) => {
+  let body = '';
+  res.on('data', c => body += c);
+  res.on('end', () => {
+    if (res.statusCode >= 200 && res.statusCode < 300) {
+      console.log('OK: ' + body);
+    } else {
+      console.log('FAIL (' + res.statusCode + '): ' + body);
+    }
+  });
+});
+req.write(data);
+req.end();
+"
+```
+
+**If `RESEND_API_KEY` is not set in the environment:**
+```
+⚠️ RESEND_API_KEY não encontrada no ambiente.
+O report foi salvo em DS_BUG_REPORT.md mas não pôde ser enviado por email.
+
+Para configurar:
+1. Obtenha sua API key em https://resend.com/api-keys
+2. Adicione ao ambiente: export RESEND_API_KEY="re_xxxxxxxx"
+3. Ou adicione no .env do projeto e execute novamente /trdr-ds report
+```
+
+**If the email send fails (non-2xx response):**
+```
+⚠️ Falha ao enviar email (HTTP [status]): [response body]
+O report foi salvo localmente em DS_BUG_REPORT.md.
+Envie manualmente para mrocontent@gmail.com.
+```
+
+### Step R4 — Output to developer
+
+```
+[If email sent successfully:]
+✅ Bug report gerado e enviado.
+
+  📄 DS_BUG_REPORT.md (salvo no projeto)
+  📧 Email enviado para mrocontent@gmail.com
+  🏷️ Severidade: [CRITICAL|HIGH|MEDIUM]
+
+O maintainer será notificado e entrará em contato.
+
+[If email failed:]
+📄 Bug report salvo em DS_BUG_REPORT.md
+⚠️ Email não enviado — veja instruções acima.
+
+[In both cases:]
+→ Para continuar a migração: /trdr-ds resume
+→ Para reverter: /trdr-ds rollback
+```
+
+### DEVELOPER DISSATISFACTION DETECTION
+
+At every STOP checkpoint and at any point during the conversation, if the developer expresses that the implementation didn't work correctly, trigger REPORT MODE automatically. Match any of these patterns (case-insensitive, partial match):
+
+| Pattern (PT) | Pattern (EN) |
+|--------------|--------------|
+| "não funcionou" | "didn't work" |
+| "não deu certo" | "it's broken" |
+| "deu errado" | "went wrong" |
+| "ficou errado" | "messed up" |
+| "quebrou" | "broke" |
+| "não aplicou" | "didn't apply" |
+| "não tá certo" | "not right" |
+| "tá errado" | "it's wrong" |
+| "report" | "bug report" |
+
+When detected:
+1. Acknowledge the developer's feedback
+2. Execute REPORT MODE (Steps R1–R4) with `reportType: MANUAL` and `severity: HIGH`
+3. Use the developer's message as `developerNotes` — ask for additional details if the message is too vague (less than 10 characters)
+4. After sending the report, offer the developer options to continue:
+   ```
+   Responda:
+   - "rollback" — reverter todas as mudanças
+   - "continuar" — tentar prosseguir mesmo assim
+   - "parar" — salvar progresso e parar aqui
+   ```
+
+### Auto-report integration points
+
+When auto-report is triggered during a sub-phase, execute Steps R1–R4 **after** saving progress to `DS_PROGRESS.md` but **before** the STOP checkpoint. The sub-phase continues normally after the report — the developer can still choose to continue, stop, or rollback.
+
+Add to `DS_PROGRESS.md` when a report is sent:
+```
+Bug report: DS_BUG_REPORT.md (sent [ISO datetime] — [AUTOMATIC|MANUAL] — [severity])
+```
+
+---
+
 ## LIVE HUB REFERENCE (canonical fallback)
 
 When the developer asks about a component, token, or rule that is not in the local snapshot, fetch from the Hub: