kakaroto-config 1.0.5 → 1.0.6

package/config/commands/feature/playbooks/ui/red.md

@@ -0,0 +1,71 @@
+# UI - RED (Testes)
+
+## Testes Requeridos
+
+| Tipo | Obrigatorio | Motivo |
+|------|-------------|--------|
+| Unit | SE hooks | Logica de hooks isolada |
+| Integration | Opcional | Componentes complexos |
+| E2E | **SIM** | Fluxo visual do usuario |
+
+## Mocks Tipicos
+- API routes: MSW ou fetch mock
+- Context providers
+- Next.js router
+
+## Test Pattern - Hook (Vitest)
+
+```typescript
+import { describe, it, expect } from 'vitest';
+import { renderHook, act } from '@testing-library/react';
+import { useFeature } from './useFeature';
+
+describe('useFeature', () => {
+  it('should initialize with default state', () => {
+    const { result } = renderHook(() => useFeature());
+    expect(result.current.state).toEqual({ items: [], loading: false });
+  });
+
+  it('should update state on action', () => {
+    const { result } = renderHook(() => useFeature());
+
+    act(() => {
+      result.current.actions.addItem({ id: '1', name: 'Test' });
+    });
+
+    expect(result.current.state.items).toHaveLength(1);
+  });
+});
+```
+
+## Test Pattern - Component (React Testing Library)
+
+```typescript
+import { describe, it, expect, vi } from 'vitest';
+import { render, screen, fireEvent } from '@testing-library/react';
+import { FeatureComponent } from './FeatureComponent';
+
+describe('FeatureComponent', () => {
+  it('should render items', () => {
+    render(<FeatureComponent items={[{ id: '1', name: 'Test' }]} />);
+    expect(screen.getByText('Test')).toBeInTheDocument();
+  });
+
+  it('should call onSubmit when form submitted', async () => {
+    const onSubmit = vi.fn();
+    render(<FeatureComponent onSubmit={onSubmit} />);
+
+    fireEvent.change(screen.getByLabelText('Name'), {
+      target: { value: 'New Item' },
+    });
+    fireEvent.click(screen.getByRole('button', { name: 'Submit' }));
+
+    expect(onSubmit).toHaveBeenCalledWith({ name: 'New Item' });
+  });
+});
+```
+
+## Convenções
+- Hooks: testar com `renderHook`
+- Components: preferir queries por role/label
+- Forms: testar submit e validacao

package/config/commands/feature.md

@@ -1,13 +1,46 @@
 ---
 model: opus
 ---
-# Feature Workflow
+# Feature Workflow v2
 
 Desenvolver: $ARGUMENTS
 
 ## INICIAR
-AÇÃO OBRIGATÓRIA: Read ~/.claude/commands/feature/01-interview.md
-Seguir instruções. Cada fase aponta para a próxima.
+ACAO OBRIGATORIA: Read ~/.claude/commands/feature/01-understand.md
+Seguir instrucoes. Cada fase aponta para a proxima.
 
 ## Fluxo
-Interview → Spec → Planner → [APROVAÇÃO] → Implement → Quality → Commit → Evaluate
+
+```
+01-understand (requisitos)
+    ↓ User responde perguntas de PRODUTO
+02-analyze (interna - triage + playbook)
+    ↓ Automatico
+03-strategy ← UNICA APROVACAO
+    ↓ User aprova estrategia de testes
+04-red (RED)
+    ↓ Automatico
+05-green (GREEN)
+    ↓ Automatico
+06-quality (REFACTOR)
+    ↓ Automatico
+07-validation (E2E)
+    ↓ Automatico
+08-delivery (commit)
+    ↓ Automatico
+09-evaluate (auto-avaliacao)
+```
+
+## Fases
+
+| Fase | Responsabilidade | Aprovacao? |
+|------|------------------|------------|
+| 01-understand | Coletar requisitos de produto | User responde |
+| 02-analyze | Triage + playbook (interna) | Automatico |
+| 03-strategy | Aprovar estrategia de testes | **USER APROVA** |
+| 04-red | Escrever testes RED | Automatico |
+| 05-green | Código mínimo GREEN | Automatico |
+| 06-quality | REFACTOR + Quality Gate | Automatico |
+| 07-validation | E2E Validation | Automatico |
+| 08-delivery | Commit + Push + Memory Sync | Automatico |
+| 09-evaluate | Auto-avaliacao + melhorias | Automatico |

