@daniel-da-silva-alves/sddk 2.0.0 → 2.1.0

package/sddk/skills/system-design-document/references/standards-design-system-template.md

@@ -1,116 +1,116 @@
-# Template: Design System do Projeto
+# Template: Project Design System
 
-Use este template para gerar `.specs/standards/design-system.md`. Preencha com as respostas do onboarding. Se o projeto é backend-only, criar o arquivo com conteúdo "N/A — projeto backend-only".
+Use this template to generate `.specs/standards/design-system.md`. Fill in with the onboarding interview answers. If the project is backend-only, create the file with content "N/A — backend-only project".
 
 ```markdown
 # Design System
 
-**Projeto**: {nome do projeto}
-**Última atualização**: {data}
+**Project**: {project name}
+**Last updated**: {date}
 
 ---
 
-## 1. Paleta de Cores
+## 1. Color Palette
 
-### Cores Primárias
-| Token | Valor | Uso |
+### Primary Colors
+| Token | Value | Usage |
 |:---|:---|:---|
-| `--color-primary-50` | {ex: #e8f0fe} | Backgrounds suaves |
-| `--color-primary-100` | {ex: #d2e3fc} | Hover em backgrounds |
-| `--color-primary-500` | {ex: #4285f4} | Ações primárias, links |
-| `--color-primary-700` | {ex: #1a73e8} | Hover em ações primárias |
-| `--color-primary-900` | {ex: #174ea6} | Texto em destaque |
-
-### Cores de Superfície
-| Token | Valor | Uso |
+| `--color-primary-50` | {e.g.: #e8f0fe} | Soft backgrounds |
+| `--color-primary-100` | {e.g.: #d2e3fc} | Hover on backgrounds |
+| `--color-primary-500` | {e.g.: #4285f4} | Primary actions, links |
+| `--color-primary-700` | {e.g.: #1a73e8} | Hover on primary actions |
+| `--color-primary-900` | {e.g.: #174ea6} | Highlighted text |
+
+### Surface Colors
+| Token | Value | Usage |
 |:---|:---|:---|
-| `--color-surface` | {ex: #ffffff} | Background de cards, modals |
-| `--color-surface-variant` | {ex: #f8f9fa} | Background de seções alternadas |
-| `--color-on-surface` | {ex: #1f1f1f} | Texto sobre surfaces |
-| `--color-on-surface-secondary` | {ex: #5f6368} | Texto secundário |
-| `--color-outline` | {ex: #dadce0} | Bordas, divisores |
-
-### Cores Semânticas
-| Token | Valor | Uso |
+| `--color-surface` | {e.g.: #ffffff} | Card, modal backgrounds |
+| `--color-surface-variant` | {e.g.: #f8f9fa} | Alternating section backgrounds |
+| `--color-on-surface` | {e.g.: #1f1f1f} | Text on surfaces |
+| `--color-on-surface-secondary` | {e.g.: #5f6368} | Secondary text |
+| `--color-outline` | {e.g.: #dadce0} | Borders, dividers |
+
+### Semantic Colors
+| Token | Value | Usage |
 |:---|:---|:---|
-| `--color-error` | {ex: #d32f2f} | Erros, validação |
-| `--color-success` | {ex: #0f9d58} | Sucesso, confirmação |
-| `--color-warning` | {ex: #f9ab00} | Alertas, avisos |
-| `--color-info` | {ex: #4285f4} | Informações |
+| `--color-error` | {e.g.: #d32f2f} | Errors, validation |
+| `--color-success` | {e.g.: #0f9d58} | Success, confirmation |
+| `--color-warning` | {e.g.: #f9ab00} | Alerts, warnings |
+| `--color-info` | {e.g.: #4285f4} | Information |
 
-### Modo Escuro (se aplicável)
-| Token Light | Token Dark | Valor Dark |
+### Dark Mode (if applicable)
+| Light Token | Dark Token | Dark Value |
 |:---|:---|:---|
-| `--color-surface` | `--color-surface-dark` | {ex: #1e1e1e} |
+| `--color-surface` | `--color-surface-dark` | {e.g.: #1e1e1e} |
 
 ---
 
-## 2. Tipografia
+## 2. Typography
 
-### Fontes
-| Token | Valor | Uso |
+### Fonts
+| Token | Value | Usage |
 |:---|:---|:---|
-| `--font-family` | {ex: 'Inter', sans-serif} | Texto geral |
-| `--font-family-heading` | {ex: 'Outfit', sans-serif} | Headings |
-| `--font-family-mono` | {ex: 'JetBrains Mono', monospace} | Código |
+| `--font-family` | {e.g.: 'Inter', sans-serif} | General text |
+| `--font-family-heading` | {e.g.: 'Outfit', sans-serif} | Headings |
+| `--font-family-mono` | {e.g.: 'JetBrains Mono', monospace} | Code |
 
-### Tamanhos
-| Token | Valor | Line Height | Uso |
+### Sizes
+| Token | Value | Line Height | Usage |
 |:---|:---|:---|:---|
-| `--text-xs` | {ex: 0.75rem} | {ex: 1rem} | Labels, captions |
-| `--text-sm` | {ex: 0.875rem} | {ex: 1.25rem} | Body small |
-| `--text-base` | {ex: 1rem} | {ex: 1.5rem} | Body default |
-| `--text-lg` | {ex: 1.125rem} | {ex: 1.75rem} | Body large |
-| `--text-xl` | {ex: 1.25rem} | {ex: 1.75rem} | Heading 4 |
-| `--text-2xl` | {ex: 1.5rem} | {ex: 2rem} | Heading 3 |
-| `--text-3xl` | {ex: 1.875rem} | {ex: 2.25rem} | Heading 2 |
-| `--text-4xl` | {ex: 2.25rem} | {ex: 2.5rem} | Heading 1 |
-
-### Pesos
-| Token | Valor | Uso |
+| `--text-xs` | {e.g.: 0.75rem} | {e.g.: 1rem} | Labels, captions |
+| `--text-sm` | {e.g.: 0.875rem} | {e.g.: 1.25rem} | Body small |
+| `--text-base` | {e.g.: 1rem} | {e.g.: 1.5rem} | Body default |
+| `--text-lg` | {e.g.: 1.125rem} | {e.g.: 1.75rem} | Body large |
+| `--text-xl` | {e.g.: 1.25rem} | {e.g.: 1.75rem} | Heading 4 |
+| `--text-2xl` | {e.g.: 1.5rem} | {e.g.: 2rem} | Heading 3 |
+| `--text-3xl` | {e.g.: 1.875rem} | {e.g.: 2.25rem} | Heading 2 |
+| `--text-4xl` | {e.g.: 2.25rem} | {e.g.: 2.5rem} | Heading 1 |
+
+### Weights
+| Token | Value | Usage |
 |:---|:---|:---|
-| `--font-regular` | {ex: 400} | Texto normal |
-| `--font-medium` | {ex: 500} | Ênfase suave |
-| `--font-semibold` | {ex: 600} | Headings, labels |
-| `--font-bold` | {ex: 700} | Destaque forte |
+| `--font-regular` | {e.g.: 400} | Normal text |
+| `--font-medium` | {e.g.: 500} | Soft emphasis |
+| `--font-semibold` | {e.g.: 600} | Headings, labels |
+| `--font-bold` | {e.g.: 700} | Strong emphasis |
 
 ---
 
-## 3. Espaçamento
+## 3. Spacing
 
-| Token | Valor | Uso |
+| Token | Value | Usage |
 |:---|:---|:---|
-| `--spacing-xs` | {ex: 0.25rem (4px)} | Espaço mínimo |
-| `--spacing-sm` | {ex: 0.5rem (8px)} | Dentro de componentes |
-| `--spacing-md` | {ex: 1rem (16px)} | Entre elementos |
-| `--spacing-lg` | {ex: 1.5rem (24px)} | Entre seções |
-| `--spacing-xl` | {ex: 2rem (32px)} | Entre blocos |
-| `--spacing-2xl` | {ex: 3rem (48px)} | Entre seções maiores |
+| `--spacing-xs` | {e.g.: 0.25rem (4px)} | Minimum spacing |
+| `--spacing-sm` | {e.g.: 0.5rem (8px)} | Inside components |
+| `--spacing-md` | {e.g.: 1rem (16px)} | Between elements |
+| `--spacing-lg` | {e.g.: 1.5rem (24px)} | Between sections |
+| `--spacing-xl` | {e.g.: 2rem (32px)} | Between blocks |
+| `--spacing-2xl` | {e.g.: 3rem (48px)} | Between larger sections |
 
 ---
 
-## 4. Bordas e Sombras
+## 4. Borders and Shadows
 
 ### Border Radius
-| Token | Valor | Uso |
+| Token | Value | Usage |
 |:---|:---|:---|
-| `--radius-sm` | {ex: 4px} | Botões, inputs |
-| `--radius-md` | {ex: 8px} | Cards |
-| `--radius-lg` | {ex: 12px} | Modals, containers |
-| `--radius-full` | {ex: 9999px} | Avatars, badges |
+| `--radius-sm` | {e.g.: 4px} | Buttons, inputs |
+| `--radius-md` | {e.g.: 8px} | Cards |
+| `--radius-lg` | {e.g.: 12px} | Modals, containers |
+| `--radius-full` | {e.g.: 9999px} | Avatars, badges |
 
 ### Shadows
-| Token | Valor | Uso |
+| Token | Value | Usage |
 |:---|:---|:---|
-| `--shadow-sm` | {ex: 0 1px 2px rgba(0,0,0,0.05)} | Cards sutis |
-| `--shadow-md` | {ex: 0 4px 6px rgba(0,0,0,0.07)} | Cards elevados |
-| `--shadow-lg` | {ex: 0 10px 15px rgba(0,0,0,0.1)} | Modals, dropdowns |
+| `--shadow-sm` | {e.g.: 0 1px 2px rgba(0,0,0,0.05)} | Subtle cards |
+| `--shadow-md` | {e.g.: 0 4px 6px rgba(0,0,0,0.07)} | Elevated cards |
+| `--shadow-lg` | {e.g.: 0 10px 15px rgba(0,0,0,0.1)} | Modals, dropdowns |
 
 ---
 
-## 5. Componentes Base
+## 5. Base Components
 
-| Componente | Background | Padding | Radius | Shadow |
+| Component | Background | Padding | Radius | Shadow |
 |:---|:---|:---|:---|:---|
 | Card | `--color-surface` | `--spacing-lg` | `--radius-md` | `--shadow-sm` |
 | Button Primary | `--color-primary-500` | `--spacing-sm` `--spacing-md` | `--radius-sm` | none |
@@ -121,17 +121,17 @@ Use este template para gerar `.specs/standards/design-system.md`. Preencha com a
 
 ---
 
-## 6. Breakpoints (Responsividade)
+## 6. Breakpoints (Responsiveness)
 
-| Token | Valor | Dispositivo |
+| Token | Value | Device |
 |:---|:---|:---|
-| `--breakpoint-sm` | {ex: 640px} | Mobile landscape |
-| `--breakpoint-md` | {ex: 768px} | Tablet |
-| `--breakpoint-lg` | {ex: 1024px} | Desktop |
-| `--breakpoint-xl` | {ex: 1280px} | Desktop largo |
+| `--breakpoint-sm` | {e.g.: 640px} | Mobile landscape |
+| `--breakpoint-md` | {e.g.: 768px} | Tablet |
+| `--breakpoint-lg` | {e.g.: 1024px} | Desktop |
+| `--breakpoint-xl` | {e.g.: 1280px} | Wide desktop |
 ```
 
