Files

Cassel 647cbec54f docs: update all documentation and add AI tooling configs

- Rewrite README.md with current architecture, features and stack
- Update docs/API.md with all current endpoints (corporate, BI, client 360)
- Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL
- Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente)
- Add docs/INDEX.md documentation index
- Add PROJETO.md comprehensive project reference
- Add BI-CCC-Implementation-Guide.md
- Include AI agent configs (.claude, .agents, .gemini, _bmad)
- Add netbird VPN configuration
- Add status report

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-19 13:29:03 -04:00

2.1 KiB

Raw Blame History

name, description

name	description
bugfixing	Fix bugs in existing code through structured investigation and verification

[F] Bugfixing — Fix Bugs in Existing Code

Goal: Systematically investigate, fix, and verify bugs with minimal side effects.

When to use: A bug has been reported or discovered in existing code.

CORE PRINCIPLES

Reproduce first — Never fix what you cannot reproduce. A fix without reproduction is a guess.
Minimal fix — Target the root cause with the smallest change possible. Do not refactor surrounding code during a bugfix.
Regression check — Every fix must be verified against the original bug AND tested for side effects on related functionality.

INITIALIZATION

Design Log

Read {output_folder}/_progress/00-design-log.md. Check Current and Backlog for context.

Essential Guides

Execution Principles — Document-first, plan-then-execute
Session Protocol — Read dialog, verify plan, present status
Inline Testing Guide — Verify fixes with Puppeteer before presenting

STEPS

Execute steps in ./steps-f/:

Step	File	Purpose
01	step-01-reproduce.md	Reproduce and document the bug
02	step-02-investigate.md	Investigate root cause
03	step-03-fix.md	Implement the fix
04	step-04-verify.md	Verify fix, check regressions
05	step-05-document.md	Document fix, update tests

Flow: 01 → 02 → 03 → 04 → 05

Critical Rules

ALWAYS reproduce the bug before investigating
ALWAYS identify root cause before writing a fix
ALWAYS create a test that catches the bug before fixing
ALWAYS run regression checks after fixing
NEVER refactor surrounding code in the same fix
NEVER fix symptoms — fix the root cause

AFTER COMPLETION

Append a progress entry to {output_folder}/_progress/00-design-log.md under ## Progress: ### [date] — Bugfix: [what was fixed]
Suggest re-running acceptance testing (Phase 5 [T]) to verify the fix

2.1 KiB Raw Blame History