package/config/commands/gate.md

@@ -75,7 +75,7 @@ Based on changes detected, invoke appropriate agents **using Task tool with suba
 **IMPORTANTE:** Todos os agents sao TOTALMENTE AUTONOMOS - eles irao identificar E CORRIGIR problemas automaticamente.
 
 **Ordem de execucao:**
-`test-fixer (baseline) -> code-simplifier -> dry-enforcer -> test-fixer (verificacao) -> code-reviewer -> visual-validator (se UI) -> terraform-validator (se env)`
+`test-fixer (baseline) -> code-simplifier (inclui DRY) -> test-fixer (verificacao) -> code-reviewer -> visual-validator (se UI) -> terraform-validator (se env)`
 
 ### 3.1 Test Fixer (BASELINE)
 
@@ -91,28 +91,18 @@ Garantir que codigo implementado passa nos testes ANTES de refatorar.
 
 **If tests fail:** Fix before proceeding. NAO prosseguir ate baseline passar.
 
-### 3.2 Code Simplification
+### 3.2 Code Simplification (inclui DRY)
 
 **Invoke:** `Task` tool with `subagent_type: code-simplifier`
 
 **Expected output:**
 - Dead code removed
 - Naming improved
-- Structure simplified
-- Magic values extracted
+- Structure simplified (nesting, function length)
+- Duplications replaced with calls to existing utils/services
+- Reimplementations flagged and fixed
 
-### 3.3 DRY Analysis
-
-**Invoke:** `Task` tool with `subagent_type: dry-enforcer`
-
-**Expected output:**
-- Unused existing code that should have been used
-- Duplications within new code
-- Abstraction opportunities
-
-**If issues found:** Fix before proceeding.
-
-### 3.4 Test Fixer (VERIFICACAO)
+### 3.3 Test Fixer (VERIFICACAO)
 
 Garantir que refatoracoes nao quebraram nada.
 
@@ -127,7 +117,7 @@ Garantir que refatoracoes nao quebraram nada.
 
 **If tests fail:** Fix before proceeding.
 
-### 3.5 Code Review
+### 3.4 Code Review
 
 **Invoke:** `Task` tool with `subagent_type: code-reviewer`
 
@@ -139,7 +129,7 @@ Garantir que refatoracoes nao quebraram nada.
 
 **If CRITICAL issues found:** Fix before proceeding.
 
-### 3.6 Visual Validation (SE UI)
+### 3.5 Visual Validation (SE UI)
 
 **Detect UI changes:**
 ```bash
@@ -164,7 +154,7 @@ git diff origin/main...HEAD --name-only | grep -E '\.(tsx|css|scss)$' | grep -v
 
 **If FAIL after 3 attempts:** BLOCK gate, report errors to user.
 
-### 3.7 Environment Validation (SE env)
+### 3.6 Environment Validation (SE env)
 
 **Detect env changes:**
 ```bash
@@ -200,8 +190,7 @@ Collect results from all agents (na ordem de execucao):
 | Agent | Status | Issues Found | Fixed |
 |-------|--------|--------------|-------|
 | test-fixer (baseline) | PASS/FAIL | X | X |
-| code-simplifier | PASS/FAIL | X | X |
-| dry-enforcer | PASS/FAIL | X | X |
+| code-simplifier (DRY) | PASS/FAIL | X | X |
 | test-fixer (verificacao) | PASS/FAIL | X | X |
 | code-reviewer | PASS/FAIL | X | X |
 | visual-validator | SKIP/PASS/FAIL | X | X |
@@ -249,8 +238,7 @@ Gerar relatorio consolidado:
 | Agent | Status | Issues Found | Fixed |
 |-------|--------|--------------|-------|
 | test-fixer (baseline) | [PASS/FAIL] | X | X |