-## Regra para o Agente
+## Rule for the Agent
 
 > [!IMPORTANT]
-> Quando o design system está definido, o agente NUNCA deve usar valores hardcoded para cores, espaçamentos, tipografia ou border-radius. SEMPRE usar os tokens definidos neste documento.
+> When the design system is defined, the agent must NEVER use hardcoded values for colors, spacing, typography, or border-radius. ALWAYS use the tokens defined in this document.

package/sddk/skills/system-design-document/references/standards-naming-template.md

@@ -1,96 +1,96 @@
-# Template: Convenções de Nomenclatura do Projeto
+# Template: Project Naming Conventions
 
-Use este template para gerar `.specs/standards/naming-conventions.md`. Preencha com as respostas do onboarding.
+Use this template to generate `.specs/standards/naming-conventions.md`. Fill in with the onboarding interview answers.
 
 ```markdown
-# Convenções de Nomenclatura
+# Naming Conventions
 
-**Projeto**: {nome do projeto}
-**Última atualização**: {data}
+**Project**: {project name}
+**Last updated**: {date}
 
 ---
 
-## 1. Banco de Dados
+## 1. Database
 
-| Elemento | Convenção | Exemplo | Anti-exemplo |
+| Element | Convention | Example | Anti-example |
 |:---|:---|:---|:---|
-| Tabelas | {ex: snake_case, plural} | {ex: `auth_users`} | {ex: `User`, `authUser`} |
-| Colunas | {ex: snake_case, singular} | {ex: `first_name`} | {ex: `firstName`, `FirstName`} |
-| Primary Keys | {ex: `id` (UUID v4)} | {ex: `id`} | {ex: `user_id`, `ID`} |
-| Foreign Keys | {ex: `{tabela_singular}_id`} | {ex: `user_id`} | {ex: `fk_user`, `userId`} |
-| Índices | {ex: `idx_{tabela}_{colunas}`} | {ex: `idx_users_email`} | {ex: `index1`} |
-| Enums (valores) | {ex: UPPER_SNAKE_CASE} | {ex: `PENDING_PAYMENT`} | {ex: `pendingPayment`} |
-| Timestamps | {ex: `created_at`, `updated_at`} | — | {ex: `createdAt`, `date_created`} |
-| Soft delete | {ex: `deleted_at` nullable} | — | {ex: `is_deleted`} |
-| Booleanos | {ex: `is_` prefix} | {ex: `is_active`} | {ex: `active`, `status`} |
-
-### Prefixos de Módulo (se aplicável)
-| Módulo | Prefixo | Exemplo |
+| Tables | {e.g.: snake_case, plural} | {e.g.: `auth_users`} | {e.g.: `User`, `authUser`} |
+| Columns | {e.g.: snake_case, singular} | {e.g.: `first_name`} | {e.g.: `firstName`, `FirstName`} |
+| Primary Keys | {e.g.: `id` (UUID v4)} | {e.g.: `id`} | {e.g.: `user_id`, `ID`} |
+| Foreign Keys | {e.g.: `{singular_table}_id`} | {e.g.: `user_id`} | {e.g.: `fk_user`, `userId`} |
+| Indexes | {e.g.: `idx_{table}_{columns}`} | {e.g.: `idx_users_email`} | {e.g.: `index1`} |
+| Enums (values) | {e.g.: UPPER_SNAKE_CASE} | {e.g.: `PENDING_PAYMENT`} | {e.g.: `pendingPayment`} |
+| Timestamps | {e.g.: `created_at`, `updated_at`} | — | {e.g.: `createdAt`, `date_created`} |
+| Soft delete | {e.g.: `deleted_at` nullable} | — | {e.g.: `is_deleted`} |
+| Booleans | {e.g.: `is_` prefix} | {e.g.: `is_active`} | {e.g.: `active`, `status`} |
+
+### Module Prefixes (if applicable)
+| Module | Prefix | Example |
 |:---|:---|:---|
-| {ex: Autenticação} | {ex: `auth_`} | {ex: `auth_users`, `auth_sessions`} |
-| {ex: Pagamentos} | {ex: `pay_`} | {ex: `pay_transactions`} |
+| {e.g.: Authentication} | {e.g.: `auth_`} | {e.g.: `auth_users`, `auth_sessions`} |
+| {e.g.: Payments} | {e.g.: `pay_`} | {e.g.: `pay_transactions`} |
 
 ---
 
-## 2. Código ({linguagem})
+## 2. Code ({language})
 
-### Variáveis
+### Variables
 
-| Tipo | Convenção | Exemplo | Anti-exemplo |
+| Type | Convention | Example | Anti-example |
 |:---|:---|:---|:---|
-| Variáveis locais | {ex: camelCase} | {ex: `userName`} | {ex: `user_name`, `UserName`} |
-| Constantes | {ex: UPPER_SNAKE_CASE} | {ex: `MAX_RETRIES`} | {ex: `maxRetries`} |
-| Booleanos | {ex: prefixo is/has/can/should} | {ex: `isAuthenticated`} | {ex: `authenticated`, `auth`} |
-| Arrays/Coleções | {ex: plural} | {ex: `activeUsers`} | {ex: `userList`, `data`} |
+| Local variables | {e.g.: camelCase} | {e.g.: `userName`} | {e.g.: `user_name`, `UserName`} |
+| Constants | {e.g.: UPPER_SNAKE_CASE} | {e.g.: `MAX_RETRIES`} | {e.g.: `maxRetries`} |
+| Booleans | {e.g.: is/has/can/should prefix} | {e.g.: `isAuthenticated`} | {e.g.: `authenticated`, `auth`} |
+| Arrays/Collections | {e.g.: plural} | {e.g.: `activeUsers`} | {e.g.: `userList`, `data`} |
 
-### Funções
+### Functions
 
-| Tipo | Convenção | Exemplo | Anti-exemplo |
+| Type | Convention | Example | Anti-example |
 |:---|:---|:---|:---|
-| Funções gerais | {ex: verbo + substantivo, camelCase} | {ex: `calculateTotal`} | {ex: `calc`, `doStuff`} |
-| Handlers | {ex: handle + evento específico} | {ex: `handleLoginSubmit`} | {ex: `handleClick`} |
-| Getters | {ex: get + o quê} | {ex: `getUserOrders`} | {ex: `getData`} |
-| Validadores | {ex: is/validate + o quê} | {ex: `isValidEmail`} | {ex: `check`} |
-| Transformadores | {ex: formato + To + formato} | {ex: `dtoToEntity`} | {ex: `convert`} |
+| General functions | {e.g.: verb + noun, camelCase} | {e.g.: `calculateTotal`} | {e.g.: `calc`, `doStuff`} |
+| Handlers | {e.g.: handle + specific event} | {e.g.: `handleLoginSubmit`} | {e.g.: `handleClick`} |
+| Getters | {e.g.: get + what} | {e.g.: `getUserOrders`} | {e.g.: `getData`} |
+| Validators | {e.g.: is/validate + what} | {e.g.: `isValidEmail`} | {e.g.: `check`} |
+| Transformers | {e.g.: format + To + format} | {e.g.: `dtoToEntity`} | {e.g.: `convert`} |
 
-### Classes e Types
+### Classes and Types
 
-| Tipo | Convenção | Exemplo | Anti-exemplo |
+| Type | Convention | Example | Anti-example |
 |:---|:---|:---|:---|
-| Classes | {ex: PascalCase, substantivo} | {ex: `UserService`} | {ex: `userService`} |
-| Interfaces | {ex: PascalCase, sem prefixo I} | {ex: `UserProfile`} | {ex: `IUserProfile`} |
-| Types | {ex: PascalCase} | {ex: `OrderStatus`} | {ex: `TOrderStatus`} |
-| Enums | {ex: PascalCase singular} | {ex: `PaymentMethod`} | {ex: `PaymentMethods`} |
+| Classes | {e.g.: PascalCase, noun} | {e.g.: `UserService`} | {e.g.: `userService`} |
+| Interfaces | {e.g.: PascalCase, no I prefix} | {e.g.: `UserProfile`} | {e.g.: `IUserProfile`} |
+| Types | {e.g.: PascalCase} | {e.g.: `OrderStatus`} | {e.g.: `TOrderStatus`} |
+| Enums | {e.g.: PascalCase singular} | {e.g.: `PaymentMethod`} | {e.g.: `PaymentMethods`} |
 
-### Componentes (Frontend)
+### Components (Frontend)
 
-| Tipo | Convenção | Exemplo | Anti-exemplo |
+| Type | Convention | Example | Anti-example |
 |:---|:---|:---|:---|
-| Componentes | {ex: PascalCase, específico} | {ex: `ProductCard`} | {ex: `Card`} |
-| Hooks | {ex: use + contexto} | {ex: `useOrderData`} | {ex: `useData`} |
-| Context | {ex: PascalCase + Context} | {ex: `AuthContext`} | {ex: `ctx`} |
+| Components | {e.g.: PascalCase, specific} | {e.g.: `ProductCard`} | {e.g.: `Card`} |
+| Hooks | {e.g.: use + context} | {e.g.: `useOrderData`} | {e.g.: `useData`} |
+| Context | {e.g.: PascalCase + Context} | {e.g.: `AuthContext`} | {e.g.: `ctx`} |
 
 ---
 
-## 3. Arquivos e Diretórios
+## 3. Files and Directories
 
-| Tipo | Convenção | Exemplo |
+| Type | Convention | Example |
 |:---|:---|:---|
-| Componentes | {ex: PascalCase.tsx} | {ex: `ProductCard.tsx`} |
-| Hooks | {ex: camelCase.ts} | {ex: `useAuth.ts`} |
-| Utils | {ex: camelCase.ts} | {ex: `formatCurrency.ts`} |
-| Types | {ex: camelCase.ts} | {ex: `userTypes.ts`} |
-| Services | {ex: camelCase.service.ts} | {ex: `auth.service.ts`} |
-| Repositories | {ex: camelCase.repository.ts} | {ex: `user.repository.ts`} |
-| Migrations | {ex: NNN_descricao.sql} | {ex: `001_create_users.sql`} |
+| Components | {e.g.: PascalCase.tsx} | {e.g.: `ProductCard.tsx`} |
+| Hooks | {e.g.: camelCase.ts} | {e.g.: `useAuth.ts`} |
+| Utils | {e.g.: camelCase.ts} | {e.g.: `formatCurrency.ts`} |
+| Types | {e.g.: camelCase.ts} | {e.g.: `userTypes.ts`} |
+| Services | {e.g.: camelCase.service.ts} | {e.g.: `auth.service.ts`} |
+| Repositories | {e.g.: camelCase.repository.ts} | {e.g.: `user.repository.ts`} |
+| Migrations | {e.g.: NNN_description.sql} | {e.g.: `001_create_users.sql`} |
 
 ---
 
 ## 4. Git
 
-| Tipo | Convenção | Exemplo |
+| Type | Convention | Example |
 |:---|:---|:---|
-| Branches | {ex: tipo/descricao-curta} | {ex: `feat/user-auth`, `fix/login-redirect`} |
-| Commits | {ex: Conventional Commits} | {ex: `feat(auth): add login endpoint`} |
-| Tags | {ex: semver} | {ex: `v1.2.3`} |
+| Branches | {e.g.: type/short-description} | {e.g.: `feat/user-auth`, `fix/login-redirect`} |
+| Commits | {e.g.: Conventional Commits} | {e.g.: `feat(auth): add login endpoint`} |
+| Tags | {e.g.: semver} | {e.g.: `v1.2.3`} |
 ```

