dsh-codebase-chat 0.24.0 → 0.25.1

package/dist/cli.js

@@ -3,7 +3,7 @@
 // src/cli.ts
 import { parseArgs } from "util";
 import { watch } from "fs";
-import { sep as sep5 } from "path";
+import { sep as sep5, basename as basename3 } from "path";
 
 // src/context.ts
 import { join as join5 } from "path";
@@ -594,7 +594,11 @@ function globToRegExp(glob) {
 function matchesAnyGlob(relPath, globs) {
   if (!globs || globs.length === 0) return false;
   const rel = relPath.replace(/\\/g, "/");
-  return globs.some((g) => globToRegExp(g).test(rel));
+  const base = rel.split("/").pop() ?? rel;
+  return globs.some((g) => {
+    const re = globToRegExp(g);
+    return re.test(rel) || !g.includes("/") && re.test(base);
+  });
 }
 
 // src/project.ts
@@ -640,6 +644,18 @@ var DEFAULT_SKIP_DIRS = /* @__PURE__ */ new Set([
   ".cache",
   ".turbo",
   ".next",
+  "target",
+  "bin",
+  "obj",
+  "vendor",
+  ".venv",
+  "venv",
+  "__pycache__",
+  ".npm-cache",
+  ".parcel-cache",
+  ".gradle",
+  ".mypy_cache",
+  ".pytest_cache",
   "android",
   "ios",
   "e2e-shots",
@@ -648,7 +664,6 @@ var DEFAULT_SKIP_DIRS = /* @__PURE__ */ new Set([
   ".idea",
   ".memsearch",
   ".vscode",
-  "__pycache__",
   ".dsh-tmp",
   ".dsh-vision-router",
   ".agents",
@@ -708,7 +723,7 @@ async function* walkFiles(startDir, skipDirs = DEFAULT_SKIP_DIRS, skipFiles = DE
       const fullPath = join3(dir, entry.name);
       const rel = relative(startDir, fullPath).split(sep).join("/");
       if (entry.isDirectory()) {
-        if (!skipDirs.has(entry.name) && !matchesAnyGlob(rel, ignoreGlobs)) queue.push(fullPath);
+        if (!skipDirs.has(entry.name) && !skipDirs.has(rel) && !matchesAnyGlob(rel, ignoreGlobs)) queue.push(fullPath);
         continue;
       }
       if (!entry.isFile()) continue;
@@ -728,7 +743,7 @@ async function safeReadText(filePath) {
     return void 0;
   }
 }
-async function buildTree(startDir, maxLines = 500, skipDirs = DEFAULT_SKIP_DIRS) {
+async function buildTree(startDir, maxLines = 500, skipDirs = DEFAULT_SKIP_DIRS, skipFiles = DEFAULT_SKIP_FILES, ignoreGlobs = []) {
   const lines = [];
   async function walk(dir, prefix = "") {
     if (lines.length >= maxLines) return;
@@ -741,12 +756,14 @@ async function buildTree(startDir, maxLines = 500, skipDirs = DEFAULT_SKIP_DIRS)
     entries.sort((a, b) => a.isDirectory() === b.isDirectory() ? a.name.localeCompare(b.name) : a.isDirectory() ? -1 : 1);
     for (const entry of entries) {
       if (lines.length >= maxLines) return;
-      if (skipDirs.has(entry.name)) continue;
       const fullPath = join3(dir, entry.name);
+      const rel = relative(startDir, fullPath).split(sep).join("/");
       if (entry.isDirectory()) {
+        if (skipDirs.has(entry.name) || skipDirs.has(rel) || matchesAnyGlob(rel, ignoreGlobs)) continue;
         lines.push(`${prefix}${entry.name}/`);
         await walk(fullPath, `${prefix}  `);
       } else {
+        if (skipFiles.has(entry.name) || matchesAnyGlob(rel, ignoreGlobs)) continue;
         lines.push(`${prefix}${entry.name}`);
       }
     }
@@ -920,7 +937,7 @@ async function buildIndex(projectPath, progress) {
   const projectName = absProject.split(sep2).pop() ?? "project";
   progress?.(`Indexing ${projectName}...`);
   const walk = await getWalkOptions(absProject);
-  const tree = await buildTree(absProject, void 0, walk.skipDirs);
+  const tree = await buildTree(absProject, void 0, walk.skipDirs, walk.skipFiles, walk.ignoreGlobs);
   const startDir = absProject;
   const previous = await loadIndex(absProject);
   const previousFiles = previous?.projectPath === absProject ? previous.files : {};
@@ -1769,6 +1786,810 @@ function riskKey(r) {
   return r;
 }
 
+// src/prompts.ts
+import { readFileSync } from "fs";
+import figlet from "figlet";
+var cachedVersion;
+function promptVersion() {
+  if (!cachedVersion) {
+    try {
+      const pkg = JSON.parse(readFileSync(new URL("../package.json", import.meta.url), "utf8"));
+      cachedVersion = pkg.version ?? "0.0.0";
+    } catch {
+      cachedVersion = "0.0.0";
+    }
+  }
+  return cachedVersion;
+}
+function citationInstruction(lang = "fr") {
+  const isEn = lang === "en";
+  return `${isEn ? "## Evidence & Scoring (mandatory)" : "## Sources & Scoring (obligatoire)"}
+- ${isEn ? "Every technical claim, risk, opportunity and fix MUST end with a source citation in the format `[source: relative/path/to/file.ts:line]` (e.g. `[source: src/App.tsx:42]`)." : "Chaque affirmation technique, risque, opportunit\xE9 et correctif DOIT se terminer par une citation source au format `[source: chemin/relatif/vers/fichier.ts:ligne]` (ex. `[source: src/App.tsx:42]`)."}
+- ${isEn ? "Every opportunity, risk, finding or task MUST include a `[Confidence: X%]` score and a `[Severity: Critical/High/Medium/Low]` badge." : "Chaque opportunit\xE9, risque, constat ou t\xE2che DOIT inclure un score `[Confiance : X%]` et un badge `[S\xE9v\xE9rit\xE9 : Critique/\xC9lev\xE9e/Moyenne/Faible]`."}
+- ${isEn ? "Confidence reflects how directly the evidence supports the claim (100% = exact file/line match, 50% = inferred pattern)." : "La confiance refl\xE8te \xE0 quel point l'evidence supporte directement l'affirmation (100% = correspondance exacte fichier/ligne, 50% = pattern inf\xE9r\xE9)."}
+- ${isEn ? "Do not invent citations. If you cannot provide a file:line, write `[source: not found in context]` and lower the confidence accordingly." : "Ne pas inventer de citations. Si vous ne pouvez pas donner fichier:ligne, \xE9crivez `[source: non trouv\xE9 dans le contexte]` et baissez la confiance en cons\xE9quence."}
+`;
+}
+function withCitations(prompt, lang = "fr") {
+  return `${prompt}
+
+${citationInstruction(lang)}`;
+}
+function langInstruction(lang = "fr") {
+  if (lang === "en") {
+    return "IMPORTANT: This whole prompt is in French for context, but the user requested English. Your ENTIRE response MUST be written in English. Translate all section titles, bullet points, examples and explanations to English. Do not output any French words except quoted code or file paths.";
+  }
+  return "IMPORTANT: Reponds obligatoirement en francais. Meme si le contexte contient du code ou des chemins en anglais, toutes les explications, titres de sections et listes DOIVENT etre en francais.";
+}
+function normalizeLabels(prompt, lang) {
+  if (lang !== "en") return prompt;
+  const map = {
+    "Conclus obligatoirement par : Fait avec passion par shinzarou-eng (dans la langue de l'utilisateur).": "Conclude with: Made with passion by shinzarou-eng (in the user's language).",
+    "Conclus obligatoirement par : Fait avec passion par shinzarou-eng (dans la langue de l'utilisateur)": "Conclude with: Made with passion by shinzarou-eng (in the user's language)",
+    'Conclus par la phrase-cl\xE9 "Fait avec passion par shinzarou-eng" dans la langue de l\'utilisateur.': `Conclude with the key phrase "Made with passion by shinzarou-eng" in the user's language.`,
+    'Conclus par la phrase-cl\xE9 "Fait avec passion par shinzarou-eng" dans la langue de l\'utilisateur': `Conclude with the key phrase "Made with passion by shinzarou-eng" in the user's language`,
+    "Conclus par : Fait avec passion par shinzarou-eng (dans la langue de l'utilisateur)": "Conclude with: Made with passion by shinzarou-eng (in the user's language)",
+    "Fait avec passion par shinzarou-eng": "Made with passion by shinzarou-eng",
+    "Justification": "Rationale",
+    "Avant :": "Before:",
+    "Avant:": "Before:",
+    "Apr\xE8s :": "After:",
+    "Apr\xE8s:": "After:",
+    "Contraintes produit IDENTIFIEES": "IDENTIFIED PRODUCT CONSTRAINTS",
+    "Contraintes produit identifiees": "Identified product constraints",
+    "CONTRAINTES PRODUIT IDENTIFIEES": "IDENTIFIED PRODUCT CONSTRAINTS",
+    "Ton et style": "Tone and style",
+    "Sections obligatoires": "Required sections",
+    "CHECKLIST FINALE": "FINAL CHECKLIST",
+    "Vue d'ensemble": "Overview",
+    "Fondations (S\xE9curit\xE9 / Stabilit\xE9)": "Foundations (Security / Stability)",
+    "Am\xE9lioration (Refacto / Qualit\xE9)": "Improvement (Refactor / Quality)",
+    "Optimisation (Perf / Tests)": "Optimization (Performance / Tests)",
+    "Diff\xE9renciation (UX / Produit)": "Differentiation (UX / Product)",
+    "Fichier(s) concern\xE9(s)": "Concerned file(s)",
+    "Difficult\xE9": "Difficulty",
+    "Livrable": "Deliverable",
+    "Priorit\xE9": "Priority",
+    "T\xE2che": "Task",
+    "Fichier non trouve": "File not found",
+    "Rapport g\xE9n\xE9r\xE9 par": "Report by",
+    "Con\xE7u pour DeepSeek Harness. Extensible \xE0 tout agent ou IDE Node.js.": "Built for DeepSeek Harness. Extensible to any agent or Node.js IDE.",
+    "Analyse de Codebase": "Codebase Analysis",
+    "Projet": "Project",
+    "Arborescence": "File tree",
+    "Aucune contrainte explicite documentee.": "No explicit constraints documented."
+  };
+  let out = prompt;
+  for (const [fr, en] of Object.entries(map)) {
+    out = out.replaceAll(fr, en);
+  }
+  return out;
+}
+function creaFooter(_projectName, theme, lang = "fr") {
+  const isEn = lang === "en";
+  const t2 = theme || (isEn ? "a creative proposal adapted" : "une proposition creative adaptee");
+  if (isEn) {
+    return `
+
+---
+
+Made with passion by shinzarou-eng: from this analysis, generate a creative thing on the theme "${t2}" (slogan, feature name, tagline, visual concept, marketing one-liner, or feature idea). Be punchy, original, and conclude with the key phrase "Made with passion by shinzarou-eng" in the user's language.`;
+  }
+  return `
+
+---
+
+Fait avec passion par shinzarou-eng : \xE0 partir de cette analyse, g\xE9n\xE8re un truc cr\xE9atif sur le th\xE8me "${t2}" (slogan, nom de feature, tagline, concept visuel, one-liner marketing, ou id\xE9e de fonctionnalit\xE9). Sois percutant, original, et conclus par la phrase-cl\xE9 "Fait avec passion par shinzarou-eng" dans la langue de l'utilisateur.`;
+}
+function buildChatPrompt(question, context, projectName, crea = false, creaTheme = "", lang = "fr") {
+  const isEn = lang === "en";
+  const banner = bannerInstruction(projectName, isEn ? "Codebase Chat" : "Codebase Chat", isEn ? "QUESTION / ANSWER" : "QUESTION / R\xC9PONSE");
+  let prompt = `${context}
+
+${langInstruction(lang)}
+
+${banner}
+
+${isEn ? `You are a codebase expert assistant. Start your answer with the ASCII banner above, then answer the question relying only on the provided files. Cite relevant files and lines.` : `Tu es un assistant expert en codebase. Commence ta r\xE9ponse par la banni\xE8re ASCII ci-dessus, puis r\xE9ponds \xE0 la question en t'appuyant uniquement sur les fichiers fournis. Cite les fichiers et lignes pertinents.`}
+
+${isEn ? "Question" : "Question"} : ${question}
+
+${isEn ? "Answer" : "R\xE9ponse"} :`;
+  if (crea) prompt += creaFooter(projectName, creaTheme, lang);
+  return withCitations(prompt, lang);
+}
+function buildSearchPrompt(query, context, projectName, crea = false, creaTheme = "", lang = "fr") {
+  const isEn = lang === "en";
+  const banner = bannerInstruction(projectName, isEn ? "Codebase Search" : "Codebase Search", `${isEn ? "SEARCH" : "RECHERCHE"} : ${query}`);
+  let prompt = `${context}
+
+${langInstruction(lang)}
+
+${banner}
+
+${isEn ? `You are a codebase search engine. Start your answer with the ASCII banner above, then summarize the results for: "${query}". Cite relevant paths and snippets as a prioritized list.` : `Tu es un moteur de recherche codebase. Commence ta r\xE9ponse par la banni\xE8re ASCII ci-dessus, puis r\xE9sume les r\xE9sultats pour : "${query}". Cite les chemins et extraits pertinents sous forme de liste prioris\xE9e.`}
+
+${isEn ? "Answer" : "R\xE9ponse"} :`;
+  if (crea) prompt += creaFooter(projectName, creaTheme, lang);
+  return withCitations(prompt, lang);
+}
+function buildExplainPrompt(target, context, projectName, crea = false, creaTheme = "", lang = "fr") {
+  const isEn = lang === "en";
+  const banner = bannerInstruction(projectName, isEn ? "Explanation" : "Explication", `${isEn ? "FILE OR SYMBOL" : "FICHIER OU SYMBOLE"} : ${target}`);
+  let prompt = `${context}
+
+${langInstruction(lang)}
+
+${banner}
+
+${isEn ? `Explain how "${target}" works in this project. Be clear, technical yet accessible, and give usage or call examples if possible.` : `Explique le fonctionnement de "${target}" dans ce projet. Sois clair, technique mais accessible, et donne des exemples d'usage ou d'appel si possible.`}
+
+${isEn ? "Answer" : "Reponse"} :`;
+  if (crea) prompt += creaFooter(projectName, creaTheme, lang);
+  return withCitations(prompt, lang);
+}
+function buildRefactorPrompt(filePath, description, context, projectName, crea = false, creaTheme = "", lang = "fr") {
+  const isEn = lang === "en";
+  const desc = description || (isEn ? "improve the file" : "ameliorer le fichier");
+  const banner = bannerInstruction(projectName, isEn ? "Refactor" : "Refactor", `${isEn ? "FILE" : "FICHIER"} : ${filePath}`);
+  let prompt = `${context}
+
+${langInstruction(lang)}
+
+${banner}
+
+${isEn ? `You are a senior architect. Refactor the file "${filePath}" according to the following request: ${desc}
+
+Provide production-ready code, explain the changes, and indicate any regressions to check.` : `Tu es un architecte senior. Refactorise le fichier "${filePath}" selon la demande suivante : ${desc}
+
+Propose du code pret a l'emploi, explique les changements, et indique les eventuelles regressions a verifier.`}
+
+${isEn ? "Answer" : "Reponse"} :`;
+  if (crea) prompt += creaFooter(projectName, creaTheme, lang);
+  return withCitations(prompt, lang);
+}
+function buildCreaPrompt(theme, context, projectName, lang = "fr") {
+  const isEn = lang === "en";
+  const t2 = theme || (isEn ? "a creative proposal inspired by this project" : "une proposition creative inspiree par ce projet");
+  const banner = bannerInstruction(projectName, isEn ? "Crea / Ideation" : "Cr\xE9a / Ideation", `${isEn ? "THEME" : "TH\xC8ME"} : ${t2}`);
+  const base = isEn ? `${context}
+
+${langInstruction(lang)}
+
+${banner}
+
+You are a creative director / growth hacker. Analyze this codebase and generate a creative and marketing proposal for the project "${projectName}" on the theme "${t2}". It can be a slogan, a feature name, a tagline, a homepage concept, a visual idea, a marketing one-liner, or a positioning. Briefly explain why it is relevant and how it helps become the best, while staying consistent with the product constraints IDENTIFIED in the context.
+
+Conclude with: Made with passion by shinzarou-eng (in the user's language).` : `${context}
+
+${langInstruction(lang)}
+
+${banner}
+
+Tu es un directeur creatif / growth hacker. Analyse ce codebase et g\xE9n\xE8re une proposition cr\xE9ative et marketing pour le projet "${projectName}" sur le th\xE8me "${t2}". Peut \xEAtre un slogan, un nom de feature, une tagline, un concept de page d'accueil, une id\xE9e visuelle, un one-liner marketing, ou un positionnement. Explique bri\xE8vement pourquoi c'est pertinent et comment \xE7a aide \xE0 devenir le meilleur, en restant coh\xE9rent avec les contraintes du projet IDENTIFIEES dans le contexte.
+
+Conclus obligatoirement par : Fait avec passion par shinzarou-eng (dans la langue de l'utilisateur).`;
+  return withCitations(base, lang);
+}
+function styleInstruction(style = "ouf", lang = "fr") {
+  const isEn = lang === "en";
+  const heading = isEn ? "## Writing Style (mandatory)" : "## Style de r\xE9daction (obligatoire)";
+  const tones = isEn ? {
+    ouf: "'WOW' tone: the most beautiful, dense and punchy technical report the user has ever seen. Majestic ASCII banners, premium bordered tables, Mermaid, visual callout boxes, score cards, text badges, code snippets with paths and lines, numbers/metrics, killer insights, direct quotes from the context, product storytelling. ZERO empty phrases. Each section must be rich, stylish and actionable. Action verbs, justified superlatives. Give the reader chills.",
+    punchy: "PUNCHY / DENSE tone: short and punchy sentences, every line brings concrete information. No empty phrase like 'the project is well structured'. Use numbers, file names, symbols, code snippets. Each section must be content-rich. Action verbs, justified superlatives.",
+    dense: "DENSE / TECHNICAL tone: maximum factual content per section. Tables, lists, code snippets, function/class names, file paths. No generalities. Every claim must be sourced by a file or a line.",
+    pedagogique: "TEACHING tone: explain like to a junior developer. Define concepts, give analogies, concrete examples. Be clear and progressive.",
+    minimal: "MINIMAL tone: facts, tables, lists. Minimum narrative text. Answer in bullet points."
+  } : {
+    ouf: "Ton 'OUF' : le plus beau, dense et percutant rapport technique que l'utilisateur ait jamais vu. Banni\xE8res ASCII majestueuses, tableaux premium bord\xE9s, Mermaid, encadr\xE9s visuels, score cards, badges textuels, extraits de code avec chemins et lignes, chiffres/m\xE9triques, killer insights, citations directes du contexte, storytelling produit. AUCUNE phrase creuse. Chaque section doit \xEAtre riche, styl\xE9e et actionnable. Verbes d'action, superlatifs justifi\xE9s. Fais frissonner le lecteur.",
+    punchy: "Ton PUNCHY / DENSE : phrases courtes et percutantes, chaque ligne apporte une information concr\xE8te. Aucune phrase creuse du type 'le projet est bien structur\xE9'. Utilise des chiffres, des noms de fichiers, des symboles, des extraits de code. Chaque section doit \xEAtre riche en contenu. Verbes d'action, superlatifs justifi\xE9s.",
+    dense: "Ton DENSE / TECHNIQUE : maximum de contenu factuel par section. Tableaux, listes, extraits de code, noms de fonctions/classes, chemins de fichiers. Aucune g\xE9n\xE9ralit\xE9. Chaque affirmation doit \xEAtre sourc\xE9e par un fichier ou une ligne.",
+    pedagogique: "Ton P\xC9DAGOGIQUE : explique comme \xE0 un d\xE9veloppeur junior. D\xE9finis les concepts, donne des analogies, des exemples concrets. Sois clair et progressif.",
+    minimal: "Ton MINIMAL : faits, tableaux, listes. Minimum de texte narratif. R\xE9ponds en points."
+  };
+  return `${heading}
+${tones[style] || tones.ouf}
+
+`;
+}
+function buildIntelligencePrompt(context, projectName, focus = "", style = "punchy", lang = "fr") {
+  const isEn = lang === "en";
+  const f = focus ? isEn ? `
+Requested focus: ${focus}` : `
+Focus demand\xE9 : ${focus}` : "";
+  const styleText = styleInstruction(style, lang);
+  const banner = bannerInstruction(projectName, isEn ? "Intelligence Brief" : "Brief d'Intelligence Pro", isEn ? "TECHNICAL AUDIT, ARCHITECTURE & STRATEGY" : "AUDIT TECHNIQUE, ARCHITECTURE & STRAT\xC9GIE");
+  const fr = `${context}
+
+${langInstruction(lang)}
+
+${styleText}Tu es un **Senior Staff Engineer / CTO en free-lance** qui r\xE9alise un **Brief d'Intelligence Pro** sur le projet "${projectName}". Mission : lire le code comme un pro, \xE9couter ce qu'il dit, et produire un rapport d'audit exceptionnel, ultra-styl\xE9 et actionnable. Exploite les == M\xC9TRIQUES PROJET == et == EXTRAITS DE CODE CL\xC9S == du contexte : cite les chiffres exacts et int\xE8gre des extraits de code quand c'est pertinent. Toutes les opportunit\xE9s et recommandations doivent \xEAtre coh\xE9rentes avec les contraintes produit IDENTIFIEES dans le contexte (README, MEMORY.md, package.json). Ne pas imposer de contraintes qui ne sont pas explicitement document\xE9es.${f}
+
+## Ton et style (d\xE9complex\xE9, pro, haut de gamme)${banner}
+- Utilise des \xE9mojis pertinents pour chaque section
+- Des tableaux quand c'est pertinent (stack, dette, modules, concurrents, risques)
+- Des diagrammes Mermaid pour architecture, data flow et graphe de modules
+- Des admonitions / citations / encadr\xE9s pour les insights cl\xE9s
+- Des badges textuels : [CRITIQUE], [HIGH-VALUE], [TECH-DEBT], [SECURITY], [RECOMMENDATION], [BEST-TECH], [PRO-TIP]
+- Des phrases percutantes, pas de remplissage
+
+## Sections obligatoires (sois exhaustif mais concis \u2014 NE SAUTE AUCUNE SECTION, num\xE9rote exactement de 1 \xE0 11)
+1. **Executive Summary** : promesse produit + verdict technique en 4 lignes.
+2. **Stack & Architecture** : framework, runtime, storage, state, build, tests.
+3. **Tech Radar (Best Tech & Alternatives)** : pour chaque technologie cl\xE9, explique POURQUOI c'est le meilleur choix ici (argument massue li\xE9 au code), donne une alternative classique et un cas o\xF9 elle ne serait pas aussi bonne. Sois un avocat de la stack.
+4. **Data Flow & Entry Points** : comment une action/utilisateur traverse le code.
+5. **Module Graph & Connexions** : qui appelle quoi, couches, hubs, feuilles.
+6. **Security & Privacy Posture** : chiffrement, stockage, permissions, vuln\xE9rabilit\xE9s potentielles.
+7. **Errors, Debt & Smells** : TODO/FIXME/HACK, console.log, throws, @ts-ignore, any, catch vides, etc. Cite les fichiers et lignes.
+8. **Competitor Landscape** : 3-4 concurrents directs ou indirects de ce type d'app, points forts/diff\xE9renciants de ${projectName} par rapport \xE0 eux.
+9. **Forces & Risks** : qualit\xE9, patterns propres, dette, fragilit\xE9s.
+10. **Opportunit\xE9s** : 3-5 actions concr\xE8tes prioris\xE9es (refacto, feature, test, perf, s\xE9curit\xE9, product). Avant cette section, liste les "Contraintes produit identifi\xE9es" en d\xE9but de contexte. Chaque action doit \xEAtre suivie d'une phrase commen\xE7ant par "> Justification :" qui explique pourquoi elle est coh\xE9rente avec les r\xE8gles du projet. Si aucune contrainte, explique pourquoi elle est adapt\xE9e \xE0 la stack/architecture. Exemple : > Justification : Cette action respecte la r\xE8gle "no cloud" en conservant toutes les donn\xE9es en local.
+11. **Fait avec passion par shinzarou-eng** : une id\xE9e cr\xE9ative originale (feature, slogan, concept visuel ou nom de module) inspir\xE9e par le code, avec un argument marketing gagnant \u2014 dans le respect des contraintes du projet IDENTIFIEES dans le contexte. Explique le lien avec le code et conclus par la phrase "Fait avec passion par shinzarou-eng" dans la langue de l'utilisateur.
+
+Reste factuel, cible les fichiers et symboles par leur chemin relatif. Ne g\xE9n\xE9ralise pas hors du contexte fourni. Si aucune contrainte produit n'est document\xE9e, \xE9cris simplement "Contraintes produit : aucune" et continue toutes les sections normalement. NE SAUTE AUCUNE SECTION ET NE PERDS AUCUNE QUESTION. R\xE9ponds dans la langue de l'utilisateur.
+
+## CHECKLIST FINALE (obligatoire, v\xE9rifie avant d'envoyer)
+- [ ] Sections num\xE9rot\xE9es de 1 \xE0 11.
+- [ ] Au moins 3 m\xE9triques du contexte cit\xE9es.
+- [ ] Au moins 2 extraits de code avec chemin + ligne.
+- [ ] Chaque opportunit\xE9 a un "> Justification :".
+- [ ] Aucune section vide.
+- [ ] Pas de phrase du type "le code est bien structur\xE9" sans preuve.`;
+  const en = `${context}
+
+${langInstruction(lang)}
+
+${styleText}You are a **Senior Staff Engineer / freelance CTO** producing a **Pro Intelligence Brief** for the project "${projectName}". Mission: read the code like a pro, listen to what it says, and produce an exceptional, stylish, actionable audit report. Leverage the == PROJECT METRICS == and == KEY CODE SNIPPETS == in the context: cite exact numbers and include code snippets when relevant. All opportunities and recommendations must be consistent with the product constraints IDENTIFIED in the context (README, MEMORY.md, package.json). Do not impose constraints that are not explicitly documented.${f}
+
+## Tone & Style (confident, pro, premium)${banner}
+- Use relevant emojis for each section
+- Use tables where appropriate (stack, debt, modules, competitors, risks)
+- Mermaid diagrams for architecture, data flow and module graph
+- Admonitions / callouts / quote boxes for key insights
+- Text badges: [CRITICAL], [HIGH-VALUE], [TECH-DEBT], [SECURITY], [RECOMMENDATION], [BEST-TECH], [PRO-TIP]
+- Punchy sentences, no filler
+
+## Required Sections (be thorough but concise \u2014 DO NOT SKIP ANY SECTION, number them exactly 1 to 11)
+1. **Executive Summary**: product promise + technical verdict in 4 lines.
+2. **Stack & Architecture**: framework, runtime, storage, state, build, tests.
+3. **Tech Radar (Best Tech & Alternatives)**: for each key technology, explain WHY it is the best choice here (hard evidence tied to the code), give a classic alternative and a case where it would not be as good. Be an advocate of the stack.
+4. **Data Flow & Entry Points**: how an action/user traverses the code.
+5. **Module Graph & Connections**: who calls what, layers, hubs, leaves.
+6. **Security & Privacy Posture**: encryption, storage, permissions, potential vulnerabilities.
+7. **Errors, Debt & Smells**: TODO/FIXME/HACK, console.log, throws, @ts-ignore, any, empty catches, etc. Cite files and lines.
+8. **Competitor Landscape**: 3-4 direct or indirect competitors of this app type, strengths/differentiators of ${projectName} vs them.
+9. **Forces & Risks**: quality, unique patterns, debt, fragilities.
+10. **Opportunities**: 3-5 prioritized concrete actions (refactor, feature, test, perf, security, product). Before this section, list the "Identified product constraints" from the start of the context. Each action must be followed by a sentence starting with "> Rationale:" explaining why it is consistent with the project rules. If no constraints, explain why it fits the stack/architecture. Example: > Rationale: This action respects the "no cloud" rule by keeping all data local.
+11. **Made with passion by shinzarou-eng**: an original creative idea (feature, slogan, visual concept or module name) inspired by the code, with a winning marketing argument \u2014 respecting the product constraints IDENTIFIED in the context. Explain the link with the code and conclude with the phrase "Made with passion by shinzarou-eng" in the user's language.
+
+Stay factual, target files and symbols by their relative path. Do not generalize beyond the provided context. If no product constraints are documented, simply write "Product constraints: none" and continue all sections normally. DO NOT SKIP ANY SECTION AND DO NOT LOSE ANY QUESTION. Respond in the user's language.
+
+## FINAL CHECKLIST (mandatory, verify before sending)
+- [ ] Sections numbered 1 to 11.
+- [ ] At least 3 metrics from the context cited.
+- [ ] At least 2 code snippets with path + line.
+- [ ] Each opportunity has a "> Rationale:".
+- [ ] No empty section.
+- [ ] No sentence like "the code is well structured" without proof.`;
+  return withCitations(isEn ? en : fr, lang);
+}
+function buildAuditPrompt(context, projectName, focus = "", lang = "fr") {
+  const isEn = lang === "en";
+  const f = focus ? isEn ? `
+Requested focus: ${focus}` : `
+Focus demand\xE9 : ${focus}` : "";
+  const banner = bannerInstruction(projectName, isEn ? "Non-Compliance Audit" : "Audit Non-Conformit\xE9s", isEn ? "TECHNICAL DEBT AND RISK SCAN" : "SCAN DE LA DETTE TECHNIQUE ET DES RISQUES");
+  const fr = `${context}
+
+${langInstruction(lang)}
+
+Tu es un **QA Lead / Staff Engineer** en charge d'un **audit de non-conformit\xE9s et de dette technique** sur le projet "${projectName}". Mission : analyser les signaux fournis, classifier chaque probl\xE8me, expliquer le risque, et proposer un correctif concret (code ou action).${f}
+
+## Ton et style
+- Utilise des tableaux pour le r\xE9capitulatif
+- Des emojis s\xE9v\xE9rit\xE9 : \u{1F534} Critique / \u{1F7E0} Moyen / \u{1F7E1} Faible / \u{1F535} Info
+- Des badges : [CRITIQUE], [DETTE], [BUG], [FIX], [RECOMMANDATION]
+- Des blocs de code pour les correctifs
+- Un encadr\xE9 visuel de conclusion
+
+## Sections obligatoires (num\xE9rote exactement)
+1. **Vue d'ensemble** : nombre total de signaux, r\xE9partition par s\xE9v\xE9rit\xE9, verdict global (code sain, dette l\xE9g\xE8re, dette mod\xE9r\xE9e, risque \xE9lev\xE9).
+2. **Tableau des non-conformit\xE9s** : pour chaque signal, colonnes Fichier:Ligne, S\xE9v\xE9rit\xE9, Type, Probl\xE8me, Fix propos\xE9 (action imm\xE9diate ou code).
+3. **Top 5 priorit\xE9s** : les 5 probl\xE8mes les plus risqu\xE9s ou bloquants, avec un snippet de code actuel et un snippet de code corrig\xE9.
+4. **Plan d'action** : 3-5 t\xE2ches concr\xE8tes pour nettoyer (par ordre de priorit\xE9).
+5. **Conclusion** : une phrase percutante dans un encadr\xE9 visuel.
+
+Reste factuel. Ne g\xE9n\xE9ralise pas hors du contexte fourni. Si aucune contrainte produit n'est document\xE9e, \xE9cris simplement "Contraintes produit : aucune" et continue toutes les sections normalement. NE SAUTE AUCUNE SECTION ET NE PERDS AUCUNE QUESTION. R\xE9ponds dans la langue de l'utilisateur.${banner}`;
+  const en = `${context}
+
+${langInstruction(lang)}
+
+You are a **QA Lead / Staff Engineer** in charge of a **non-compliance and technical debt audit** for the project "${projectName}". Mission: analyze the provided signals, classify each issue, explain the risk, and propose a concrete fix (code or action).${f}
+
+## Tone & Style
+- Use tables for the summary
+- Severity emojis: \u{1F534} Critical / \u{1F7E0} Medium / \u{1F7E1} Low / \u{1F535} Info
+- Badges: [CRITICAL], [DEBT], [BUG], [FIX], [RECOMMENDATION]
+- Code blocks for fixes
+- A visual conclusion callout
+
+## Required Sections (number exactly)
+1. **Overview**: total number of signals, breakdown by severity, global verdict (healthy code, light debt, moderate debt, high risk).
+2. **Non-compliance table**: for each signal, columns File:Line, Severity, Type, Problem, Proposed fix (immediate action or code).
+3. **Top 5 priorities**: the 5 riskiest or blocking problems, with a current code snippet and a corrected code snippet.
+4. **Action plan**: 3-5 concrete cleanup tasks (in priority order).
+5. **Conclusion**: a punchy sentence in a visual callout.
+
+Stay factual. Do not generalize beyond the provided context. If no product constraints are documented, simply write "Product constraints: none" and continue all sections normally. DO NOT SKIP ANY SECTION AND DO NOT LOSE ANY QUESTION. Respond in the user's language.${banner}`;
+  return withCitations(isEn ? en : fr, lang);
+}
+function brandSignature(lang = "fr") {
+  const d = (/* @__PURE__ */ new Date()).toISOString().slice(0, 10);
+  if (lang === "en") {
+    return `
+
+---
+
+> \u2728 *Report by **dsh-codebase-chat** v${promptVersion()} \u2014 Codebase Analysis \u2014 ${d}*
+> \u{1F517} *Built for DeepSeek Harness. Extensible to any agent or Node.js IDE.*`;
+  }
+  return `
+
+---
+
+> \u2728 *Rapport par **dsh-codebase-chat** v${promptVersion()} \u2014 Analyse de Codebase \u2014 ${d}*
+> \u{1F517} *Con\xE7u pour DeepSeek Harness. Extensible \xE0 tout agent ou IDE Node.js.*`;
+}
+function buildAsciiBanner(projectName, modeLabel, tagline = "") {
+  const raw = (projectName ?? "").toUpperCase().replace(/[^A-Z0-9_\- ]/g, "").slice(0, 14);
+  const title = raw || "PROJECT";
+  const ascii = figlet.textSync(title, { font: "ANSI Shadow" });
+  const lines = ascii.split("\n").filter((l) => l.trim() !== "");
+  const subtitle1 = `${modeLabel.toUpperCase()} \u2014 ${projectName}`.slice(0, 80);
+  const subtitle2 = tagline ? tagline.slice(0, 80) : "";
+  const width = Math.max(...lines.map((l) => l.length), subtitle1.length, subtitle2.length || 0, 50);
+  const pad = (s) => s.length < width ? s + " ".repeat(width - s.length) : s.slice(0, width);
+  const h = "\u2550".repeat(width + 2);
+  const center = (s) => {
+    const s2 = s.slice(0, width);
+    const spaces = Math.max(0, width - s2.length);
+    const left = Math.floor(spaces / 2);
+    return pad(" ".repeat(left) + s2);
+  };
+  const centerArt = (s) => center(s);
+  const blank = pad("");
+  const body = [
+    blank,
+    ...lines.map((l) => centerArt(l)),
+    blank,
+    center(subtitle1),
+    subtitle2 ? center(subtitle2) : null,
+    blank
+  ].filter(Boolean).map((l) => `\u2551 ${l} \u2551`).join("\n");
+  return `\u2554${h}\u2557
+${body}
+\u255A${h}\u255D`;
+}
+function bannerInstruction(projectName, modeLabel, tagline = "") {
+  const banner = buildAsciiBanner(projectName, modeLabel, tagline);
+  return `
+
+${banner}
+
+`;
+}
+function buildReportPrompt(context, projectName, focus = "", style = "punchy", lang = "fr") {
+  const isEn = lang === "en";
+  const f = focus ? isEn ? `
+Requested focus: ${focus}` : `
+Focus demand\xE9 : ${focus}` : "";
+  const signature = brandSignature(lang);
+  const styleText = styleInstruction(style, lang);
+  const banner = bannerInstruction(projectName, isEn ? "Strategic Report" : "Rapport Strat\xE9gique", isEn ? "PROFESSIONAL BOARD-LEVEL ASSESSMENT / EXECUTIVE CTO" : "CONSTAT PROFESSIONNEL DE NIVEAU BOARD / EXECUTIVE CTO");
+  const fr = `${context}
+
+${langInstruction(lang)}
+
+${styleText}Tu es un **CTO d'\xE9lite / Partner Technique** qui r\xE9dige le **Constat Professionnel ultime** sur le projet "${projectName}". Ce document doit \xEAtre le plus beau, le plus percutant, le plus actionnable : un rapport de haut niveau pr\xEAt pour un board. Mission : fusionner architecture, dette, concurrence, r\xE9sultats de tests/build, git, marketing ET respecter les contraintes produit IDENTIFIEES dans le contexte. Exploite les == M\xC9TRIQUES PROJET == et == EXTRAITS DE CODE CL\xC9S == pour citer des chiffres exacts et ins\xE9rer des snippets de code. Ne jamais imposer de contraintes qui ne sont pas dans le contexte.${f}
+
+## Identit\xE9 visuelle (obligatoire)${banner}
+- Utilise des \xE9mojis premium pour chaque section
+- Des tableaux professionnels bord\xE9s par des lignes Markdown
+- Des diagrammes Mermaid
+- Des encadr\xE9s avec > pour les insights et verdicts
+- Des "score cards" : Maturit\xE9, S\xE9curit\xE9, Maintenabilit\xE9, Performance, UX (notes sur 10 avec justification)
+- Des badges textuels : [CRITIQUE], [HIGH-VALUE], [SECURITY], [STRATEGY], [BEST-TECH], [MARKETING], [RECOMMANDATION].
+- Finis par le bloc signature ci-dessous :
+${signature}
+
+## Sections obligatoires (num\xE9rote exactement de 1 \xE0 13)
+1. **Page de Garde** : banni\xE8re, date, projet, version, auteur (DSH Codebase Analysis).
+2. **Executive Summary** : promesse produit, verdict technique, 5 score cards sur 10, argument de pourquoi ce projet peut \xEAtre le meilleur, et alignement avec les contraintes/produits IDENTIFIEES dans le contexte.
+3. **Constat Profond** : diagnostic synth\xE9tique en 3-5 phrases fortes.
+4. **SWOT Strat\xE9gique** : tableau 2x2 (Forces, Faiblesses, Opportunit\xE9s, Menaces).
+5. **Architecture & Tech Radar (Best-of-Breed)** : pour chaque technologie cl\xE9, explique pourquoi c'est le meilleur choix ici, donne un argument massue, un contre-argument, et une alternative classique.
+6. **Module Graph & Connexions** : hubs, feuilles, Mermaid, points de fragilit\xE9.
+7. **S\xE9curit\xE9 & Confidentialit\xE9** : posture, cryptographie, vuln\xE9rabilit\xE9s.
+8. **Qualit\xE9 du Code & Dette** : signaux, top risques, correctifs.
+9. **Produit & UX** : parcours utilisateur, points de friction, id\xE9es d'am\xE9lioration.
+10. **Paysage Concurrentiel** : positionnement vs 3-4 acteurs, avantages diff\xE9renciants, r\xE8gles du jeu du march\xE9.
+11. **Marketing & Positionnement** : persona cible, promesse unique (USP), tagline, canaux d'acquisition, argumentaire "pourquoi on va gagner", et **Master Move** : la feature/strat\xE9gie dominante qui fait gagner, compatible avec les contraintes du projet IDENTIFIEES dans le contexte.
+11b. **Contraintes Produits du Projet** (avant la roadmap) : liste les contraintes explicites identifi\xE9es dans == CONTRAINTES PRODUIT IDENTIFIEES == en d\xE9but de contexte. Si aucune, indique "Aucune contrainte document\xE9e". Cette section sert de r\xE9f\xE9rence pour justifier chaque action.
+12. **Roadmap 90 Jours & Justifications** : 4-6 actions concr\xE8tes prioris\xE9es (semaines 1-4, 5-8, 9-12) pour devenir le meilleur. Chaque action DOIT \xEAtre suivie d'une phrase commen\xE7ant par "> Justification :" qui explique pourquoi elle est coh\xE9rente avec les r\xE8gles du projet. Si aucune contrainte, explique pourquoi elle est adapt\xE9e \xE0 la stack/architecture. Exemple : > Justification : Cette action respecte la r\xE8gle "100% offline" car elle n'utilise aucun backend cloud.
+13. **Fait avec passion par shinzarou-eng** : concept produit/visuel original, slogan percutant, et argumentaire marketing gagnant inspir\xE9 par le code \u2014 dans le respect des contraintes du projet IDENTIFIEES dans le contexte.
+
+Reste factuel, cible les fichiers par leur chemin relatif. Ne g\xE9n\xE9ralise pas hors du contexte. Si aucune contrainte produit n'est document\xE9e, \xE9cris simplement "Contraintes produit : aucune" et continue toutes les sections normalement. NE SAUTE AUCUNE SECTION ET NE PERDS AUCUNE QUESTION. R\xE9ponds dans la langue de l'utilisateur.
+
+## CHECKLIST FINALE (obligatoire, v\xE9rifie avant d'envoyer)
+- [ ] Sections num\xE9rot\xE9es de 1 \xE0 13.
+- [ ] Banni\xE8re ASCII en haut.
+- [ ] 5 score cards avec notes /10.
+- [ ] 1 diagramme Mermaid (architecture, data flow ou module graph).
+- [ ] Chaque action roadmap a un "> Justification :".
+- [ ] Au moins 2 citations de fichiers exactes (ligne).
+- [ ] Conclusion "Fait avec passion par shinzarou-eng".`;
+  const en = `${context}
+
+${langInstruction(lang)}
+
+${styleText}You are an **elite CTO / Technical Partner** writing the **ultimate Professional Assessment** for the project "${projectName}". This document must be the most beautiful, punchy and actionable: a board-ready high-level report. Mission: merge architecture, debt, competition, test/build results, git, marketing AND respect the product constraints IDENTIFIED in the context. Leverage the == PROJECT METRICS == and == KEY CODE SNIPPETS == to cite exact numbers and insert code snippets. Never impose constraints that are not in the context.${f}
+
+## Visual Identity (mandatory)${banner}
+- Use premium emojis for each section
+- Professional tables framed by Markdown lines
+- Mermaid diagrams
+- Quote boxes with > for insights and verdicts
+- "Score cards": Maturity, Security, Maintainability, Performance, UX (scores out of 10 with rationale)
+- Text badges: [CRITICAL], [HIGH-VALUE], [SECURITY], [STRATEGY], [BEST-TECH], [MARKETING], [RECOMMENDATION].
+- End with the signature block below:
+${signature}
+
+## Required Sections (number exactly 1 to 13)
+1. **Cover Page**: banner, date, project, version, author (DSH Codebase Analysis).
+2. **Executive Summary**: product promise, technical verdict, 5 score cards out of 10, argument for why this project can be the best, and alignment with the product constraints IDENTIFIED in the context.
+3. **Deep Diagnosis**: synthetic diagnosis in 3-5 strong sentences.
+4. **Strategic SWOT**: 2x2 table (Strengths, Weaknesses, Opportunities, Threats).
+5. **Architecture & Tech Radar (Best-of-Breed)**: for each key technology, explain why it is the best choice here, give a hard-hitting argument, a counter-argument, and a classic alternative.
+6. **Module Graph & Connections**: hubs, leaves, Mermaid, fragility points.
+7. **Security & Privacy**: posture, cryptography, vulnerabilities.
+8. **Code Quality & Debt**: signals, top risks, fixes.
+9. **Product & UX**: user journey, friction points, improvement ideas.
+10. **Competitive Landscape**: positioning vs 3-4 players, differentiating advantages, market rules.
+11. **Marketing & Positioning**: target persona, unique selling proposition (USP), tagline, acquisition channels, "why we will win" argument, and **Master Move**: the dominant feature/strategy that makes you win, compatible with the product constraints IDENTIFIED in the context.
+11b. **Product Constraints of the Project** (before the roadmap): list the explicit constraints identified in == IDENTIFIED PRODUCT CONSTRAINTS == at the start of the context. If none, indicate "No documented constraints". This section serves as a reference to justify each action.
+12. **90-Day Roadmap & Rationale**: 4-6 prioritized concrete actions (weeks 1-4, 5-8, 9-12) to become the best. Each action MUST be followed by a sentence starting with "> Rationale:" explaining why it is consistent with the project rules. If no constraints, explain why it fits the stack/architecture. Example: > Rationale: This action respects the "100% offline" rule by not using any cloud backend.
+13. **Made with passion by shinzarou-eng**: an original product/visual concept, a punchy slogan, and a winning marketing argument inspired by the code \u2014 respecting the product constraints IDENTIFIED in the context.
+
+Stay factual, target files by their relative path. Do not generalize beyond the context. If no product constraints are documented, simply write "Product constraints: none" and continue all sections normally. DO NOT SKIP ANY SECTION AND DO NOT LOSE ANY QUESTION. Respond in the user's language.
+
+## FINAL CHECKLIST (mandatory, verify before sending)
+- [ ] Sections numbered 1 to 13.
+- [ ] ASCII banner at the top.
+- [ ] 5 score cards with scores out of 10.
+- [ ] 1 Mermaid diagram (architecture, data flow or module graph).
+- [ ] Each roadmap action has a "> Rationale:".
+- [ ] At least 2 exact file citations (line).
+- [ ] Conclusion "Made with passion by shinzarou-eng".`;
+  return withCitations(isEn ? en : fr, lang);
+}
+function buildTasksPrompt(context, projectName, focus = "", style = "punchy", lang = "fr") {
+  const isEn = lang === "en";
+  const f = focus ? isEn ? `
+Requested focus: ${focus}` : `
+Focus demand\xE9 : ${focus}` : "";
+  const styleText = styleInstruction(style, lang);
+  const banner = bannerInstruction(projectName, isEn ? "TASKS Action Plan" : "Plan d'Action TASKS", isEn ? "EXECUTABLE ROADMAP AND PRIORITIZED SPRINTS" : "ROADMAP EX\xC9CUTABLE ET SPRINTS PRIORIS\xC9S");
+  const fr = `${context}
+
+${langInstruction(lang)}
+
+${styleText}Tu es un **Delivery Lead / CTO** qui transforme un rapport de codebase en **plan d'action ex\xE9cutable** pour le projet "${projectName}". R\xC8GLE D'OR : la section == T\xC2CHES G\xC9N\xC9R\xC9ES DEPUIS LES SIGNAUX == contient d\xE9j\xE0 les t\xE2ches avec leurs blocs Avant/Apr\xE8s. Tu DOIS les recopier TELLES QUELLES dans le TASKS.md final, les organiser en sprints (P0, P1, P2, P3), et conserver OBLIGATOIREMENT les blocs Avant et Apr\xE8s FOURNIS. Tu as le droit d'ajouter 2-3 t\xE2ches maximum si tu identifies un risque majeur absent, mais la majorit\xE9 du plan doit venir des t\xE2ches pr\xE9-g\xE9n\xE9r\xE9es. Chaque t\xE2che doit \xEAtre compatible avec les contraintes produit IDENTIFIEES dans le contexte (README, MEMORY.md, package.json). Avant la liste des t\xE2ches, ajoute une section "Contraintes produit identifi\xE9es" pour servir de r\xE9f\xE9rence.${f}
+
+## Ton et style${banner}
+- Un titre clair :
+~~~markdown
+# TASKS.md \u2014 Plan d'action ${projectName}
+~~~
+- Des tableaux avec colonnes : Priorit\xE9, T\xE2che, Fichier(s) concern\xE9(s), Difficult\xE9 (1-5), Impact, Livrable
+- Des checklists Markdown : '[ ]' / '[x]'
+- Des sprints : Sprint 1 (semaines 1-2), Sprint 2, Sprint 3
+- Des badges : [CRITIQUE], [RAPIDE], [STRATEGIQUE], [TECH-DEBT].
+- Conclus par : Fait avec passion par shinzarou-eng (dans la langue de l'utilisateur)
+
+## Sections obligatoires
+1. **Vue d'ensemble** : 3-5 t\xE2ches prioritaires dans un tableau.
+2. **Sprint 1 \u2014 Fondations** : s\xE9curit\xE9, stabilit\xE9, tests.
+3. **Sprint 2 \u2014 Am\xE9lioration** : refacto, UX, performance.
+4. **Sprint 3 \u2014 Diff\xE9renciation** : features gagnantes, marketing.
+5. **Checklist globale** : toutes les t\xE2ches avec '[ ]'.
+
+Chaque t\xE2che doit \xEAtre actionnable, citer un chemin de fichier relatif quand c'est possible, et \xEAtre suivie d'une phrase commen\xE7ant par "> Justification :" qui explique pourquoi elle est coh\xE9rente avec les r\xE8gles du projet.
+
+## Exigence AVANT / APR\xC8S
+Pour CHAQUE t\xE2che, ajoute obligatoirement deux blocs de code :
+- **Avant** : extrait du code actuel (max 10 lignes) depuis le contexte == TECH DEBT & SIGNALS == ou == EXTRAITS DE CODE CL\xC9S ==.
+- **Apr\xE8s** : extrait du code corrig\xE9 propos\xE9 (max 10 lignes).
+
+Exemple de format :
+- [ ] **[TASK-01] Typer l'\xE9v\xE9nement SpeechRecognition**
+  - Fichier : src/components/KodaAssistantModal.tsx:651
+  - Avant :
+    --- code ts ---
+    recognition.onresult = (event: any) => { ... };
+    ---
+  - Apr\xE8s :
+    --- code ts ---
+    recognition.onresult = (event: SpeechRecognitionEvent) => { ... };
+    ---
+  > Justification : ...
+
+Si tu ne peux pas extraire l'extrait, cite au minimum le fichier et la ligne.
+
+## CHECKLIST FINALE (obligatoire, v\xE9rifie avant d'envoyer)
+- [ ] 5 sections pr\xE9sentes (Vue d'ensemble, Sprint 1, Sprint 2, Sprint 3, Checklist globale).
+- [ ] Toutes les t\xE2ches ont un statut '[ ]'.
+- [ ] Chaque t\xE2che a un bloc **Avant** (code actuel) et un bloc **Apr\xE8s** (code propos\xE9), ou 'N/A' avec explication.
+- [ ] Chaque t\xE2che a un Fichier:Ligne.
+- [ ] Chaque t\xE2che a un "> Justification :".
+- [ ] Conclusion "Fait avec passion par shinzarou-eng".
+
+Si aucune contrainte n'est trouv\xE9e, \xE9cris "Contraintes produit : aucune" et continue toutes les sections normalement. NE SAUTE AUCUNE SECTION ET NE PERDS AUCUNE QUESTION.`;
+  const en = `${context}
+
+${langInstruction(lang)}
+
+${styleText}You are a **Delivery Lead / CTO** turning a codebase report into an **executable action plan** for the project "${projectName}". GOLDEN RULE: the section == TASKS GENERATED FROM SIGNALS == already contains the tasks with their Before/After blocks. You MUST copy them AS-IS into the final TASKS.md, organize them into sprints (P0, P1, P2, P3), and OBLIGATORILY keep the provided Before and After blocks. You may add 2-3 extra tasks at most if you identify a major missing risk, but the majority of the plan must come from the pre-generated tasks. Each task must be compatible with the product constraints IDENTIFIED in the context (README, MEMORY.md, package.json). Before the task list, add an "Identified product constraints" section as a reference.${f}
+
+## Tone & Style${banner}
+- A clear title:
+~~~markdown
+# TASKS.md \u2014 Action Plan ${projectName}
+~~~
+- Tables with columns: Priority, Task, Concerned file(s), Difficulty (1-5), Impact, Deliverable
+- Markdown checklists: '[ ]' / '[x]'
+- Sprints: Sprint 1 (weeks 1-2), Sprint 2, Sprint 3
+- Badges: [CRITICAL], [QUICK], [STRATEGIC], [TECH-DEBT].
+- Conclude with: Made with passion by shinzarou-eng (in the user's language)
+
+## Required Sections
+1. **Overview**: 3-5 prioritized tasks in a table.
+2. **Sprint 1 \u2014 Foundations**: security, stability, tests.
+3. **Sprint 2 \u2014 Improvement**: refactor, UX, performance.
+4. **Sprint 3 \u2014 Differentiation**: winning features, marketing.
+5. **Global Checklist**: all tasks with '[ ]'.
+
+Each task must be actionable, cite a relative file path when possible, and be followed by a sentence starting with "> Rationale:" explaining why it is consistent with the project rules.
+
+## BEFORE / AFTER Requirement
+For EACH task, you MUST add two code blocks:
+- **Before**: current code snippet (max 10 lines) from == TECH DEBT & SIGNALS == or == KEY CODE SNIPPETS == in the context.
+- **After**: proposed fixed code snippet (max 10 lines).
+
+Example format:
+- [ ] **[TASK-01] Type the SpeechRecognition event**
+  - File: src/components/KodaAssistantModal.tsx:651
+  - Before:
+    --- code ts ---
+    recognition.onresult = (event: any) => { ... };
+    ---
+  - After:
+    --- code ts ---
+    recognition.onresult = (event: SpeechRecognitionEvent) => { ... };
+    ---
+  > Rationale : ...
+
+If you cannot extract the snippet, at least cite the file and line.
+
+## FINAL CHECKLIST (mandatory, verify before sending)
+- [ ] 5 sections present (Overview, Sprint 1, Sprint 2, Sprint 3, Global Checklist).
+- [ ] All tasks have status '[ ]'.
+- [ ] Each task has a **Before** (current code) and an **After** (proposed code) block, or 'N/A' with explanation.
+- [ ] Each task has a File:Line.
+- [ ] Each task has a "> Rationale:".
+- [ ] Conclusion "Made with passion by shinzarou-eng".
+
+If no constraints are found, write "Product constraints: none" and continue all sections normally. DO NOT SKIP ANY SECTION AND DO NOT LOSE ANY QUESTION.`;
+  return withCitations(isEn ? en : fr, lang);
+}
+function buildCeoPrompt(context, projectName, focus = "", lang = "fr") {
+  const isEn = lang === "en";
+  const f = focus ? isEn ? `
+Requested focus: ${focus}` : `
+Focus demand\xE9 : ${focus}` : "";
+  const styleText = styleInstruction("ouf", lang);
+  const signature = brandSignature(lang);
+  const banner = bannerInstruction(projectName, isEn ? "One-Page CEO Brief" : "One-Page CEO Brief", isEn ? "EXECUTIVE SUMMARY FOR DECISION MAKERS" : "EXECUTIVE SUMMARY POUR D\xC9CIDEUR");
+  const fr = `${context}
+
+${langInstruction(lang)}
+
+${styleText}Tu es un **CTO / CEO / Partner** qui r\xE9dige le **One-Page Executive Brief** ultime sur le projet "${projectName}". R\xC8GLE D'OR : ce document tient sur UNE SEULE PAGE A4. MAXIMUM 7 sections courtes. Pas de blabla, que des insights \xE0 fort impact, des chiffres, des verdicts, des actions. Chaque section max 5-8 lignes. Utilise tableaux et listes. Si tu d\xE9passes une page, tu as \xE9chou\xE9.${f}
+
+## Identit\xE9 visuelle (obligatoire)${banner}
+- Tableau ex\xE9cutif unique avec les metrics cl\xE9s.
+- 5 score cards (sur 10) avec justification en UNE phrase.
+- Encadr\xE9s visuels pour les insights.
+- Badges : [CRITIQUE], [HIGH-VALUE], [STRATEGY], [BEST-TECH], [KILLER-MOVE], [MARKETING].
+- Conclus par le bloc signature ci-dessous :
+${signature}
+
+## Sections obligatoires (num\xE9rote de 1 \xE0 7, STRICTEMENT 1 PAGE)
+1. **Banni\xE8re & Titre** : 1 ligne.
+2. **Executive Summary** : 3 phrases + 1 tableau 4 m\xE9triques.
+3. **Verdict du board** : 5 score cards, 1 ligne chacune (Domaine | Note | 5 mots de justification).
+4. **Top 3 risques / dette** : 1 ligne par risque (Fichier:Ligne - Probl\xE8me - Impact).
+5. **Top 3 opportunit\xE9s / Killer Moves** : 1 phrase par action + Justification en 1 phrase.
+6. **SWOT ultra-concis** : 4 cases, max 4 points de 3-5 mots chacun.
+7. **Fait avec passion par shinzarou-eng** : 1 concept + 1 slogan + 1 phrase marketing.
+
+Reste factuel, cible les fichiers par leur chemin relatif. Exploite les == M\xC9TRIQUES PROJET == et == EXTRAITS DE CODE CL\xC9S ==. R\xE9ponds dans la langue de l'utilisateur.
+
+## CHECKLIST FINALE (obligatoire, v\xE9rifie avant d'envoyer)
+- [ ] Exactement 7 sections num\xE9rot\xE9es.
+- [ ] Le document tient sur une page (max 60-80 lignes au total).
+- [ ] 5 score cards, 1 ligne chacune.
+- [ ] Top 3 risques avec Fichier:Ligne.
+- [ ] Top 3 opportunit\xE9s avec "> Justification :".
+- [ ] SWOT : 4 points de 3-5 mots par case.
+- [ ] Aucun Mermaid, aucun tableau g\xE9ant, aucune explication longue.`;
+  const en = `${context}
+
+${langInstruction(lang)}
+
+${styleText}You are a **CTO / CEO / Partner** writing the ultimate **One-Page Executive Brief** for the project "${projectName}". GOLDEN RULE: this document fits on a SINGLE A4 page. MAXIMUM 7 short sections. No filler, only high-impact insights, numbers, verdicts, actions. Each section max 5-8 lines. Use tables and lists. If you exceed one page, you failed.${f}
+
+## Visual Identity (mandatory)${banner}
+- Single executive table with key metrics.
+- 5 score cards (out of 10) with rationale in ONE sentence.
+- Visual callouts for insights.
+- Badges: [CRITICAL], [HIGH-VALUE], [STRATEGY], [BEST-TECH], [KILLER-MOVE], [MARKETING].
+- Conclude with the signature block below:
+${signature}
+
+## Required Sections (number 1 to 7, STRICTLY 1 PAGE)
+1. **Banner & Title**: 1 line.
+2. **Executive Summary**: 3 sentences + 1 table with 4 metrics.
+3. **Board verdict**: 5 score cards, 1 line each (Area | Score | 5-word rationale).
+4. **Top 3 risks / debt**: 1 line per risk (File:Line - Problem - Impact).
+5. **Top 3 opportunities / Killer Moves**: 1 sentence per action + Rationale in 1 sentence.
+6. **Ultra-concise SWOT**: 4 boxes, max 4 points of 3-5 words each.
+7. **Made with passion by shinzarou-eng**: 1 concept + 1 slogan + 1 marketing sentence.
+
+Stay factual, target files by their relative path. Leverage == PROJECT METRICS == and == KEY CODE SNIPPETS ==. Respond in the user's language.
+
+## FINAL CHECKLIST (mandatory, verify before sending)
+- [ ] Exactly 7 numbered sections.
+- [ ] Document fits on one page (max 60-80 lines total).
+- [ ] 5 score cards, 1 line each.
+- [ ] Top 3 risks with File:Line.
+- [ ] Top 3 opportunities with "> Rationale:".
+- [ ] SWOT: 4 points of 3-5 words per box.
+- [ ] No Mermaid, no giant table, no long explanation.`;
+  return withCitations(isEn ? en : fr, lang);
+}
+function buildPlayerPrompt(context, projectName, focus = "", lang = "fr") {
+  const isEn = lang === "en";
+  const f = focus ? isEn ? `
+Requested focus: ${focus}` : `
+Focus demand\xE9 : ${focus}` : "";
+  const banner = bannerInstruction(projectName, isEn ? "Player Brief" : "Player Brief", isEn ? "USER JOURNEY & EXPERIENCE" : "PARCOURS UTILISATEUR & EXP\xC9RIENCE");
+  const fr = `${context}
+
+${langInstruction(lang)}
+
+${banner}
+
+Tu es un **UX Researcher / Playtester / Product Hunter** qui r\xE9alise un **Player Brief** sur le projet "${projectName}". Tu ne regardes pas le code comme un dev, mais comme un vrai utilisateur final qui d\xE9couvre l'app, clique, se frustre, se r\xE9jouit. Mission : d\xE9crire l'exp\xE9rience v\xE9cue, identifier les moments cl\xE9s, les frictions et les opportunit\xE9s de 'wow'.${f}
+
+## Format attendu
+- Banni\xE8re ASCII : "PLAYER BRIEF \u2014 ${(projectName ?? "").toUpperCase()}"
+- Score cards : Onboarding, Clart\xE9, R\xE9activit\xE9, Confiance, Plaisir (sur 10)
+- Tableau du parcours utilisateur : \xC9tape, Action, Sentiment, Friction, Fix
+- Top 5 moments 'Wow' (ce qui impressionne)
+- Top 5 frictions bloquantes ou irritantes
+- Id\xE9es de gamification / engagement (si pertinent)
+- Roadmap UX 30 jours : 3 actions rapides d'impact utilisateur
+- Conclusion : Fait avec passion par shinzarou-eng (langue utilisateur)`;
+  const en = `${context}
+
+${langInstruction(lang)}
+
+${banner}
+
+You are a **UX Researcher / Playtester / Product Hunter** producing a **Player Brief** for the project "${projectName}". You do not look at the code like a dev, but like a real end user discovering the app, clicking, getting frustrated, getting delighted. Mission: describe the lived experience, identify key moments, frictions and 'wow' opportunities.${f}
+
+## Expected format
+- ASCII banner: "PLAYER BRIEF \u2014 ${(projectName ?? "").toUpperCase()}"
+- Score cards: Onboarding, Clarity, Responsiveness, Trust, Delight (out of 10)
+- User journey table: Step, Action, Sentiment, Friction, Fix
+- Top 5 'Wow' moments (what impresses)
+- Top 5 blocking or annoying frictions
+- Gamification / engagement ideas (if relevant)
+- 30-day UX roadmap: 3 quick high-impact actions
+- Conclusion: Made with passion by shinzarou-eng (user language)`;
+  return withCitations(isEn ? en : fr, lang);
+}
+var TOOL_BUILDERS = {
+  codebase_intelligence: (o) => buildIntelligencePrompt(o.context, o.projectName, o.focus || o.query || "", o.style || "ouf", o.lang || "fr"),
+  codebase_report: (o) => buildReportPrompt(o.context, o.projectName, o.focus || o.query || "", o.style || "ouf", o.lang || "fr"),
+  codebase_audit: (o) => buildAuditPrompt(o.context, o.projectName, o.focus || o.query || "", o.lang || "fr"),
+  codebase_tasks: (o) => buildTasksPrompt(o.context, o.projectName, o.focus || o.query || "", o.style || "ouf", o.lang || "fr"),
+  codebase_ceo: (o) => buildCeoPrompt(o.context, o.projectName, o.focus || o.query || "", o.lang || "fr"),
+  codebase_player: (o) => buildPlayerPrompt(o.context, o.projectName, o.focus || o.query || "", o.lang || "fr"),
+  codebase_search: (o) => buildSearchPrompt(o.query || o.focus || "", o.context, o.projectName, o.crea, o.creaTheme, o.lang || "fr"),
+  codebase_explain: (o) => buildExplainPrompt(o.filePath || o.query || o.focus || "", o.context, o.projectName, o.crea, o.creaTheme, o.lang || "fr"),
+  codebase_refactor: (o) => buildRefactorPrompt(o.filePath || o.focus || "", o.description || o.query || "", o.context, o.projectName, o.crea, o.creaTheme, o.lang || "fr"),
+  codebase_chat: (o) => buildChatPrompt(o.query || o.focus || "", o.context, o.projectName, o.crea, o.creaTheme, o.lang || "fr"),
+  codebase_crea: (o) => buildCreaPrompt(o.focus || o.query || "creative idea", o.context, o.projectName, o.lang || "fr")
+};
+function buildToolPrompt(tool, opts) {
+  const builder = TOOL_BUILDERS[tool];
+  if (!builder) throw new Error(`unknown prompt tool: ${tool}`);
+  return normalizeLabels(builder(opts), opts.lang || "fr");
+}
+
+// src/local-llm.ts
+import { existsSync as existsSync2 } from "fs";
+import { join as join8 } from "path";
+var DEFAULT_MODEL_URI = "hf:Qwen/Qwen2.5-1.5B-Instruct-GGUF:Q4_K_M";
+var LOCAL_CONTEXT_SIZE = 8192;
+var LOCAL_MAX_TOKENS = 1024;
+function isLocalLlmEnabled() {
+  return !!(process.env.CODEBASE_LOCAL_LLM || "").trim();
+}
+function configuredModel() {
+  const v = (process.env.CODEBASE_LOCAL_LLM || "").trim();
+  if (!v || v === "1" || v.toLowerCase() === "true") return DEFAULT_MODEL_URI;
+  return v;
+}
+async function importLlama() {
+  try {
+    return await import("node-llama-cpp");
+  } catch {
+    throw new Error("Local LLM needs the optional dependency: npm i node-llama-cpp");
+  }
+}
+var modelPromise = null;
+function loadLocalModel() {
+  if (!modelPromise) {
+    modelPromise = (async () => {
+      const spec = configuredModel();
+      let modelPath = spec;
+      if (spec.startsWith("hf:")) {
+        const { createModelDownloader } = await importLlama();
+        const downloader = await createModelDownloader({
+          modelUri: spec,
+          dirPath: join8(getCacheDir(), "models")
+        });
+        modelPath = await downloader.download();
+      } else if (!existsSync2(spec)) {
+        throw new Error(`Local model not found: ${spec}`);
+      }
+      const { getLlama } = await importLlama();
+      const llama = await getLlama();
+      return llama.loadModel({ modelPath });
+    })();
+    modelPromise.catch(() => {
+      modelPromise = null;
+    });
+  }
+  return modelPromise;
+}
+async function callLocalLlm(prompt, lang = "fr") {
+  const model = await loadLocalModel();
+  const { LlamaChatSession } = await importLlama();
+  const context = await model.createContext({ contextSize: LOCAL_CONTEXT_SIZE });
+  try {
+    const session = new LlamaChatSession({
+      contextSequence: context.getSequence(),
+      systemPrompt: lang === "en" ? "You are a senior codebase analyst. Be precise and cite files with [source: path:line]." : "Tu es un analyste codebase senior. Sois precis et cite les fichiers avec [source: chemin:ligne]."
+    });
+    return await session.prompt(prompt, { temperature: 0.2, maxTokens: LOCAL_MAX_TOKENS });
+  } finally {
+    await context.dispose();
+  }
+}
+
 // src/cli.ts
 var ExitSignal = class {
   constructor(code) {
@@ -1795,6 +2616,9 @@ Usage:
   npx dsh-codebase-chat --project <path> --impact src/store.ts
   npx dsh-codebase-chat --project <path> --health --diff main
   npx dsh-codebase-chat --project <path> --watch
+  npx dsh-codebase-chat --project <path> --prompt intelligence
+  npx dsh-codebase-chat --project <path> --prompt intelligence --call   # answered via DEEPSEEK_API_KEY
+  npx dsh-codebase-chat --project <path> --prompt intelligence --local  # answered 100% offline
 
 Options:
   -p, --project <path>   Project directory (default: current directory)
@@ -1806,6 +2630,17 @@ Options:
   -H, --health           Deterministic static analysis (cycles, dead code, dupes, complexity)
   --impact <file>        Blast radius \u2014 which files transitively depend on <file>
   -d, --diff <ref>       Scope --ask/--search/--health to files changed vs a git ref
+  --prompt <mode>        Print the full LLM prompt (banner + instructions) for a
+                         report mode: intelligence, report, audit, tasks, ceo,
+                         player, chat, search, explain, refactor, crea.
+                         Pipe it to any LLM (e.g. ... --prompt intelligence | dsh).
+                         Query modes read --ask/--search/--file; --focus and
+                         --style (ouf|punchy|dense|pedagogique|minimal) apply.
+  --call                 With --prompt: send it to the API (needs DEEPSEEK_API_KEY
+                         or OPENAI_API_KEY; DEEPSEEK_BASE_URL / CODEBASE_MODEL
+                         customize endpoint/model) instead of printing it.
+  --local                With --prompt: answer with the embedded local model
+                         (node-llama-cpp, ~1 GB download on first use, offline).
   -w, --watch            Keep the index hot \u2014 rebuild incrementally on file changes
   -e, --embed            Enable local semantic embeddings (slower, more relevant)
   --lang <en|fr>         Language for headings (default: .codebase-chat.json lang, else fr)
@@ -1831,6 +2666,11 @@ async function main() {
       health: { type: "boolean", short: "H", default: false },
       impact: { type: "string" },
       diff: { type: "string", short: "d" },
+      prompt: { type: "string" },
+      focus: { type: "string" },
+      style: { type: "string" },
+      call: { type: "boolean", default: false },
+      local: { type: "boolean", default: false },
       watch: { type: "boolean", short: "w", default: false },
       embed: { type: "boolean", short: "e", default: false },
       lang: { type: "string" },
@@ -1919,6 +2759,91 @@ async function main() {
     console.log(formatImpactReport(r.report, lang));
     exit(0);
   }
+  if (values.prompt) {
+    const mode = values.prompt.toLowerCase();
+    const tool = `codebase_${mode}`;
+    const needsQuery = /* @__PURE__ */ new Set(["chat", "search", "explain", "refactor", "crea"]);
+    const query = values.ask ?? values.search ?? values.focus ?? "";
+    if (needsQuery.has(mode) && !query && !values.file) {
+      console.error(lang === "en" ? `--prompt ${mode} needs a query: add --ask/--search/--file (or --focus)` : `--prompt ${mode} n\xE9cessite une requ\xEAte : ajoute --ask/--search/--file (ou --focus)`);
+      exit(1);
+    }
+    const result = await buildContext({
+      project: values.project,
+      query,
+      searchQuery: values.search,
+      filePath: values.file,
+      lang,
+      embed: values.embed,
+      diff: values.diff
+    });
+    let staticSection = "";
+    if ((/* @__PURE__ */ new Set(["intelligence", "report", "audit", "tasks", "ceo"])).has(mode)) {
+      try {
+        const report = await analyzeProject(result.absProject);
+        staticSection = `
+
+== ${lang === "en" ? "STATIC ANALYSIS (deterministic)" : "ANALYSE STATIQUE (d\xE9terministe)"} ==
+${formatHealthReport(report, lang)}`;
+      } catch {
+      }
+    }
+    const projectName = basename3(result.absProject);
+    let prompt;
+    try {
+      prompt = buildToolPrompt(tool, {
+        context: `${result.context}${staticSection}`,
+        projectName,
+        lang,
+        style: values.style,
+        query,
+        focus: values.focus ?? query,
+        filePath: values.file ?? "",
+        description: query
+      });
+    } catch {
+      console.error(lang === "en" ? `unknown prompt mode "${mode}" \u2014 expected: intelligence, report, audit, tasks, ceo, player, chat, search, explain, refactor, crea` : `mode de prompt inconnu "${mode}" \u2014 attendu : intelligence, report, audit, tasks, ceo, player, chat, search, explain, refactor, crea`);
+      exit(1);
+    }
+    if (values.local || isLocalLlmEnabled()) {
+      console.error(lang === "en" ? "Answering with the embedded local model (first run downloads ~1 GB)..." : "R\xE9ponse via le mod\xE8le local embarqu\xE9 (premier lancement : ~1 Go de t\xE9l\xE9chargement)...");
+      console.log(await callLocalLlm(prompt, lang));
+      exit(0);
+    }
+    if (values.call) {
+      const apiKey = process.env.DEEPSEEK_API_KEY || process.env.OPENAI_API_KEY || "";
+      if (!apiKey) {
+        console.error(lang === "en" ? "--call needs DEEPSEEK_API_KEY or OPENAI_API_KEY in the environment" : "--call n\xE9cessite DEEPSEEK_API_KEY ou OPENAI_API_KEY dans l\u2019environnement");
+        exit(1);
+      }
+      const baseUrl = process.env.DEEPSEEK_BASE_URL || process.env.OPENAI_BASE_URL || "https://api.deepseek.com/v1";
+      const model = process.env.CODEBASE_MODEL || "deepseek-chat";
+      const res = await fetch(`${baseUrl}/chat/completions`, {
+        method: "POST",
+        signal: AbortSignal.timeout(12e4),
+        headers: { "Content-Type": "application/json", Authorization: `Bearer ${apiKey}` },
+        body: JSON.stringify({
+          model,
+          messages: [
+            { role: "system", content: lang === "en" ? "You are a senior codebase analyst. Be precise and cite files." : "Tu es un analyste codebase senior. Sois pr\xE9cis et cite les fichiers." },
+            { role: "user", content: prompt }
+          ],
+          temperature: 0.3,
+          max_tokens: 8192
+        })
+      });
+      if (!res.ok) {
+        const text = await res.text().catch(() => "");
+        console.error(`API error ${res.status}: ${text}`);
+        exit(1);
+      }
+      const data = await res.json();
+      console.log(data.choices?.[0]?.message?.content || "");
+      exit(0);
+    }
+    console.log(prompt);
+    exit(0);
+  }
   if (values.ask || values.search || values.file) {
     const result = await buildContext({
       project: values.project,