-| code-simplifier | [PASS/FAIL] | X | X |
-| dry-enforcer | [PASS/FAIL] | X | X |
+| code-simplifier (DRY) | [PASS/FAIL] | X | X |
 | test-fixer (verificacao) | [PASS/FAIL] | X | X |
 | code-reviewer | [PASS/FAIL] | X | X |
 | visual-validator | [SKIP/PASS/FAIL] | X | X |

package/config/templates/spec-template.md

@@ -1,92 +1,106 @@
 # Spec: [Nome da Feature]
 
-**Status:** Draft
+## Metadata
+- **Data:** [YYYY-MM-DD]
+- **Interview:** `.claude/interviews/[slug].md`
+- **Acceptance Criteria Source:** Interview Fase 1
 
-## Problema
-[1-2 frases - o problema, não a solução]
+---
 
-## Solução
-[Descrição de alto nível]
+## Resumo
 
-## Escopo
+[1-2 frases descrevendo o que a feature faz]
 
-### Inclui
-- [Deliverable 1]
-- [Deliverable 2]
+---
 
-### Não Inclui
-- [O que não será feito]
+## Componentes
 
-## Design Técnico
+| Componente | Tipo | Descrição |
+|------------|------|-----------|
+| [nome] | Service/Handler/Component | [descrição] |
 
-### Dados
-[Estruturas, campos novos, tabelas]
+---
 
-### Services
-| Service | Mudanças |
-|---------|----------|
-| [nome] | [o que muda] |
+## Código a Reutilizar
 
-### API (se aplicável)
-[Endpoints, signatures]
+| Necessidade | Código Existente | Ação |
+|-------------|------------------|------|
+| [o que precisa] | [arquivo:linha] ou "Não existe" | Reutilizar/Estender/Criar |
 
-### Tratamento de Erros
-| Cenário | Comportamento |
-|---------|---------------|
-| [erro] | [o que acontece] |
+---
 
-### Reutilização Obrigatória
-| Existente | Uso |
-|-----------|-----|
-| [código] | [como usar] |
+## Test Cases
 
-### Justificativa para Código Novo
-| Novo Código | Por que não reutilizar existente? |
-|-------------|-----------------------------------|
-| [arquivo/função] | [justificativa] |
+### Acceptance Tests (OBRIGATÓRIOS)
 
-## UI/UX (se aplicável)
+| Acceptance Criterion (user) | Acceptance Test | Tipo |
+|-----------------------------|-----------------|------|
+| "[criterion 1 - linguagem do user]" | `it('[comportamento observável]')` | Integration/E2E |
+| "[criterion 2 - linguagem do user]" | `it('[comportamento observável]')` | Integration/E2E |
 
-### Fluxo
-1. User faz X
-2. Sistema responde Y
+**Validação mental:** Se este teste passar, o user validaria manualmente e ficaria satisfeito? ✓
 
-### Estados
-| Estado | Display |
-|--------|---------|
-| Loading | [desc] |
-| Empty | [desc] |
-| Error | [desc] |
-| Success | [desc] |
+### Unit Tests (se lógica complexa)
 
-## Edge Cases
-| Caso | Tratamento |
-|------|------------|
-| [edge] | [como tratar] |
+| Função | Test Case | Input → Output |
+|--------|-----------|----------------|
+| `[função]` | `[caso]` | `[input]` → `[output]` |
 
-## Testes
+### Integration Tests (se multi-serviço)
 
-### Unitários (OBRIGATÓRIO)
-| Função | Arquivo Teste | Casos |
-|--------|---------------|-------|
-| [func] | [file.test.ts] | [casos] |
+| Fluxo | Serviços Envolvidos | Mock Strategy |
+|-------|---------------------|---------------|
+| `[fluxo]` | `[serviços]` | `[o que mockar]` |
 
-### API/Integração (SE CRUD)
-| Endpoint | Método | Casos |
-|----------|--------|-------|
-| [/api/X] | [POST] | [criar, validação 400, erro 500] |
+### E2E Tests (se UI)
 