package/sddk/skills/system-design-document/references/standards-onboarding-guide.md

@@ -1,119 +1,119 @@
-# Guia de Onboarding de Padrões do Projeto
+# Project Standards Onboarding Guide
 
-## Propósito
+## Purpose
 
-Este guia instrui o agente a conduzir uma entrevista de onboarding para definir os padrões do projeto. Os padrões são salvos em `.specs/standards/` e funcionam como **memória estática persistente** — consultados por TODAS as features do projeto.
+This guide instructs the agent to conduct an onboarding interview to define the project's standards. Standards are saved in `.specs/standards/` and function as **persistent static memory** — consulted by ALL features in the project.
 
-## Quando Executar
+## When to Execute
 
-O onboarding é acionado pela **Skill SDD (Skill 2)** nos seguintes cenários:
+Onboarding is triggered by **Skill SDD (Skill 2)** in the following scenarios:
 
-| Cenário | Ação |
+| Scenario | Action |
 |:---|:---|
-| `.specs/standards/` **não existe** | Conduzir onboarding completo |
-| `.specs/standards/` **existe mas incompleto** | Perguntar se quer completar |
-| `.specs/standards/` **existe e completo** | Ler e respeitar, propor adições se necessário |
+| `.specs/standards/` **does not exist** | Conduct full onboarding |
+| `.specs/standards/` **exists but incomplete** | Ask if they want to complete it |
+| `.specs/standards/` **exists and complete** | Read and respect, propose additions if necessary |
 
