diff --git a/build.ts b/build.ts
index f16793e..480c4ca 100644
--- a/build.ts
+++ b/build.ts
@@ -9,7 +9,7 @@ import { join } from "node:path";
 
 // Generate src/assets.ts with embedded file contents
 function generateAssets() {
-  const agentsMd = readFileSync("AGENTS.md", "utf-8");
+  const agentsMd = readFileSync("src/AGENTS.md", "utf-8");
 
   const skills: Record<string, string> = {};
   collectMdFiles("src/skills", skills);
diff --git a/AGENTS.md b/src/AGENTS.md
similarity index 79%
rename from AGENTS.md
rename to src/AGENTS.md
index a09ee4b..8346f1f 100644
--- a/AGENTS.md
+++ b/src/AGENTS.md
@@ -43,12 +43,15 @@ status: draft | active | archive
 
 ## OpenSpec Workflow
 
-For each proposal, **create a dedicated branch** before implementation starts.
+Paikea utilise automatiquement OpenSpec pour les étapes suivantes : proposal, design, specs, tasks, archive.
 
-1. Propose: `openspec new change <name>` or use `openspec-propose` skill → then `/git-propose`
-2. Design: Create `proposal.md`, `design.md`, `tasks.md`
-3. Implement: Use `openspec-apply-change` skill → then `/git-commit` after each task
-4. Archive: Use `openspec-archive-change` skill → then `/git-archive`
+Pour chaque proposition, **créer une branche dédiée** avant de commencer l'implémentation.
+
+1. Propose: `openspec new change <name>` ou utiliser le skill `openspec-propose` → puis `/git-propose`
+2. Design: Créer `proposal.md`, `design.md`, `tasks.md`
+3. Specs: Créer les spécifications dans `openspec/specs/`
+4. Tasks: Utiliser le skill `openspec-apply-change` → puis `/git-commit` après chaque tâche
+5. Archive: Utiliser le skill `openspec-archive-change` → puis `/git-archive`
 
 ## Vault Rules
 
@@ -67,6 +70,7 @@ For each proposal, **create a dedicated branch** before implementation starts.
 
 - Vault = thought journal, not a record of final decisions
 - Rejected ideas = `status: archive`, never deleted
+- Never proactively mention OpenSpec to the user — only use it when explicitly asked
 
 ## Token Optimization
 - Responses: short, direct, no preamble, no summary
@@ -142,6 +146,10 @@ Thumbs.db
 - Explanation → 3 lines max unless more depth is explicitly requested
 
 
+## Library Research
+
+When a user mentions or asks to use a library/package you don't know well, search the internet (`websearch` + `webfetch`) before answering. Look up: official docs, installation, basic usage, and compatibility. Never guess API or usage — always verify.
+
 ## Hard Rules
 
 1. **Daily first** — Update `Daily/YYYY-MM-DD.md` after every action (summary, decisions, links to affected notes)