-### E2E/Smoke (SE UI)
-| Fluxo | Verificação |
-|-------|-------------|
-| [Criar via form] | [Entidade aparece na lista] |
+| Fluxo | Steps | Verificação |
+|-------|-------|-------------|
+| `[fluxo]` | `[passos]` | `[assertion]` |
 
-### Infraestrutura (SE Banco)
-| Recurso | Configuração |
-|---------|--------------|
-| [Collection X] | [Índice: accountId + createdAt DESC] |
+---
 
-## Decisões
-| Decisão | Justificativa |
-|---------|---------------|
-| [escolha] | [por quê] |
+## Mock Strategy
+
+| Test Case | Mock Level | Serviços Mockados |
+|-----------|------------|-------------------|
+| [acceptance test 1] | integration | [apenas externos obrigatórios] |
+| [unit test 1] | unit | - |
+
+### Princípio de Mocks
+
+- **Acceptance Tests:** Mínimo de mocks (apenas serviços externos obrigatórios)
+- **Unit Tests:** Liberado para isolar
+
+---
+
+## Arquivos a Criar/Modificar
+
+| Arquivo | Ação | Descrição |
+|---------|------|-----------|
+| `[path]` | Criar/Modificar | `[descrição]` |
+
+---
+
+## Dependências
+
+- [ ] Nenhuma nova dependência
+- [ ] Nova dependência: `[nome]` - Motivo: [explicação]
+
+---
+
+## Riscos Identificados
+
+| Risco | Mitigação |
+|-------|-----------|
+| [risco] | [como mitigar] |
+
+---
+
+## Checklist de Spec
+
+- [ ] Todos Acceptance Criteria têm Acceptance Test correspondente
+- [ ] Acceptance Tests validam comportamento observável (não implementação)
+- [ ] Mocks para Acceptance Tests são mínimos
+- [ ] Código existente foi mapeado para reutilização
+- [ ] Arquivos a criar/modificar estão listados

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kakaroto-config",
-  "version": "1.0.5",
+  "version": "1.0.6",
   "description": "Claude Code configuration by Pedro Jahara - autonomous workflows for /feature, /debug, /gate",
   "bin": {
     "kakaroto-config": "bin/install.js"

package/config/agents/dry-enforcer.md

@@ -1,227 +0,0 @@
----
-name: dry-enforcer
-description: "DRY (Don't Repeat Yourself) specialist. Use PROACTIVELY after new code is added to detect duplications, suggest existing code reuse, and identify abstraction opportunities. MUST BE USED before any PR."
-tools: Read, Edit, Grep, Glob, Bash, mcp__memory__search_nodes
-model: opus
----
-
-You are a DRY (Don't Repeat Yourself) enforcement specialist.
-
-## Core Principle
-
-**Default is to REUSE. New code requires JUSTIFICATION.**
-
-## Scope (DYNAMIC)
-
-1. Load scope from MCP Memory:
-   `mcp__memory__search_nodes({ query: "config" })`
-
-2. Extract `codebase_scope` and `forbidden_paths` from the entity observations
-
-3. If not found, use current working directory as scope
-
-4. **NEVER** modify files outside the allowed scope
-
-## When Invoked
-
-### Step 1: Identify New/Changed Code
-
-```bash
-git diff --stat HEAD~1
-```
-
-### Step 2: Map Project Structure
-
-Search for utilities and services directories:
-```bash
-find . -type d -name "utils" -o -name "services" -o -name "helpers" 2>/dev/null
-```
-
-List existing helpers and services to check before creating new code.
-
-### Step 3: Search for Similar Existing Code
-
-For each new function/logic block, search for similar patterns in the codebase.
-
-## Analysis Categories
-
-### 1. Unused Existing Code (CRITICAL)
-
-Code that SHOULD have been used but wasn't:
-
-| New Code | Existing Alternative | Location | Action |
-|----------|---------------------|----------|--------|
-| [new function/pattern] | [existing helper] | [file:line] | REFACTOR to use existing |
-
-### 2. Duplication Within New Code
-
-Similar logic appearing multiple times in new changes:
-
-| Pattern | Occurrences | Files |
-|---------|-------------|-------|
-| [code pattern] | [count] | [file1, file2] |
-
-**Action:** Extract to helper function.
-
-### 3. Duplication With Existing Code
-
-New code that duplicates existing functionality:
-
-| New Code Location | Duplicates | Existing Location |
-|-------------------|------------|-------------------|
-| [file:line] | [what] | [existing file:line] |
-
-**Action:** Use existing implementation.
-
-### 4. Abstraction Opportunities
-
-If 3+ places use similar pattern, consider creating abstraction:
-
-| Pattern | Locations | Proposed Abstraction |
-|---------|-----------|---------------------|
-| [repeated code] | [list of files] | [helper/util name] |
-
-## Scoring System
-
-For each new file/function, score DRY compliance:
-
-| Score | Meaning | Action |
-|-------|---------|--------|
-| A | Uses existing code perfectly | Approve |
-| B | Minor improvements possible | Note suggestions |
-| C | Significant duplication | Request changes |
-| D | Rewrite recommended | Block until fixed |
-
-## Anti-Patterns to Flag
-
-| Anti-Pattern | Example | Correct Approach |
-|--------------|---------|------------------|
-| Reimplementing date logic | Custom date formatting | Use existing dateHelpers |
-| New database queries | Direct DB calls | Use existing service |
-| Duplicate validation | Inline schemas | Extract to shared schema |
-| Copy-paste error handling | Repeated try/catch | Create error handler util |
-| Hardcoded constants | Magic strings/numbers | Extract to constants file |
-
-## Questions to Ask for New Code
-
-For each NEW file or function, answer:
-
-1. **Did you check utils/ for similar helpers?**
-2. **Did you check services/ for similar functionality?**
-3. **Can this be generalized for future reuse?**
-4. **Why couldn't you use existing code?**
-
-If answers are unsatisfactory, flag for refactoring.
-
-## Output Format
-
-### DRY Analysis Report
-
-**Files Analyzed:** [list]
-**Overall DRY Score:** [A-D]
-
----
-
-#### CRITICAL Issues (Must Fix)
-
-| Location | Issue | Existing Code | Action |
-|----------|-------|---------------|--------|
-| [file:line] | [duplication] | [existing file:line] | Refactor to use existing |
-
----
-
-#### HIGH Issues (Should Fix)
-
-| Location | Issue | Suggestion |
-|----------|-------|------------|
-| [file:line] | [description] | [how to improve] |
-
----
-
-#### Abstraction Opportunities
-
-If I found 3+ similar patterns:
-
-**Proposed Helper:** `[name]`
-**Purpose:** [what it does]
-**Locations that would benefit:**
-- [file1:line]
-- [file2:line]
-- [file3:line]
-
----
-
-#### Summary
-
-| Metric | Count |
-|--------|-------|
-| Critical issues | X |
-| High issues | X |
-| Abstraction opportunities | X |
-| **Ready for PR** | YES/NO |
-
----
-
-## Autonomia Total
-
-**REGRA:** Este agent e TOTALMENTE AUTONOMO. Aplique TODAS as correcoes diretamente, sem pedir aprovacao.
-
-### Auto-fix (apply ALL directly):
-
-| Issue Type | Action |
-|------------|--------|
-| Reimplementation of existing utils | **Replace** with call to existing util |
-| Reimplementation of existing services | **Replace** with call to existing service |
-| Copy-paste code blocks | **Extract** to helper function |
-| Magic values hardcoded | **Extract** to constants |
-| Duplicated validation logic | **Extract** to shared schema |
-| Similar code patterns (3+ occurrences) | **Create** abstraction in utils/ |
-
-### Workflow
-
-1. Identify all DRY violations
-2. **Automatically fix each one** (use Edit tool)
-3. Run type check to verify no errors introduced
-4. If type errors, revert and try simpler fix
-5. Report summary of what was changed
-
-**NAO peca confirmacao.** Execute as correcoes e reporte o que foi feito.
-
----
-
-## Checklist Before Approval
-
-- [ ] No reimplementation of existing utils
-- [ ] No reimplementation of existing services
-- [ ] No copy-paste code blocks
-- [ ] Magic values extracted to constants
-- [ ] New helpers are generic enough for reuse
-- [ ] New code justified (if existing could have been used)
-
----
-
-## Quality Gates
-
-After fixes, run quality gates from Memory (search for `quality_gates`).
-
-All must pass before marking complete.
-
----
-
-## Output Obrigatorio
-
-Ao final do relatorio, SEMPRE incluir:
-
-```
----AGENT_RESULT---
-STATUS: PASS | FAIL
-ISSUES_FOUND: <numero>
-ISSUES_FIXED: <numero>
-BLOCKING: true | false
----END_RESULT---
-```
-
-Regras:
-- STATUS=FAIL se DRY Score e D (rewrite recomendado)
-- BLOCKING=true se reimplementacao de codigo existente nao corrigida
-- BLOCKING=false se apenas sugestoes de abstracao (Score B ou C)

package/config/commands/debug/techniques/flow-tracing.md

@@ -1,75 +0,0 @@
-# Tecnica: Rastreamento de Fluxo
-
-Para bugs que envolvem **dados incorretos** (null, undefined, formato invalido, valor inesperado).
-
----
-
-## Passo 1: Identificar Valor Problematico
-
-- Qual valor esta errado?
-- Onde ele CAUSA o erro? (arquivo:linha)
-
----
-
-## Passo 2: Rastrear para Tras (Backward Tracing)
-
-Seguir a call chain de volta ate a ORIGEM:
-
-1. **ONDE e usado?** (ponto do erro) → arquivo:linha
-2. **QUEM chama essa funcao?** → `Grep: "nomeDaFuncao("`
-3. **DE ONDE vem o parametro?** → Subir na call chain
-4. **ONDE o valor e definido/calculado?** → Continuar ate achar a ORIGEM
-
----
-
-## Passo 3: Diagrama de Fluxo
-
-Documentar o caminho completo:
-
-```
-FLUXO DO VALOR:
-[ORIGEM]      →   [transform 1]   →   [transform 2]   →   [USO/ERRO]
-arquivo1:42   →   arquivo2:108    →   arquivo3:55     →   arquivo4:23
-   |                  |                   |                   |
-   v                  v                   v                   v
- [valor]          [operacao]          [operacao]          [erro]
-```
-
----
-
-## Passo 4: Classificacao do Bug
-
-O bug esta em qual parte do fluxo?
-
-- [ ] **ORIGEM**: Valor ja nasce errado (ex: input invalido, query errada)
-- [ ] **TRANSFORMACAO**: Valor e corrompido no caminho (ex: parsing, conversao)
-- [ ] **USO**: Valor correto usado incorretamente (ex: logica errada, condicao invertida)
-
-**IMPORTANTE**: O fix deve ser aplicado onde o problema COMECA, nao onde ele APARECE.
-
----
-
-## Passo 4.1: SE Origem em Arquivo de Config Gerado
-
-**SE** valor incorreto vem de arquivo de config (.env, .json, .yaml):
-
-1. **O arquivo e GERADO ou EDITADO manualmente?**
-   - `Grep: ">.env" ou "generate_" ou "create.*config"`
-
-2. **SE GERADO**: Rastrear processo gerador
-   - QUAL script gera o arquivo?
-   - ONDE no script o valor e definido?
-
-3. **Diagrama Estendido**:
-   ```
-   [PROCESSO]  →  [CONFIG]  →  [APP]
-   deploy.sh   →  .env      →  app.ts
-   ```
-
-4. **Classificacao**:
-   - [ ] ORIGEM EM PROCESSO: Script gera valor errado
-   - [ ] ORIGEM EM TEMPLATE: Template tem erro
-   - [ ] TRANSFORMACAO: Script corrompe durante geracao
-
-**IMPORTANTE**: Corrigir arquivo manualmente e PALIATIVO.
-Fix DEVE corrigir o PROCESSO GERADOR.