-## Estrutura de Standards
+## Standards Structure
 
 ```
 .specs/
 └── standards/
-    ├── architecture.md           ← Padrões arquiteturais (DDD, CQRS, BFF, etc.)
-    ├── naming-conventions.md     ← Nomenclatura (funções, tabelas, variáveis)
-    ├── design-system.md          ← Tokens, paleta, tipografia, componentes
-    ├── api-conventions.md        ← Padrões de API (REST, GraphQL, error format)
-    └── coding-standards.md       ← Boas práticas e princípios (SSOT, DRY, etc.)
+    ├── architecture.md           ← Architectural patterns (DDD, CQRS, BFF, etc.)
+    ├── naming-conventions.md     ← Naming (functions, tables, variables)
+    ├── design-system.md          ← Tokens, palette, typography, components
+    ├── api-conventions.md        ← API patterns (REST, GraphQL, error format)
+    └── coding-standards.md       ← Best practices and principles (SSOT, DRY, etc.)
 ```
 
-## Fluxo do Onboarding
+## Onboarding Flow
 
-### Passo 1: Verificação
+### Step 1: Verification
 
-Verificar se `.specs/standards/` existe no projeto:
-- Se NÃO existe → prosseguir para Passo 2
-- Se existe → ler todos os arquivos e prosseguir diretamente para a entrevista técnica do SDD
+Check if `.specs/standards/` exists in the project:
+- If it DOES NOT exist → proceed to Step 2
+- If it exists → read all files and proceed directly to the SDD technical interview
 
