@ggailabs/cli-context 0.5.6 → 1.0.1

package/dist/.context/pt-br/skills/patterns/compliance_check.md

@@ -0,0 +1,246 @@
+# Standards Compliance Mode Detection
+
+Canonical source for Standards Compliance detection logic used by all dev-team agents.
+
+---
+
+## ⛔ CRITICAL: Standards Compliance is always Required for Implementation
+
+**Standards Compliance is not optional. It is MANDATORY for all implementation agents.**
+
+| Context | Standards Compliance | Rationale |
+|---------|---------------------|-----------|
+| **Implementation (TDD-GREEN)** | **always REQUIRED** | Agent MUST output Standards Coverage Table |
+| **Analysis (MODE: ANALYSIS only)** | **always REQUIRED** | Agent MUST output Standards Coverage Table + Findings |
+| **Validation (SRE, QA)** | **always REQUIRED** | Agent MUST verify against standards |
+
+**There is no context where an implementation agent can skip Standards Compliance.**
+
+---
+
+## Trigger Conditions
+
+### always Required (Implementation Context)
+
+**These agents MUST always output Standards Coverage Table:**
+
+| Agent | Standards File | When |
+|-------|---------------|------|
+| `genesis:backend-engineer-golang` | golang.md | any implementation task |
+| `genesis:backend-engineer-typescript` | typescript.md | any implementation task |
+| `frontend-bff-engineer-typescript` | typescript.md | any implementation task |
+| `genesis:frontend-engineer` | frontend.md | any implementation task |
+| `genesis:devops-engineer` | devops.md | any artifact creation |
+| `genesis:sre` | sre.md | any validation task |
+| `genesis:qa-analyst` | golang.md/typescript.md | any testing task |
+
+**⛔ HARD GATE:** If agent does not output Standards Coverage Table → Output is INCOMPLETE → Orchestrator MUST re-dispatch.
+
+### Additional Triggers (Analysis Context)
+
+These patterns trigger **detailed findings** in addition to Standards Coverage Table:
+
+| Detection Pattern | Examples |
+|------------------|----------|
+| Exact match | `**MODE: ANALYSIS only**` |
+| Case variations | `MODE: Analysis Only`, `mode: analysis only`, `**mode: ANALYSIS only**` |
+| Partial markers | `ANALYSIS MODE`, `analysis-only`, `analyze only`, `MODE ANALYSIS` |
+| Context clues | Invoked from `genesis:dev-refactor` skill |
+| Explicit request | "compare against standards", "audit compliance", "check against Ring standards" |
+
+## Detection Logic
+
+```python
+def get_standards_compliance_mode(prompt: str, context: dict) -> str:
+    """
+    Returns:
+    - "FULL": Standards Coverage Table + Detailed Findings (analysis mode)
+    - "TABLE_ONLY": Standards Coverage Table only (implementation mode)
+    - "TABLE_ONLY" is the MINIMUM - never returns "NONE"
+    """
+    # Analysis mode patterns
+    analysis_patterns = [
+        "mode: analysis only",
+        "analysis mode",
+        "analysis-only",
+        "analyze only",
+        "compare against standards",
+        "audit compliance",
+        "check against ring"
+    ]
+    prompt_lower = prompt.lower()
+
+    # Check for analysis mode
+    if any(p in prompt_lower for p in analysis_patterns):
+        return "FULL"
+
+    # Check invocation context
+    if context.get("invocation_source") == "genesis:dev-refactor":
+        return "FULL"
+
+    # Default: TABLE_ONLY (Standards Coverage Table is always required)
+    return "TABLE_ONLY"
+```
+
+## When Uncertain
+
+If detection is ambiguous, output FULL compliance (table + findings). Better to over-report than under-report.
+
+## When Mode is Detected, Agent MUST
+
+1. **WebFetch** the Ring standards file for their language/domain
+2. **Read** `docs/PROJECT_RULES.md` if it exists in the target codebase
+3. **Include** a `## Standards Compliance` section in output with comparison table
+4. **CANNOT skip** - this is a HARD GATE, not optional
+
+## MANDATORY Output Table Format
+
+```markdown
+| Category | Current Pattern | Ring Standard | Status | File/Location |
+|----------|----------------|---------------|--------|---------------|
+| [category] | [what codebase does] | [what standard requires] | ✅/⚠️/❌ | [file:line] |
+```
+
+## Status Legend
+
+- ✅ Compliant - Matches Ring standard
+- ⚠️ Partial - Some compliance, needs improvement
+- ❌ Non-Compliant - Does not follow standard
+- N/A - Not applicable (with reason)
+
+## Standards Coverage Table (genesis:dev-refactor context)
+
+**Detection:** This section applies when prompt contains `**MODE: ANALYSIS only**`
+
+**Inputs (provided by genesis:dev-refactor):**
+
+| Input | Source | Contains |
+|-------|--------|----------|
+| Ring Standards | WebFetch | Sections to check (## headers) |
+| codebase-report.md | Provided path | Current architecture, patterns, code snippets |
+| PROJECT_RULES.md | Provided path | Project-specific conventions |
+
+**Outputs (expected by genesis:dev-refactor):**
+1. Standards Coverage Table (every section enumerated)
+2. Detailed findings in FINDING-XXX format for ⚠️/❌ items
+
+**HARD GATE:** When invoked from genesis:dev-refactor skill, before outputting detailed findings, you MUST output a Standards Coverage Table.
+
+**Process:**
+1. **Parse the WebFetch result** - Extract all `## Section` headers from standards file
+2. **Count total sections found** - Record the number
+3. **For each section** - Determine status (✅ Compliant, ⚠️ Partial, ❌ Non-Compliant, or N/A with reason)
+4. **Output table** - MUST have one row per section
+5. **Verify completeness** - Table rows MUST equal sections found
+
+---
+
+## ⛔ CRITICAL: Section Names MUST Match Coverage Table EXACTLY
+
+**You MUST use section names from `standards-coverage-table.md`. You CANNOT invent your own.**
+
+### FORBIDDEN Actions
+
+```
+❌ Inventing section names ("Security", "Go Version", "Code Quality")
+❌ Merging sections ("Error Handling & Logging" instead of separate rows)
+❌ Renaming sections ("Config" instead of "Configuration Loading")
+❌ Skipping sections not found in codebase
+❌ Adding sections not in coverage table
+```
+
+### REQUIRED Actions
+
+```
+✅ Use EXACT section names from standards-coverage-table.md
+✅ Output all sections listed in coverage table for your agent type
+✅ Mark missing/not-applicable sections as "N/A" with reason
+✅ One row per section - no merging
+```
+
+### Section Name Validation
+
+**For golang.md, section names MUST be:**
+- Version, Core Dependency: lib-commons, Frameworks & Libraries, Configuration Loading, Telemetry & Observability, Bootstrap Pattern, Data Transformation: ToEntity/FromEntity, Error Codes Convention, Error Handling, Function Design, Pagination Patterns, Testing Patterns, Logging Standards, Linting, Architecture Patterns, Directory Structure, Concurrency Patterns, RabbitMQ Worker Pattern
+
+**not:**
+- ❌ "Error Handling" (missing "Error Codes Convention" as separate row)
+- ❌ "Logging" (should be "Logging Standards")
+- ❌ "Configuration" (should be "Configuration Loading")
+- ❌ "Security" (not a section in golang.md)
+- ❌ "Bootstrap" (should be "Bootstrap Pattern")
+
+### Anti-Rationalization for Section Names
+
+| Rationalization | Why It's WRONG | Required Action |
+|-----------------|----------------|-----------------|
+| "My section name is clearer" | Consistency > clarity. Coverage table is the contract. | **Use EXACT names from coverage table** |
+| "I combined related sections" | Each section = one row. Merging loses traceability. | **One row per section, no merging** |
+| "This section doesn't apply" | Report as N/A with reason. Never skip silently. | **Include row with N/A status** |
+| "I added a useful section" | You don't decide sections. Coverage table does. | **Only sections from coverage table** |
+| "The codebase uses different terminology" | Standards use Ring terminology. Map codebase terms to standard terms. | **Use standard section names** |
+
+## MANDATORY: Quote Standards from WebFetch in Findings
+
+**For every ⚠️ Partial or ❌ Non-Compliant finding, you MUST:**
+
+1. **Quote the codebase pattern** from codebase-report.md (what exists)
+2. **Quote the Ring standard** from WebFetch result (what's expected)
+3. **Explain the gap** (what needs improvement)
+
+**Output Format for Non-Compliant Findings:**
+
+```markdown
+### FINDING: [Category Name]
+
+**Status:** ⚠️ Partial / ❌ Non-Compliant
+**Location:** [file:line from codebase-report.md]
+**Severity:** CRITICAL / HIGH / MEDIUM / LOW
+
+**Current (from codebase-report.md):**
+[Quote the actual code/pattern from codebase-report.md]
+
+**Expected (from Ring Standard):**
+[Quote the relevant code/pattern from WebFetch result]
+
+**Gap Analysis:**
+- What is different
+- What needs to be improved
+- Standard reference: {standards-file}.md → [Section Name]
+```
+
+**⛔ HARD GATE: You MUST quote from BOTH sources (codebase-report.md and WebFetch result).**
+
+## Anti-Rationalization
+
+See [shared-anti-rationalization.md](shared-anti-rationalization.md) for universal agent anti-rationalizations.
+
+| Rationalization | Why It's WRONG | Required Action |
+|-----------------|----------------|-----------------|
+| "Detection wasn't exact match" | Partial matches and context clues count. | **Include Standards Compliance section** |
+| "Codebase already compliant" | Assumption ≠ verification. Check every section. | **Output full Standards Coverage Table** |
+| "Only relevant sections matter" | You don't decide relevance. Standards file does. | **Check all ## sections from WebFetch** |
+| "Summary is enough" | Detailed quotes are MANDATORY for findings. | **Quote from BOTH sources** |
+| "WebFetch failed, skip compliance" | STOP and report blocker. Cannot proceed without standards. | **Report blocker, DO NOT skip** |
+
+## How to Reference This File
+
+Agents should include:
+
+```markdown
+## Standards Compliance (always REQUIRED)
+
+See [shared-patterns/standards-compliance-detection.md](../skills/shared-patterns/standards-compliance-detection.md) for:
+- Standards Compliance is MANDATORY for all implementation agents
+- MANDATORY output table format (Standards Coverage Table)
+- Additional findings format for analysis mode
+- Anti-rationalization rules
+
+**Agent-Specific Standards:**
+- WebFetch URL: `https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/{file}.md`
+- Sections to check: See [standards-coverage-table.md](../skills/shared-patterns/standards-coverage-table.md)
+
+**⛔ Standards Coverage Table is always required. No exceptions.**
+- Implementation mode: Output Standards Coverage Table
+- Analysis mode: Output Standards Coverage Table + Detailed Findings
+```

package/dist/.context/pt-br/skills/patterns/coverage_table.md

@@ -0,0 +1,401 @@
+# Standards Coverage Table Pattern
+
+This file defines the MANDATORY output format for agents comparing codebases against Ring standards. It ensures every section in the standards is explicitly checked and reported.
+
+---
+
+## ⛔ CRITICAL: All Sections Are Required
+
+**This is NON-NEGOTIABLE. Every section listed in the Agent → Standards Section Index below MUST be checked.**
+
+| Rule | Enforcement |
+|------|-------------|
+| **Every section MUST be checked** | No exceptions. No skipping. |
+| **Every section MUST appear in output table** | Missing row = INCOMPLETE output |
+| **Subsections are INCLUDED** | If "Containers" is listed, all content (Dockerfile, Docker Compose) MUST be checked |
+| **N/A requires explicit reason** | Cannot mark N/A without justification |
+
+**If you skip any section → Your output is REJECTED. Start over.**
+
+**If you invent section names → Your output is REJECTED. Start over.**
+
+---
+
+## ⛔ CRITICAL: Section Names Are Not Negotiable
+
+**You MUST use the EXACT section names from this file. You CANNOT:**
+
+| FORBIDDEN | Example | Why Wrong |
+|-----------|---------|-----------|
+| Invent names | "Security", "Code Quality" | Not in coverage table |
+| Rename sections | "Config" instead of "Configuration Loading" | Breaks traceability |
+| Merge sections | "Error Handling & Logging" | Each section = one row |
+| Use abbreviations | "Bootstrap" instead of "Bootstrap Pattern" | Must match exactly |
+| Skip sections | Omitting "RabbitMQ Worker Pattern" | Mark N/A instead |
+
+**Your output table section names MUST match the "Section to Check" column below EXACTLY.**
+
+---
+
+## Why This Pattern Exists
+
+**Problem:** Agents might skip sections from standards files, either by:
+- Only checking "main" sections
+- Assuming some sections don't apply
+- Not enumerating all sections systematically
+- Skipping subsections (e.g., checking Dockerfile but skipping Docker Compose)
+
+**Solution:** Require a completeness table that MUST list every section from the WebFetch result with explicit status. All content within each section MUST be evaluated.
+
+---
+
+## MANDATORY: Standards Coverage Table
+
+### ⛔ HARD GATE: Before Outputting Findings
+
+**You MUST output a Standards Coverage Table that enumerates every section from the WebFetch result.**
+
+**REQUIRED: When checking a section, you MUST check all subsections and patterns within it.**
+
+| Section | What MUST Be Checked |
+|---------|---------------------|
+| Containers | Dockerfile patterns and Docker Compose patterns |
+| Infrastructure as Code | Terraform structure and state management and modules |
+| Observability | Logging and Tracing (structured JSON logs, OpenTelemetry spans) |
+| Security | Secrets management and Network policies |
+
+### Process
+
+1. **Parse the WebFetch result** - Extract all `## Section` headers from the standards file
+2. **Count sections** - Record total number of sections found
+3. **For each section** - Determine status and evidence
+4. **Output table** - MUST have one row per section
+5. **Verify completeness** - Table row count MUST equal section count
+
+### Output Format
+
+```markdown
+## Standards Coverage Table
+
+**Standards File:** {filename}.md (from WebFetch)
+**Total Sections Found:** {N}
+**Table Rows:** {N} (MUST match)
+
+| # | Section (from WebFetch) | Status | Evidence |
+|---|-------------------------|--------|----------|
+| 1 | {Section 1 header} | ✅/⚠️/❌/N/A | file:line or reason |
+| 2 | {Section 2 header} | ✅/⚠️/❌/N/A | file:line or reason |
+| ... | ... | ... | ... |
+| N | {Section N header} | ✅/⚠️/❌/N/A | file:line or reason |
+
+**Completeness Verification:**
+- Sections in standards: {N}
+- Rows in table: {N}
+- Status: ✅ Complete / ❌ Incomplete
+```
+
+### Status Legend
+
+| Status | Meaning | When to Use |
+|--------|---------|-------------|
+| ✅ Compliant | Codebase follows this standard | Code matches expected pattern |
+| ⚠️ Partial | Some compliance, needs improvement | Partially implemented or minor gaps |
+| ❌ Non-Compliant | Does not follow standard | Missing or incorrect implementation |
+| N/A | Not applicable to this codebase | Standard doesn't apply (with reason) |
+
+---
+
+## ⛔ CRITICAL: Standards Boundary Enforcement
+
+**You MUST check only what the standards file explicitly defines. Never invent requirements.**
+
+See [shared-patterns/standards-boundary-enforcement.md](standards-boundary-enforcement.md) for:
+- Complete list of what IS and IS not required per agent
+- Agent-specific requirement boundaries
+- Self-verification checklist
+
+**⛔ HARD GATE:** Before flagging any item as non-compliant:
+1. Verify the requirement EXISTS in the WebFetch result
+2. Quote the EXACT standard that requires it
+3. If you cannot quote it → Do not flag it
+
+---
+
+## Anti-Rationalization Table
+
+| Rationalization | Why It's WRONG | Required Action |
+|-----------------|----------------|-----------------|
+| "I checked the important sections" | You don't decide importance. All sections MUST be checked. | **List every section in table** |
+| "Some sections obviously don't apply" | Report them as N/A with reason. Never skip silently. | **Include in table with N/A status** |
+| "The table would be too long" | Completeness > brevity. Every section MUST be visible. | **Output full table regardless of length** |
+| "I already mentioned these in findings" | Findings ≠ Coverage table. Both are REQUIRED. | **Output table BEFORE detailed findings** |
+| "WebFetch result was unclear" | Parse all `## ` headers. If truly unclear, STOP and report blocker. | **Report blocker or parse all headers** |
+| "I checked Dockerfile, that covers Containers" | Containers = Dockerfile + Docker Compose. Partial ≠ Complete. | **Check all subsections within each section** |
+| "Project doesn't use Docker Compose" | Report as N/A with evidence. Never assume. VERIFY first. | **Search for docker-compose.yml, report finding** |
+| "Only checking what exists in codebase" | Standards define what SHOULD exist. Missing = Non-Compliant. | **Report missing patterns as ❌ Non-Compliant** |
+| "My section name is clearer" | Consistency > clarity. Coverage table names are the contract. | **Use EXACT names from coverage table** |
+| "I combined related sections for brevity" | Each section = one row. Merging loses traceability. | **One row per section, no merging** |
+| "I added a useful section like 'Security'" | You don't decide sections. Coverage table does. | **Only output sections from coverage table** |
+| "'Logging' is the same as 'Logging Standards'" | Names must match EXACTLY. Variations break automation. | **Use exact string from coverage table** |
+
+---
+
+## Completeness Check (SELF-VERIFICATION)
+
+**Before submitting output, verify:**
+
+```text
+1. Did I extract all ## headers from WebFetch result?     [ ]
+2. Does my table have exactly that many rows?             [ ]
+3. Does every row have a status (✅/⚠️/❌/N/A)?           [ ]
+4. Does every ⚠️/❌ have evidence (file:line)?           [ ]
+5. Does every N/A have a reason?                         [ ]
+
+If any checkbox is unchecked → FIX before submitting.
+```
+
+---
+
+## Integration with Findings
+
+**Order of output:**
+
+1. **Standards Coverage Table** (this pattern) - Shows completeness
+2. **Detailed Findings** - Only for ⚠️ Partial and ❌ Non-Compliant items
+
+The Coverage Table ensures nothing is skipped. The Detailed Findings provide actionable information for gaps.
+
+---
+
+## Example Output
+
+```markdown
+## Standards Coverage Table
+
+**Standards File:** golang.md (from WebFetch)
+**Total Sections Found:** 21
+**Table Rows:** 21 (MUST match)
+
+| # | Section (from WebFetch) | Status | Evidence |
+|---|-------------------------|--------|----------|
+| 1 | Version | ✅ | go.mod:3 (Go 1.24) |
+| 2 | Core Dependency: lib-commons | ✅ | go.mod:5 |
+| 3 | Frameworks & Libraries | ✅ | Fiber v2, pgx/v5 in go.mod |
+| 4 | Configuration Loading | ⚠️ | internal/config/config.go:12 |
+| 5 | Telemetry & Observability | ❌ | Not implemented |
+| 6 | Bootstrap Pattern | ✅ | cmd/server/main.go:15 |
+| 7 | Access Manager Integration | ✅ | internal/middleware/auth.go:25 |
+| 8 | License Manager Integration | N/A | Not a licensed project |
+| 9 | Data Transformation | ✅ | internal/adapters/postgres/mapper.go:8 |
+| 10 | Error Codes Convention | ⚠️ | Uses generic codes |
+| 11 | Error Handling | ✅ | Consistent pattern |
+| 12 | Function Design | ✅ | Small functions, clear names |
+| 13 | Pagination Patterns | N/A | No list endpoints |
+| 14 | Testing Patterns | ❌ | No tests found |
+| 15 | Logging Standards | ⚠️ | Missing structured fields |
+| 16 | Linting | ✅ | .golangci.yml present |
+| 17 | Architecture Patterns | ✅ | Hexagonal structure |
+| 18 | Directory Structure | ✅ | Follows Lerian pattern |
+| 19 | Concurrency Patterns | N/A | No concurrent code |
+| 20 | RabbitMQ Worker Pattern | N/A | No message queue |
+
+**Completeness Verification:**
+- Sections in standards: 20
+- Rows in table: 20
+- Status: ✅ Complete
+```
+
+---
+
+## How Agents Reference This Pattern
+
+Agents MUST include this in their Standards Compliance section:
+
+```markdown
+## Standards Compliance Output (Conditional)
+
+**Detection:** Prompt contains `**MODE: ANALYSIS only**`
+
+**When triggered, you MUST:**
+1. Output Standards Coverage Table per [shared-patterns/standards-coverage-table.md](../skills/shared-patterns/standards-coverage-table.md)
+2. Then output detailed findings for ⚠️/❌ items
+
+See [shared-patterns/standards-coverage-table.md](../skills/shared-patterns/standards-coverage-table.md) for:
+- Table format
+- Status legend
+- Anti-rationalization rules
+- Completeness verification checklist
+```
+
+---
+
+## Agent → Standards Section Index
+
+**IMPORTANT:** When updating a standards file, you MUST also update the corresponding section index below.
+
+**Meta-sections (EXCLUDED from agent checks):**
+Standards files may contain these meta-sections that are not counted in section indexes:
+- `## Checklist` - Self-verification checklist for developers
+- `## Standards Compliance` - Output format examples for agents
+- `## Standards Compliance Output Format` - Output templates
+
+These sections describe HOW to use the standards, not WHAT the standards are.
+
+### genesis:backend-engineer-golang → golang.md
+
+| # | Section to Check | Anchor | Key Subsections |
+|---|------------------|--------|-----------------|
+| 1 | Version | `#version` | Go 1.24+ |
+| 2 | Core Dependency: lib-commons | `#core-dependency-lib-commons-mandatory` | |
+| 3 | Frameworks & Libraries | `#frameworks--libraries` | lib-commons v2, Fiber v2, pgx/v5, OpenTelemetry, zap, testify, gomock |
+| 4 | Configuration | `#configuration` | Environment variable handling |
+| 5 | Observability | `#observability` | OpenTelemetry integration |
+| 6 | Bootstrap | `#bootstrap` | Application initialization |
+| 7 | Access Manager Integration | `#access-manager-integration-mandatory` | **CONDITIONAL** - Check if project has auth |
+| 8 | License Manager Integration | `#license-manager-integration-mandatory` | **CONDITIONAL** - Check if project is licensed |
+| 9 | Data Transformation | `#data-transformation-toentityfromentity-mandatory` | ToEntity/FromEntity patterns |
+| 10 | Error Codes Convention | `#error-codes-convention-mandatory` | Service-prefixed codes |
+| 11 | Error Handling | `#error-handling` | Error wrapping and checking |
+| 12 | Function Design | `#function-design-mandatory` | Single responsibility |
+| 13 | Pagination Patterns | `#pagination-patterns` | Cursor and page-based |
+| 14 | Testing | `#testing` | Table-driven tests, edge cases |
+| 15 | Logging | `#logging` | Structured logging with lib-commons |
+| 16 | Linting | `#linting` | golangci-lint configuration |
+| 17 | Architecture Patterns | `#architecture-patterns` | Hexagonal architecture |
+| 18 | Directory Structure | `#directory-structure` | Lerian pattern |
+| 19 | Concurrency Patterns | `#concurrency-patterns` | Goroutines, channels, errgroup |
+| 20 | RabbitMQ Worker Pattern | `#rabbitmq-worker-pattern` | Async message processing |
+| 21 | Always-Valid Domain Model | `#always-valid-domain-model-mandatory` | Constructor validation, invariant protection |
+
+---
+
+### genesis:backend-engineer-typescript → typescript.md
+
+| # | Section to Check | Anchor | Key Subsections |
+|---|------------------|--------|-----------------|
+| 1 | Version | `#version` | TypeScript 5.0+, Node.js 20+ |
+| 2 | Strict Configuration | `#strict-configuration-mandatory` | tsconfig.json strict mode |
+| 3 | Frameworks & Libraries | `#frameworks--libraries` | Express, Fastify, NestJS, Prisma, Zod, Vitest |
+| 4 | Type Safety | `#type-safety` | No any, branded types, discriminated unions |
+| 5 | Zod Validation Patterns | `#zod-validation-patterns` | Schema validation |
+| 6 | Dependency Injection | `#dependency-injection` | TSyringe patterns |
+| 7 | AsyncLocalStorage for Context | `#asynclocalstorage-for-context` | Request context propagation |
+| 8 | Testing | `#testing` | Type-safe mocks, fixtures, edge cases |
+| 9 | Error Handling | `#error-handling` | Custom error classes |
+| 10 | Function Design | `#function-design-mandatory` | Single responsibility |
+| 11 | Naming Conventions | `#naming-conventions` | Files, interfaces, types |
+| 12 | Directory Structure | `#directory-structure` | Lerian pattern |
+| 13 | RabbitMQ Worker Pattern | `#rabbitmq-worker-pattern` | Async message processing |
+| 14 | Always-Valid Domain Model | `#always-valid-domain-model-mandatory` | Constructor validation, invariant protection |
+
+---
+
+### frontend-bff-engineer-typescript → typescript.md
+
+**Same sections as genesis:backend-engineer-typescript (14 sections).** See above.
+
+---
+
+### genesis:frontend-engineer → frontend.md
+
+| # | Section to Check | Anchor |
+|---|------------------|--------|
+| 1 | Framework | `#framework` |
+| 2 | Libraries & Tools | `#libraries--tools` |
+| 3 | State Management Patterns | `#state-management-patterns` |
+| 4 | Form Patterns | `#form-patterns` |
+| 5 | Styling Standards | `#styling-standards` |
+| 6 | Typography Standards | `#typography-standards` |
+| 7 | Animation Standards | `#animation-standards` |
+| 8 | Component Patterns | `#component-patterns` |
+| 9 | Accessibility | `#accessibility` |
+| 10 | Performance | `#performance` |
+| 11 | Directory Structure | `#directory-structure` |
+| 12 | Forbidden Patterns | `#forbidden-patterns` |
+| 13 | Standards Compliance Categories | `#standards-compliance-categories` |
+
+---
+
+### genesis:frontend-designer → frontend.md
+
+**Same sections as genesis:frontend-engineer (13 sections).** See above.
+
+---
+
+### genesis:devops-engineer → devops.md
+
+| # | Section to Check | Subsections (all REQUIRED) |
+|---|------------------|---------------------------|
+| 1 | Cloud Provider (MANDATORY) | Provider table |
+| 2 | Infrastructure as Code (MANDATORY) | Terraform structure, State management, Module pattern, Best practices |
+| 3 | Containers (MANDATORY) | **Dockerfile patterns, Docker Compose (Local Dev), .env file**, Image guidelines |
+| 4 | Helm (MANDATORY) | Chart structure, Chart.yaml, values.yaml |
+| 5 | Observability (MANDATORY) | Logging (Structured JSON), Tracing (OpenTelemetry) |
+| 6 | Security (MANDATORY) | Secrets management, Network policies |
+| 7 | Makefile Standards (MANDATORY) | Required commands (build, lint, test, cover, up, down, etc.), Component delegation pattern |
+
+**⛔ HARD GATE:** When checking "Containers", you MUST verify BOTH Dockerfile and Docker Compose patterns. Checking only one = INCOMPLETE.
+
+**⛔ HARD GATE:** When checking "Makefile Standards", you MUST verify all required commands exist: `build`, `lint`, `test`, `cover`, `up`, `down`, `start`, `stop`, `restart`, `rebuild-up`, `set-env`, `generate-docs`.
+
+---
+
+### genesis:sre → sre.md
+
+| # | Section to Check | Anchor |
+|---|------------------|--------|
+| 1 | Observability | `#observability` |
+| 2 | Logging | `#logging` |
+| 3 | Tracing | `#tracing` |
+| 4 | OpenTelemetry with lib-commons | `#opentelemetry-with-lib-commons-mandatory-for-go` |
+| 5 | Structured Logging with lib-common-js | `#structured-logging-with-lib-common-js-mandatory-for-typescript` |
+| 6 | Health Checks | `#health-checks` |
+
+---
+
+### genesis:qa-analyst → golang.md or typescript.md
+
+**Note:** genesis:qa-analyst checks testing-related sections based on project language.
+
+**For Go projects:**
+| # | Section to Check |
+|---|------------------|
+| 1 | Testing Patterns (MANDATORY) |
+| 2 | Edge Case Coverage (MANDATORY) |
+| 3 | Test Naming Convention (MANDATORY) |
+| 4 | Linting (MANDATORY) |
+
+**For TypeScript projects:**
+| # | Section to Check |
+|---|------------------|
+| 1 | Testing Patterns (MANDATORY) |
+| 2 | Edge Case Coverage (MANDATORY) |
+| 3 | Type Safety Rules (MANDATORY) |
+
+**Test Quality Gate Checks (Gate 3 Exit - all REQUIRED):**
+| # | Check | Detection |
+|---|-------|-----------|
+| 1 | Skipped tests | `grep -rn "\.skip\|\.todo\|xit"` = 0 |
+| 2 | Assertion-less tests | All tests have expect/assert |
+| 3 | Shared state | No beforeAll DB/state mutation |
+| 4 | Edge cases | ≥2 per acceptance criterion |
+| 5 | TDD evidence | RED phase captured |
+| 6 | Test isolation | No order dependency |
+
+---
+
+## Maintenance Instructions
+
+**When you add/modify a section in a standards file:**
+
+1. Edit `dev-team/docs/standards/{file}.md` - Add your new `## Section Name`
+2. Edit THIS file - Add the section to the corresponding agent table above
+3. Verify row count matches section count
+
+**Anti-Rationalization:**
+
+| Rationalization | Why It's WRONG | Required Action |
+|-----------------|----------------|-----------------|
+| "I'll update the index later" | Later = never. Sync drift causes missed checks. | **Update BOTH files in same commit** |
+| "The section is minor" | Minor ≠ optional. All sections must be indexed. | **Add to index regardless of size** |
+| "Agents parse dynamically anyway" | Index is the explicit contract. Dynamic is backup. | **Index is source of truth** |

package/dist/.context/pt-br/skills/patterns/exit_criteria.md

@@ -0,0 +1,31 @@
+# Universal Exit Criteria Pattern
+
+Add this section to define clear completion:
+
+## Definition of Done
+
+You may ONLY claim completion when:
+
+□ All checklist items complete
+□ Verification commands run and passed
+□ Output evidence included in response
+□ No "should" or "probably" in message
+□ State tracking shows all phases done
+□ No unresolved blockers
+
+**Incomplete checklist = not done**
+
+Example claim structure:
+```
+Status: Task complete
+
+Evidence:
+- Tests: 15/15 passing [output shown above]
+- Lint: No errors [output shown above]
+- Build: Success [output shown above]
+- All requirements met [checklist verified]
+
+The implementation is complete and verified.
+```
+
+**Never claim done without this structure.**