From 45160289f98b81f75e589e64eb11c12a88a6c240 Mon Sep 17 00:00:00 2001
From: Mathieu Benoit <mathben@technolibre.ca>
Date: Sat, 7 Mar 2026 02:30:59 -0500
Subject: [PATCH] [ADD] claude agent information

---
 CLAUDE.md         | 56 +++++++++++++++++++++++++++++++++++++++++++++++
 doc/AGENT.INFO.md |  5 +++++
 2 files changed, 61 insertions(+)
 create mode 100644 doc/AGENT.INFO.md

diff --git a/CLAUDE.md b/CLAUDE.md
index b2b54d1..6c520dc 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -246,3 +246,59 @@ Plateformes supportées : Ubuntu 20.04-25.04, Debian 12, Arch Linux, macOS (pyen
 - Pour les commits : suivre le format `[TYPE] description` (ex: `[FIX]`, `[UPD]`, `[ADD]`, `[REM]`)
 - Pour la documentation : modifier les `.base.md`, jamais les `.md` ou `.fr.md` directement
 - Outil mmg disponible via `source .venv.erplibre/bin/activate && mmg`
+
+## Workflow Orchestration
+
+### 1. Plan Mode Default
+- Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
+- If something goes sideways, STOP and re-plan immediately
+- Don't keep pushing.
+- Use plan mode for verification steps, not just building
+- Write detailed specs upfront to reduce ambiguity
+
+### 2. Subagent Strategy
+- Use subagents liberally to keep the main context window clean.
+- Offload research, exploration, and parallel analysis to subagents
+- For complex problems, throw more compute at it via subagents
+- One task per subagent for focused execution
+
+### 3. Self-Improvement Loop
+- Capture Lessons: Update AGENT.md with any change in approach the user has asked you to make.
+- Write rules for yourself that prevent the same mistake
+- Ruthlessly iterate on these lessons until the mistake rate drops.
+- Review lessons at session start for relevant project
+
+### 4. Verification Before Done
+- Never mark a task complete without proving it works
+- Diff behavior between main and your changes when relevant
+- Ask yourself, "Would a staff engineer approve this?"
+- Run tests, check logs, and demonstrate correctness.
+
+### 5. Demand Elegance (Balanced)
+- For non-trivial changes, pause and ask, "Is there a more elegant way?"
+- If a fix feels hacky: "Knowing everything I know now, implement the elegant solution"
+- Skip this for simple, obvious fixes
+- Don't over-engineer.
+- Challenge your own work before presenting it
+
+### 6. Autonomous Bug Fixing
+- When given a bug report, just fix it. Don't ask for hand-holding
+- Point at logs, errors, and failing tests.
+- Then resolve them.
+- Zero context switching required from the user
+- Go fix failing CI tests without being told how
+
+## Task Management
+
+1. **Plan First**: Write a plan to `tasks/todo.md` with checkable items.
+2. **Verify Plan**: Check in before starting implementation.
+3. **Track Progress**: Mark items complete as you go.
+4. **Explain Changes**: High-level summary at each step.
+5. **Document Results**: Add review section to `tasks/todo.md`
+6. **Capture Lessons**: Update `tasks/lessons.md` after corrections
+
+## Core Principles
+
+- **Simplicity First**: Make every change as simple as possible. Impact minimal code.
+- **No Laziness**: Find root causes. No temporary fixes. Senior developer standards.
+- **Minimal Impact**: Changes should only touch what's necessary. Avoid introducing bugs.
diff --git a/doc/AGENT.INFO.md b/doc/AGENT.INFO.md
new file mode 100644
index 0000000..97d9d80
--- /dev/null
+++ b/doc/AGENT.INFO.md
@@ -0,0 +1,5 @@
+# Agent GPT information
+
+## How to build
+
+Source for Best practices and workflows to use with an AI agent on any project https://gist.github.com/CodeLeom/519e930f70895924f0d2b9862b95a10b