-### Passo 2: Anúncio
+### Step 2: Announcement
 
-Anunciar ao usuário:
-> "Este projeto ainda não tem padrões definidos em `.specs/standards/`. Vou conduzir uma entrevista rápida para definir os padrões do projeto. Esses padrões serão usados como referência em TODAS as features futuras."
+Announce to the user:
+> "This project doesn't have standards defined in `.specs/standards/` yet. I'll conduct a quick interview to define the project standards. These standards will be used as a reference for ALL future features."
 
-### Passo 3: Entrevista por Categoria
+### Step 3: Interview by Category
 
-Para cada categoria, conduzir uma mini-entrevista via `ask_question`:
+For each category, conduct a mini-interview via `ask_question`:
 
-#### 3.1 Arquitetura
-Perguntas a fazer:
-1. "Qual padrão arquitetural o projeto segue?" (opções: MVC, Clean Architecture, DDD, Hexagonal, Feature-Based, ou descrever)
-2. "Usa algum padrão avançado?" (opções: Event Sourcing, CQRS, BFF, Microserviços, Monolito, ou descrever)
-3. "Qual a estrutura de camadas/módulos?"
-4. "Há regras de dependência entre camadas?" (ex: Domain nunca importa Infrastructure)
+#### 3.1 Architecture
+Questions to ask:
+1. "What architectural pattern does the project follow?" (options: MVC, Clean Architecture, DDD, Hexagonal, Feature-Based, or describe)
+2. "Does it use any advanced pattern?" (options: Event Sourcing, CQRS, BFF, Microservices, Monolith, or describe)
+3. "What is the layer/module structure?"
+4. "Are there dependency rules between layers?" (e.g.: Domain never imports Infrastructure)
 
-Gerar: `.specs/standards/architecture.md` usando template `references/standards-architecture-template.md`
+Generate: `.specs/standards/architecture.md` using template `references/standards-architecture-template.md`
 
-#### 3.2 Nomenclatura
-Perguntas a fazer:
-1. "Convenção para tabelas de banco?" (snake_case plural, PascalCase singular, etc.)
-2. "Convenção para colunas?" (snake_case, camelCase)
-3. "Convenção para chaves estrangeiras?" ({tabela}_id, fk_{tabela}, etc.)
-4. "Convenção para variáveis/funções JS/TS?" (camelCase, verbo+substantivo para funções)
-5. "Convenção para componentes React/Vue?" (PascalCase, kebab-case)
-6. "Convenção para arquivos?" (PascalCase para componentes, camelCase para utils, etc.)
+#### 3.2 Naming
+Questions to ask:
+1. "Convention for database tables?" (snake_case plural, PascalCase singular, etc.)
+2. "Convention for columns?" (snake_case, camelCase)
+3. "Convention for foreign keys?" ({table}_id, fk_{table}, etc.)
+4. "Convention for JS/TS variables/functions?" (camelCase, verb+noun for functions)
+5. "Convention for React/Vue components?" (PascalCase, kebab-case)
+6. "Convention for files?" (PascalCase for components, camelCase for utils, etc.)
 
-Gerar: `.specs/standards/naming-conventions.md` usando template `references/standards-naming-template.md`
+Generate: `.specs/standards/naming-conventions.md` using template `references/standards-naming-template.md`
 
-#### 3.3 Design System (se o projeto tem frontend)
-Perguntas a fazer:
-1. "O projeto tem design system definido?" (se sim, quais tokens)
-2. "Paleta de cores?" (primária, secundária, surface, error, etc.)
-3. "Tipografia?" (fonte principal, headings, sizes)
-4. "Espaçamentos?" (escala de spacing)
-5. "Border radius e shadows?" (tokens de forma)
-6. "Componentes base?" (Card, Button, Input — quais tokens usam)
+#### 3.3 Design System (if the project has frontend)
+Questions to ask:
+1. "Does the project have a defined design system?" (if yes, which tokens)
+2. "Color palette?" (primary, secondary, surface, error, etc.)
+3. "Typography?" (main font, headings, sizes)
+4. "Spacing?" (spacing scale)
+5. "Border radius and shadows?" (shape tokens)
+6. "Base components?" (Card, Button, Input — which tokens they use)
 
-Gerar: `.specs/standards/design-system.md` usando template `references/standards-design-system-template.md`
+Generate: `.specs/standards/design-system.md` using template `references/standards-design-system-template.md`
 
-Se não tem frontend, marcar como "N/A — projeto backend-only".
+If there's no frontend, mark as "N/A — backend-only project".
 
-#### 3.4 Convenções de API (se tem API)
-Perguntas a fazer:
-1. "Padrão de API?" (REST, GraphQL, tRPC, gRPC)
-2. "Formato de response?" (envelope `{data, error, meta}`, flat, etc.)
-3. "Versionamento de API?" (/v1/, header, query param)
-4. "Padrão de erro?" (HTTP status + body padronizado)
-5. "Paginação?" (cursor, offset, keyset)
-6. "Autenticação em API?" (Bearer token, cookie, API key)
+#### 3.4 API Conventions (if it has an API)
+Questions to ask:
+1. "API pattern?" (REST, GraphQL, tRPC, gRPC)
+2. "Response format?" (envelope `{data, error, meta}`, flat, etc.)
+3. "API versioning?" (/v1/, header, query param)
+4. "Error pattern?" (HTTP status + standardized body)
+5. "Pagination?" (cursor, offset, keyset)
+6. "API authentication?" (Bearer token, cookie, API key)
 
-Gerar: `.specs/standards/api-conventions.md` usando template `references/standards-api-template.md`
+Generate: `.specs/standards/api-conventions.md` using template `references/standards-api-template.md`
 
-#### 3.5 Boas Práticas e Princípios
-Perguntas a fazer:
-1. "Quais princípios o projeto adota?" (SSOT, DRY, KISS, YAGNI, SOLID — selecionar os relevantes)
-2. "Há regras de abstração?" (quando extrair função, componente, hook)
-3. "Tratamento de erros?" (custom exceptions, error boundary, etc.)
-4. "Logging?" (structured logging, níveis, o que logar)
-5. "Testes?" (estratégia, cobertura mínima, tipos de teste)
+#### 3.5 Best Practices and Principles
+Questions to ask:
+1. "Which principles does the project adopt?" (SSOT, DRY, KISS, YAGNI, SOLID — select relevant ones)
+2. "Are there abstraction rules?" (when to extract function, component, hook)
+3. "Error handling?" (custom exceptions, error boundary, etc.)
+4. "Logging?" (structured logging, levels, what to log)
+5. "Testing?" (strategy, minimum coverage, test types)
 
-Gerar: `.specs/standards/coding-standards.md` usando template `references/standards-coding-template.md`
+Generate: `.specs/standards/coding-standards.md` using template `references/standards-coding-template.md`
 
-### Passo 4: Apresentação
+### Step 4: Presentation
 
-1. Apresentar resumo de todos os padrões definidos
-2. Perguntar: "Os padrões estão corretos? Deseja ajustar algo?"
-3. Salvar todos os arquivos em `.specs/standards/`
+1. Present a summary of all defined standards
+2. Ask: "Are the standards correct? Would you like to adjust anything?"
+3. Save all files to `.specs/standards/`
 
-### Passo 5: Continuar para SDD
+### Step 5: Continue to SDD
 
-Após o onboarding, prosseguir normalmente com a Fase 1 do SDD (Análise do Contexto).
+After onboarding, proceed normally with Phase 1 of the SDD (Context Analysis).
 
 ---
 
-## Evolução Incremental
+## Incremental Evolution
 
-Durante SDDs de features futuras, o agente pode propor adições aos standards:
+During SDDs of future features, the agent may propose additions to standards:
 
-1. Se uma decisão técnica nova não está coberta pelos standards existentes
-2. Perguntar: "Essa decisão deve virar um padrão do projeto para futuras features?"
-3. Se sim, atualizar o arquivo de standards relevante
-4. Se não, documentar apenas no SDD da feature
+1. If a new technical decision is not covered by existing standards
+2. Ask: "Should this decision become a project standard for future features?"
+3. If yes, update the relevant standards file
+4. If no, document only in the feature's SDD