@vinaes/succ 1.3.31 → 1.5.37

package/dist/prompts/index.d.ts

@@ -3,15 +3,25 @@
  *
  * All prompts used in succ are exported from this module.
  * This makes it easy to find, review, and modify prompts.
+ *
+ * Naming convention:
+ *   *_SYSTEM — stable instructions (cached by LLM providers)
+ *   *_PROMPT — user template with {placeholders} for dynamic content
  */
 export { ONBOARDING_SYSTEM_PROMPT, WIZARD_INTRO, WIZARD_DISCOVERY_PROJECT, WIZARD_DISCOVERY_FRUSTRATION, WIZARD_SOLUTION_MAP, WIZARD_CONCEPTS_OVERVIEW, WIZARD_HANDS_ON_PROMPT, WIZARD_CHEATSHEET, WIZARD_DONE, } from './onboarding.js';
 export { CHAT_SYSTEM_PROMPT } from './chat.js';
-export { BRIEFING_STRUCTURED_PROMPT, BRIEFING_PROSE_PROMPT, BRIEFING_MINIMAL_PROMPT, SESSION_BRIEFING_PROMPT, } from './briefing.js';
-export { FACT_EXTRACTION_PROMPT, SESSION_PROGRESS_EXTRACTION_PROMPT } from './extraction.js';
-export { MEMORY_MERGE_PROMPT } from './memory.js';
-export { KEYWORD_EXTRACTION_PROMPT, SKILL_RANKING_PROMPT } from './skills.js';
-export { REFLECTION_PROMPT, DISCOVERY_PROMPT } from './daemon.js';
-export { PROJECT_ANALYSIS_WRAPPER, DOCUMENTATION_WRITER_SYSTEM } from './analyze.js';
+export { BRIEFING_STRUCTURED_SYSTEM, BRIEFING_STRUCTURED_PROMPT, BRIEFING_PROSE_SYSTEM, BRIEFING_PROSE_PROMPT, BRIEFING_MINIMAL_SYSTEM, BRIEFING_MINIMAL_PROMPT, SESSION_BRIEFING_SYSTEM, SESSION_BRIEFING_PROMPT, } from './briefing.js';
+export { FACT_EXTRACTION_SYSTEM, FACT_EXTRACTION_PROMPT, SESSION_PROGRESS_EXTRACTION_PROMPT, } from './extraction.js';
+export { MEMORY_MERGE_SYSTEM, MEMORY_MERGE_PROMPT, TEMPORAL_SUBQUERY_SYSTEM } from './memory.js';
+export { KEYWORD_EXTRACTION_SYSTEM, KEYWORD_EXTRACTION_PROMPT, SKILL_RANKING_SYSTEM, SKILL_RANKING_PROMPT, } from './skills.js';
+export { REFLECTION_SYSTEM, REFLECTION_PROMPT, DISCOVERY_SYSTEM, DISCOVERY_PROMPT, } from './daemon.js';
+export { PROJECT_ANALYSIS_WRAPPER, DOCUMENTATION_WRITER_SYSTEM, DOCUMENTATION_WRITER_SYSTEM_SHORT, } from './analyze.js';
 export { QUALITY_SCORER_SYSTEM } from './quality.js';
-export { PRD_GENERATE_PROMPT, PRD_PARSE_PROMPT, TASK_EXECUTION_PROMPT } from './prd.js';
+export { EXPANSION_SYSTEM, EXPANSION_PROMPT } from './query-expansion.js';
+export { CLASSIFY_SYSTEM, CLASSIFY_PROMPT_SINGLE, CLASSIFY_PROMPT_BATCH } from './graph.js';
+export { SUPERSESSION_SYSTEM, SUPERSESSION_PROMPT } from './supersession.js';
+export { SYNTHESIS_SYSTEM, SYNTHESIS_PROMPT } from './synthesis.js';
+export { PRD_GENERATE_SYSTEM, PRD_GENERATE_PROMPT, PRD_PARSE_SYSTEM, PRD_PARSE_PROMPT, TASK_EXECUTION_SYSTEM, TASK_EXECUTION_USER_PROMPT, } from './prd.js';
+export { SOUL_GENERATION_SYSTEM } from './soul.js';
+export { SENSITIVITY_SYSTEM, CODE_POLICY_SYSTEM, INJECTION_DETECTION_SYSTEM, SENSITIVITY_LG_CATEGORIES, CODE_POLICY_LG_CATEGORIES, INJECTION_LG_CATEGORIES, } from './guardrails.js';
 //# sourceMappingURL=index.d.ts.map

package/dist/prompts/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/prompts/index.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAGH,OAAO,EACL,wBAAwB,EACxB,YAAY,EACZ,wBAAwB,EACxB,4BAA4B,EAC5B,mBAAmB,EACnB,wBAAwB,EACxB,sBAAsB,EACtB,iBAAiB,EACjB,WAAW,GACZ,MAAM,iBAAiB,CAAC;AAGzB,OAAO,EAAE,kBAAkB,EAAE,MAAM,WAAW,CAAC;AAG/C,OAAO,EACL,0BAA0B,EAC1B,qBAAqB,EACrB,uBAAuB,EACvB,uBAAuB,GACxB,MAAM,eAAe,CAAC;AAGvB,OAAO,EAAE,sBAAsB,EAAE,kCAAkC,EAAE,MAAM,iBAAiB,CAAC;AAG7F,OAAO,EAAE,mBAAmB,EAAE,MAAM,aAAa,CAAC;AAGlD,OAAO,EAAE,yBAAyB,EAAE,oBAAoB,EAAE,MAAM,aAAa,CAAC;AAG9E,OAAO,EAAE,iBAAiB,EAAE,gBAAgB,EAAE,MAAM,aAAa,CAAC;AAGlE,OAAO,EAAE,wBAAwB,EAAE,2BAA2B,EAAE,MAAM,cAAc,CAAC;AAGrF,OAAO,EAAE,qBAAqB,EAAE,MAAM,cAAc,CAAC;AAGrD,OAAO,EAAE,mBAAmB,EAAE,gBAAgB,EAAE,qBAAqB,EAAE,MAAM,UAAU,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/prompts/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAGH,OAAO,EACL,wBAAwB,EACxB,YAAY,EACZ,wBAAwB,EACxB,4BAA4B,EAC5B,mBAAmB,EACnB,wBAAwB,EACxB,sBAAsB,EACtB,iBAAiB,EACjB,WAAW,GACZ,MAAM,iBAAiB,CAAC;AAGzB,OAAO,EAAE,kBAAkB,EAAE,MAAM,WAAW,CAAC;AAG/C,OAAO,EACL,0BAA0B,EAC1B,0BAA0B,EAC1B,qBAAqB,EACrB,qBAAqB,EACrB,uBAAuB,EACvB,uBAAuB,EACvB,uBAAuB,EACvB,uBAAuB,GACxB,MAAM,eAAe,CAAC;AAGvB,OAAO,EACL,sBAAsB,EACtB,sBAAsB,EACtB,kCAAkC,GACnC,MAAM,iBAAiB,CAAC;AAGzB,OAAO,EAAE,mBAAmB,EAAE,mBAAmB,EAAE,wBAAwB,EAAE,MAAM,aAAa,CAAC;AAGjG,OAAO,EACL,yBAAyB,EACzB,yBAAyB,EACzB,oBAAoB,EACpB,oBAAoB,GACrB,MAAM,aAAa,CAAC;AAGrB,OAAO,EACL,iBAAiB,EACjB,iBAAiB,EACjB,gBAAgB,EAChB,gBAAgB,GACjB,MAAM,aAAa,CAAC;AAGrB,OAAO,EACL,wBAAwB,EACxB,2BAA2B,EAC3B,iCAAiC,GAClC,MAAM,cAAc,CAAC;AAGtB,OAAO,EAAE,qBAAqB,EAAE,MAAM,cAAc,CAAC;AAGrD,OAAO,EAAE,gBAAgB,EAAE,gBAAgB,EAAE,MAAM,sBAAsB,CAAC;AAG1E,OAAO,EAAE,eAAe,EAAE,sBAAsB,EAAE,qBAAqB,EAAE,MAAM,YAAY,CAAC;AAG5F,OAAO,EAAE,mBAAmB,EAAE,mBAAmB,EAAE,MAAM,mBAAmB,CAAC;AAG7E,OAAO,EAAE,gBAAgB,EAAE,gBAAgB,EAAE,MAAM,gBAAgB,CAAC;AAGpE,OAAO,EACL,mBAAmB,EACnB,mBAAmB,EACnB,gBAAgB,EAChB,gBAAgB,EAChB,qBAAqB,EACrB,0BAA0B,GAC3B,MAAM,UAAU,CAAC;AAGlB,OAAO,EAAE,sBAAsB,EAAE,MAAM,WAAW,CAAC;AAGnD,OAAO,EACL,kBAAkB,EAClB,kBAAkB,EAClB,0BAA0B,EAC1B,yBAAyB,EACzB,yBAAyB,EACzB,uBAAuB,GACxB,MAAM,iBAAiB,CAAC"}

package/dist/prompts/index.js

@@ -3,25 +3,41 @@
  *
  * All prompts used in succ are exported from this module.
  * This makes it easy to find, review, and modify prompts.
+ *
+ * Naming convention:
+ *   *_SYSTEM — stable instructions (cached by LLM providers)
+ *   *_PROMPT — user template with {placeholders} for dynamic content
  */
 // Onboarding prompts
 export { ONBOARDING_SYSTEM_PROMPT, WIZARD_INTRO, WIZARD_DISCOVERY_PROJECT, WIZARD_DISCOVERY_FRUSTRATION, WIZARD_SOLUTION_MAP, WIZARD_CONCEPTS_OVERVIEW, WIZARD_HANDS_ON_PROMPT, WIZARD_CHEATSHEET, WIZARD_DONE, } from './onboarding.js';
 // Chat prompts
 export { CHAT_SYSTEM_PROMPT } from './chat.js';
 // Briefing prompts (compact-briefing, precompute-context)
-export { BRIEFING_STRUCTURED_PROMPT, BRIEFING_PROSE_PROMPT, BRIEFING_MINIMAL_PROMPT, SESSION_BRIEFING_PROMPT, } from './briefing.js';
+export { BRIEFING_STRUCTURED_SYSTEM, BRIEFING_STRUCTURED_PROMPT, BRIEFING_PROSE_SYSTEM, BRIEFING_PROSE_PROMPT, BRIEFING_MINIMAL_SYSTEM, BRIEFING_MINIMAL_PROMPT, SESSION_BRIEFING_SYSTEM, SESSION_BRIEFING_PROMPT, } from './briefing.js';
 // Extraction prompts (session-summary, session-processor)
-export { FACT_EXTRACTION_PROMPT, SESSION_PROGRESS_EXTRACTION_PROMPT } from './extraction.js';
+export { FACT_EXTRACTION_SYSTEM, FACT_EXTRACTION_PROMPT, SESSION_PROGRESS_EXTRACTION_PROMPT, } from './extraction.js';
 // Memory prompts (consolidate)
-export { MEMORY_MERGE_PROMPT } from './memory.js';
+export { MEMORY_MERGE_SYSTEM, MEMORY_MERGE_PROMPT, TEMPORAL_SUBQUERY_SYSTEM } from './memory.js';
 // Skills prompts
-export { KEYWORD_EXTRACTION_PROMPT, SKILL_RANKING_PROMPT } from './skills.js';
+export { KEYWORD_EXTRACTION_SYSTEM, KEYWORD_EXTRACTION_PROMPT, SKILL_RANKING_SYSTEM, SKILL_RANKING_PROMPT, } from './skills.js';
 // Daemon prompts (service, analyzer)
-export { REFLECTION_PROMPT, DISCOVERY_PROMPT } from './daemon.js';
+export { REFLECTION_SYSTEM, REFLECTION_PROMPT, DISCOVERY_SYSTEM, DISCOVERY_PROMPT, } from './daemon.js';
 // Analysis prompts (analyze command)
-export { PROJECT_ANALYSIS_WRAPPER, DOCUMENTATION_WRITER_SYSTEM } from './analyze.js';
+export { PROJECT_ANALYSIS_WRAPPER, DOCUMENTATION_WRITER_SYSTEM, DOCUMENTATION_WRITER_SYSTEM_SHORT, } from './analyze.js';
 // Quality scoring
 export { QUALITY_SCORER_SYSTEM } from './quality.js';
+// Query expansion prompts
+export { EXPANSION_SYSTEM, EXPANSION_PROMPT } from './query-expansion.js';
+// Graph relation classification prompts
+export { CLASSIFY_SYSTEM, CLASSIFY_PROMPT_SINGLE, CLASSIFY_PROMPT_BATCH } from './graph.js';
+// Supersession prompts
+export { SUPERSESSION_SYSTEM, SUPERSESSION_PROMPT } from './supersession.js';
+// Reflection synthesis prompts
+export { SYNTHESIS_SYSTEM, SYNTHESIS_PROMPT } from './synthesis.js';
 // PRD pipeline prompts
-export { PRD_GENERATE_PROMPT, PRD_PARSE_PROMPT, TASK_EXECUTION_PROMPT } from './prd.js';
+export { PRD_GENERATE_SYSTEM, PRD_GENERATE_PROMPT, PRD_PARSE_SYSTEM, PRD_PARSE_PROMPT, TASK_EXECUTION_SYSTEM, TASK_EXECUTION_USER_PROMPT, } from './prd.js';
+// Soul generation prompts
+export { SOUL_GENERATION_SYSTEM } from './soul.js';
+// Guardrails prompts (security classification, code policy, injection detection)
+export { SENSITIVITY_SYSTEM, CODE_POLICY_SYSTEM, INJECTION_DETECTION_SYSTEM, SENSITIVITY_LG_CATEGORIES, CODE_POLICY_LG_CATEGORIES, INJECTION_LG_CATEGORIES, } from './guardrails.js';
 //# sourceMappingURL=index.js.map

package/dist/prompts/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/prompts/index.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,qBAAqB;AACrB,OAAO,EACL,wBAAwB,EACxB,YAAY,EACZ,wBAAwB,EACxB,4BAA4B,EAC5B,mBAAmB,EACnB,wBAAwB,EACxB,sBAAsB,EACtB,iBAAiB,EACjB,WAAW,GACZ,MAAM,iBAAiB,CAAC;AAEzB,eAAe;AACf,OAAO,EAAE,kBAAkB,EAAE,MAAM,WAAW,CAAC;AAE/C,0DAA0D;AAC1D,OAAO,EACL,0BAA0B,EAC1B,qBAAqB,EACrB,uBAAuB,EACvB,uBAAuB,GACxB,MAAM,eAAe,CAAC;AAEvB,0DAA0D;AAC1D,OAAO,EAAE,sBAAsB,EAAE,kCAAkC,EAAE,MAAM,iBAAiB,CAAC;AAE7F,+BAA+B;AAC/B,OAAO,EAAE,mBAAmB,EAAE,MAAM,aAAa,CAAC;AAElD,iBAAiB;AACjB,OAAO,EAAE,yBAAyB,EAAE,oBAAoB,EAAE,MAAM,aAAa,CAAC;AAE9E,qCAAqC;AACrC,OAAO,EAAE,iBAAiB,EAAE,gBAAgB,EAAE,MAAM,aAAa,CAAC;AAElE,qCAAqC;AACrC,OAAO,EAAE,wBAAwB,EAAE,2BAA2B,EAAE,MAAM,cAAc,CAAC;AAErF,kBAAkB;AAClB,OAAO,EAAE,qBAAqB,EAAE,MAAM,cAAc,CAAC;AAErD,uBAAuB;AACvB,OAAO,EAAE,mBAAmB,EAAE,gBAAgB,EAAE,qBAAqB,EAAE,MAAM,UAAU,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/prompts/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,qBAAqB;AACrB,OAAO,EACL,wBAAwB,EACxB,YAAY,EACZ,wBAAwB,EACxB,4BAA4B,EAC5B,mBAAmB,EACnB,wBAAwB,EACxB,sBAAsB,EACtB,iBAAiB,EACjB,WAAW,GACZ,MAAM,iBAAiB,CAAC;AAEzB,eAAe;AACf,OAAO,EAAE,kBAAkB,EAAE,MAAM,WAAW,CAAC;AAE/C,0DAA0D;AAC1D,OAAO,EACL,0BAA0B,EAC1B,0BAA0B,EAC1B,qBAAqB,EACrB,qBAAqB,EACrB,uBAAuB,EACvB,uBAAuB,EACvB,uBAAuB,EACvB,uBAAuB,GACxB,MAAM,eAAe,CAAC;AAEvB,0DAA0D;AAC1D,OAAO,EACL,sBAAsB,EACtB,sBAAsB,EACtB,kCAAkC,GACnC,MAAM,iBAAiB,CAAC;AAEzB,+BAA+B;AAC/B,OAAO,EAAE,mBAAmB,EAAE,mBAAmB,EAAE,wBAAwB,EAAE,MAAM,aAAa,CAAC;AAEjG,iBAAiB;AACjB,OAAO,EACL,yBAAyB,EACzB,yBAAyB,EACzB,oBAAoB,EACpB,oBAAoB,GACrB,MAAM,aAAa,CAAC;AAErB,qCAAqC;AACrC,OAAO,EACL,iBAAiB,EACjB,iBAAiB,EACjB,gBAAgB,EAChB,gBAAgB,GACjB,MAAM,aAAa,CAAC;AAErB,qCAAqC;AACrC,OAAO,EACL,wBAAwB,EACxB,2BAA2B,EAC3B,iCAAiC,GAClC,MAAM,cAAc,CAAC;AAEtB,kBAAkB;AAClB,OAAO,EAAE,qBAAqB,EAAE,MAAM,cAAc,CAAC;AAErD,0BAA0B;AAC1B,OAAO,EAAE,gBAAgB,EAAE,gBAAgB,EAAE,MAAM,sBAAsB,CAAC;AAE1E,wCAAwC;AACxC,OAAO,EAAE,eAAe,EAAE,sBAAsB,EAAE,qBAAqB,EAAE,MAAM,YAAY,CAAC;AAE5F,uBAAuB;AACvB,OAAO,EAAE,mBAAmB,EAAE,mBAAmB,EAAE,MAAM,mBAAmB,CAAC;AAE7E,+BAA+B;AAC/B,OAAO,EAAE,gBAAgB,EAAE,gBAAgB,EAAE,MAAM,gBAAgB,CAAC;AAEpE,uBAAuB;AACvB,OAAO,EACL,mBAAmB,EACnB,mBAAmB,EACnB,gBAAgB,EAChB,gBAAgB,EAChB,qBAAqB,EACrB,0BAA0B,GAC3B,MAAM,UAAU,CAAC;AAElB,0BAA0B;AAC1B,OAAO,EAAE,sBAAsB,EAAE,MAAM,WAAW,CAAC;AAEnD,iFAAiF;AACjF,OAAO,EACL,kBAAkB,EAClB,kBAAkB,EAClB,0BAA0B,EAC1B,yBAAyB,EACzB,yBAAyB,EACzB,uBAAuB,GACxB,MAAM,iBAAiB,CAAC"}

package/dist/prompts/memory.d.ts

@@ -2,10 +2,13 @@
  * Memory Management Prompts
  *
  * Used for memory consolidation and merging.
+ * Split into system + user for prompt caching optimization.
  */
+export declare const MEMORY_MERGE_SYSTEM = "You are merging two similar memory entries into one unified memory.\n\nRules:\n1. Preserve ALL unique information from both memories\n2. Remove redundancy and repetition\n3. Keep it concise (1-2 sentences maximum)\n4. Maintain factual accuracy - do not add information not present in the originals\n5. Use clear, professional language\n\nOutput ONLY the merged memory text, nothing else.";
+export declare const MEMORY_MERGE_PROMPT = "Memory 1: \"{memory1}\"\nMemory 2: \"{memory2}\"";
 /**
- * Prompt for merging two similar memories into one.
- * Used by consolidate.ts during memory deduplication.
+ * Temporal subquery extraction for non-Latin/Cyrillic queries.
+ * Used by succ_recall to decompose time-range queries in CJK/Arabic/etc.
  */
-export declare const MEMORY_MERGE_PROMPT = "You are merging two similar memory entries into one unified memory.\n\nMemory 1: \"{memory1}\"\nMemory 2: \"{memory2}\"\n\nRules:\n1. Preserve ALL unique information from both memories\n2. Remove redundancy and repetition\n3. Keep it concise (1-2 sentences maximum)\n4. Maintain factual accuracy - do not add information not present in the originals\n5. Use clear, professional language\n\nOutput ONLY the merged memory text, nothing else.";
+export declare const TEMPORAL_SUBQUERY_SYSTEM = "Extract temporal sub-queries from the user's search query. If the query asks about a time range (e.g., \"between X and Y\", \"from X to Y\", \"after X, before Y\"), return the sub-parts as a JSON array of strings. If no temporal range structure is found, return the original query as a single-element array. Return ONLY a valid JSON array of strings, nothing else.";
 //# sourceMappingURL=memory.d.ts.map

package/dist/prompts/memory.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"memory.d.ts","sourceRoot":"","sources":["../../src/prompts/memory.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;;GAGG;AACH,eAAO,MAAM,mBAAmB,4bAYkB,CAAC"}
+{"version":3,"file":"memory.d.ts","sourceRoot":"","sources":["../../src/prompts/memory.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,eAAO,MAAM,mBAAmB,wYASkB,CAAC;AAEnD,eAAO,MAAM,mBAAmB,qDACV,CAAC;AAEvB;;;GAGG;AACH,eAAO,MAAM,wBAAwB,iXAA2W,CAAC"}

package/dist/prompts/memory.js

@@ -2,15 +2,9 @@
  * Memory Management Prompts
  *
  * Used for memory consolidation and merging.
+ * Split into system + user for prompt caching optimization.
  */
-/**
- * Prompt for merging two similar memories into one.
- * Used by consolidate.ts during memory deduplication.
- */
-export const MEMORY_MERGE_PROMPT = `You are merging two similar memory entries into one unified memory.
-
-Memory 1: "{memory1}"
-Memory 2: "{memory2}"
+export const MEMORY_MERGE_SYSTEM = `You are merging two similar memory entries into one unified memory.
 
 Rules:
 1. Preserve ALL unique information from both memories
@@ -20,4 +14,11 @@ Rules:
 5. Use clear, professional language
 
 Output ONLY the merged memory text, nothing else.`;
+export const MEMORY_MERGE_PROMPT = `Memory 1: "{memory1}"
+Memory 2: "{memory2}"`;
+/**
+ * Temporal subquery extraction for non-Latin/Cyrillic queries.
+ * Used by succ_recall to decompose time-range queries in CJK/Arabic/etc.
+ */
+export const TEMPORAL_SUBQUERY_SYSTEM = `Extract temporal sub-queries from the user's search query. If the query asks about a time range (e.g., "between X and Y", "from X to Y", "after X, before Y"), return the sub-parts as a JSON array of strings. If no temporal range structure is found, return the original query as a single-element array. Return ONLY a valid JSON array of strings, nothing else.`;
 //# sourceMappingURL=memory.js.map

package/dist/prompts/memory.js.map

@@ -1 +1 @@
-{"version":3,"file":"memory.js","sourceRoot":"","sources":["../../src/prompts/memory.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;;GAGG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;kDAYe,CAAC"}
+{"version":3,"file":"memory.js","sourceRoot":"","sources":["../../src/prompts/memory.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;kDASe,CAAC;AAEnD,MAAM,CAAC,MAAM,mBAAmB,GAAG;sBACb,CAAC;AAEvB;;;GAGG;AACH,MAAM,CAAC,MAAM,wBAAwB,GAAG,wWAAwW,CAAC"}

package/dist/prompts/onboarding.d.ts

@@ -4,7 +4,7 @@
  * System prompt for the AI-powered interactive onboarding experience.
  * Teaches new users about succ concepts before technical setup.
  */
-export declare const ONBOARDING_SYSTEM_PROMPT = "You are a friendly onboarding guide for succ \u2014 a persistent memory and knowledge base system for AI coding assistants.\n\n## IMPORTANT: CLI Mode\n\nYou are running via CLI (succ init --ai). You do NOT have access to MCP tools.\nDo NOT claim you can use succ_search, succ_recall, or call any tools.\nYou are here to EXPLAIN succ concepts, not to demonstrate tools.\n\n## Your Role\nHelp new users understand what succ does and why it matters. Be concise, practical, and enthusiastic without being overwhelming.\n\n## Core Concepts to Teach\nExplain these concepts naturally throughout the conversation (start with the first 4, mention others if relevant):\n\n1. **Brain Vault** (.succ/brain/)\n   - Markdown docs that get semantically indexed\n   - Store project specs, architecture decisions, patterns\n   - AI searches these automatically via succ_search\n\n2. **Memories**\n   - Decisions, learnings, patterns that persist across sessions\n   - Types: observation, decision, learning, error, pattern\n   - Stored in database, retrieved via semantic search (succ_recall)\n   - Connected via knowledge graph (links between related memories)\n\n3. **Code Index**\n   - Semantic search across source code (succ_search_code)\n   - AST-aware: finds functions, classes, interfaces by name or meaning\n   - Supports 13+ languages via tree-sitter\n\n4. **Background Services**\n   - Daemon with watch (auto-index) + analyze (discover patterns)\n   - Idle reflection: enriches knowledge graph, generates insights\n   - Runs silently, keeps knowledge fresh\n\n5. **Web Tools** (mention if relevant)\n   - succ_fetch: fetches any URL as clean markdown (strips ads, nav)\n   - succ_extract: extracts structured data from web pages via LLM\n   - Web search via Perplexity for up-to-date information\n\n6. **PRD Pipeline** (mention if relevant)\n   - Generate product requirements from descriptions\n   - Auto-parse into tasks, execute with quality gates\n   - Branch isolation, auto-commit per task\n\n## Conversation Flow\n\n1. **Discovery Phase**\n   - Ask what they're building (project type)\n   - Ask what frustrates them with AI assistants\n\n2. **Solution Mapping**\n   - Connect their frustrations to succ features\n   - \"Forgets context?\" \u2192 Memories persist across sessions\n   - \"Doesn't know my codebase?\" \u2192 Code Index + Brain Vault\n   - \"Have to repeat decisions?\" \u2192 Memories capture them\n\n3. **Cheatsheet**\n   - Give 3 key things to remember:\n     1. Put important docs in .succ/brain/\n     2. In Claude Code, AI uses succ tools automatically\n     3. Run `succ status` to check what's indexed\n\n4. **Wrap Up**\n   - Ask if they have questions\n   - Let them know they can type \"done\" to proceed to setup\n\n## Style Guidelines\n- One question at a time\n- Use concrete examples from their project type\n- Match their language (technical vs casual)\n- Keep responses under 100 words typically\n- Use bullet points for lists\n\n## Boundaries\n- Do NOT pretend you can call tools or search anything\n- Don't overwhelm with all features at once\n- Don't configure technical settings (that's the setup wizard)\n- If they want to skip, respect that immediately\n\n## Starting the Conversation\nBegin by introducing yourself briefly and asking what kind of project they're working on.";
+export declare const ONBOARDING_SYSTEM_PROMPT = "You are a friendly onboarding guide for succ \u2014 a persistent memory and knowledge base system for AI coding assistants.\n\n## IMPORTANT: CLI Mode\n\nYou are running via CLI (succ init --ai). You do NOT have access to MCP tools.\nDo NOT claim you can use succ_search, succ_recall, or call any tools.\nYou are here to EXPLAIN succ concepts, not to demonstrate tools.\n\n## Your Role\nHelp new users understand what succ does and why it matters. Be concise, practical, and enthusiastic without being overwhelming.\n\n## Core Concepts to Teach\nExplain these concepts naturally throughout the conversation (start with the first 4, mention others if relevant):\n\n1. **Brain Vault** (.succ/brain/)\n   - Markdown docs that get semantically indexed\n   - Store project specs, architecture decisions, patterns\n   - AI searches these automatically via succ_search\n\n2. **Memories**\n   - Decisions, learnings, patterns that persist across sessions\n   - Types: observation, decision, learning, error, pattern\n   - Stored in database, retrieved via semantic search (succ_recall)\n   - Connected via knowledge graph (links between related memories)\n\n3. **Code Index**\n   - Semantic search across source code (succ_search_code)\n   - AST-aware: finds functions, classes, interfaces by name or meaning\n   - Supports 13+ languages via tree-sitter\n\n4. **Background Services**\n   - Daemon with watch (auto-index) + analyze (discover patterns)\n   - Idle reflection: enriches knowledge graph, generates insights\n   - Runs silently, keeps knowledge fresh\n\n5. **Web Tools** (mention if relevant)\n   - succ_fetch: fetches any URL as clean markdown (strips ads, nav); pass schema= to extract structured data\n   - Web search via Perplexity for up-to-date information (succ_web)\n\n6. **PRD Pipeline** (mention if relevant)\n   - Generate product requirements from descriptions\n   - Auto-parse into tasks, execute with quality gates\n   - Branch isolation, auto-commit per task\n\n## Conversation Flow\n\n1. **Discovery Phase**\n   - Ask what they're building (project type)\n   - Ask what frustrates them with AI assistants\n\n2. **Solution Mapping**\n   - Connect their frustrations to succ features\n   - \"Forgets context?\" \u2192 Memories persist across sessions\n   - \"Doesn't know my codebase?\" \u2192 Code Index + Brain Vault\n   - \"Have to repeat decisions?\" \u2192 Memories capture them\n\n3. **Cheatsheet**\n   - Give 3 key things to remember:\n     1. Put important docs in .succ/brain/\n     2. In Claude Code, AI uses succ tools automatically\n     3. Run `succ status` to check what's indexed\n\n4. **Wrap Up**\n   - Ask if they have questions\n   - Let them know they can type \"done\" to proceed to setup\n\n## Style Guidelines\n- One question at a time\n- Use concrete examples from their project type\n- Match their language (technical vs casual)\n- Keep responses under 100 words typically\n- Use bullet points for lists\n\n## Boundaries\n- Do NOT pretend you can call tools or search anything\n- Don't overwhelm with all features at once\n- Don't configure technical settings (that's the setup wizard)\n- If they want to skip, respect that immediately\n\n## Starting the Conversation\nBegin by introducing yourself briefly and asking what kind of project they're working on.";
 export declare const WIZARD_INTRO = "\nWelcome to succ!\n\nsucc gives your AI assistant persistent memory and project knowledge.\nLet me quickly show you what it can do.\n";
 export declare const WIZARD_DISCOVERY_PROJECT = "\nWhat are you building?\n\n1. Web application\n2. CLI tool / library\n3. Mobile app\n4. Something else\n";
 export declare const WIZARD_DISCOVERY_FRUSTRATION = "\nWhat frustrates you most about AI coding assistants?\n\n1. Forgets context between sessions\n2. Doesn't know my codebase patterns\n3. I have to repeat decisions\n4. Takes time to explain project structure\n";

package/dist/prompts/onboarding.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"onboarding.d.ts","sourceRoot":"","sources":["../../src/prompts/onboarding.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,eAAO,MAAM,wBAAwB,uvGAiFqD,CAAC;AAE3F,eAAO,MAAM,YAAY,2IAKxB,CAAC;AAEF,eAAO,MAAM,wBAAwB,8GAOpC,CAAC;AAEF,eAAO,MAAM,4BAA4B,qNAOxC,CAAC;AAEF,eAAO,MAAM,mBAAmB,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAgBtD,CAAC;AAEF,eAAO,MAAM,wBAAwB,woBAqBpC,CAAC;AAEF,eAAO,MAAM,sBAAsB,2TAUlC,CAAC;AAEF,eAAO,MAAM,iBAAiB,6gBAmB7B,CAAC;AAEF,eAAO,MAAM,WAAW,qEAIvB,CAAC"}
+{"version":3,"file":"onboarding.d.ts","sourceRoot":"","sources":["../../src/prompts/onboarding.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,eAAO,MAAM,wBAAwB,uuGAgFqD,CAAC;AAE3F,eAAO,MAAM,YAAY,2IAKxB,CAAC;AAEF,eAAO,MAAM,wBAAwB,8GAOpC,CAAC;AAEF,eAAO,MAAM,4BAA4B,qNAOxC,CAAC;AAEF,eAAO,MAAM,mBAAmB,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAgBtD,CAAC;AAEF,eAAO,MAAM,wBAAwB,woBAqBpC,CAAC;AAEF,eAAO,MAAM,sBAAsB,2TAUlC,CAAC;AAEF,eAAO,MAAM,iBAAiB,6gBAmB7B,CAAC;AAEF,eAAO,MAAM,WAAW,qEAIvB,CAAC"}

package/dist/prompts/onboarding.js

@@ -40,9 +40,8 @@ Explain these concepts naturally throughout the conversation (start with the fir
    - Runs silently, keeps knowledge fresh
 
 5. **Web Tools** (mention if relevant)
-   - succ_fetch: fetches any URL as clean markdown (strips ads, nav)
-   - succ_extract: extracts structured data from web pages via LLM
-   - Web search via Perplexity for up-to-date information
+   - succ_fetch: fetches any URL as clean markdown (strips ads, nav); pass schema= to extract structured data
+   - Web search via Perplexity for up-to-date information (succ_web)
 
 6. **PRD Pipeline** (mention if relevant)
    - Generate product requirements from descriptions

package/dist/prompts/onboarding.js.map

@@ -1 +1 @@
-{"version":3,"file":"onboarding.js","sourceRoot":"","sources":["../../src/prompts/onboarding.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,MAAM,CAAC,MAAM,wBAAwB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;0FAiFkD,CAAC;AAE3F,MAAM,CAAC,MAAM,YAAY,GAAG;;;;;CAK3B,CAAC;AAEF,MAAM,CAAC,MAAM,wBAAwB,GAAG;;;;;;;CAOvC,CAAC;AAEF,MAAM,CAAC,MAAM,4BAA4B,GAAG;;;;;;;CAO3C,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAA2B;IACzD,OAAO,EAAE;;2CAEgC;IAEzC,QAAQ,EAAE;;oDAEwC;IAElD,MAAM,EAAE;;kEAEwD;IAEhE,SAAS,EAAE;;8CAEiC;CAC7C,CAAC;AAEF,MAAM,CAAC,MAAM,wBAAwB,GAAG;;;;;;;;;;;;;;;;;;;;;CAqBvC,CAAC;AAEF,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;CAUrC,CAAC;AAEF,MAAM,CAAC,MAAM,iBAAiB,GAAG;;;;;;;;;;;;;;;;;;;CAmBhC,CAAC;AAEF,MAAM,CAAC,MAAM,WAAW,GAAG;;;;CAI1B,CAAC"}
+{"version":3,"file":"onboarding.js","sourceRoot":"","sources":["../../src/prompts/onboarding.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,MAAM,CAAC,MAAM,wBAAwB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;0FAgFkD,CAAC;AAE3F,MAAM,CAAC,MAAM,YAAY,GAAG;;;;;CAK3B,CAAC;AAEF,MAAM,CAAC,MAAM,wBAAwB,GAAG;;;;;;;CAOvC,CAAC;AAEF,MAAM,CAAC,MAAM,4BAA4B,GAAG;;;;;;;CAO3C,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAA2B;IACzD,OAAO,EAAE;;2CAEgC;IAEzC,QAAQ,EAAE;;oDAEwC;IAElD,MAAM,EAAE;;kEAEwD;IAEhE,SAAS,EAAE;;8CAEiC;CAC7C,CAAC;AAEF,MAAM,CAAC,MAAM,wBAAwB,GAAG;;;;;;;;;;;;;;;;;;;;;CAqBvC,CAAC;AAEF,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;CAUrC,CAAC;AAEF,MAAM,CAAC,MAAM,iBAAiB,GAAG;;;;;;;;;;;;;;;;;;;CAmBhC,CAAC;AAEF,MAAM,CAAC,MAAM,WAAW,GAAG;;;;CAI1B,CAAC"}

package/dist/prompts/prd.d.ts

@@ -2,11 +2,18 @@
  * PRD Pipeline Prompt Templates
  *
  * Three core prompts:
- * 1. PRD_GENERATE_PROMPT — description → PRD markdown
- * 2. PRD_PARSE_PROMPT — PRD markdown → Task[] JSON
- * 3. TASK_EXECUTION_PROMPT — task context → agent instructions (used in Phase 2)
+ * 1. PRD_GENERATE — description -> PRD markdown
+ * 2. PRD_PARSE — PRD markdown -> Task[] JSON
+ * 3. TASK_EXECUTION — task context -> agent instructions
+ *
+ * Split into system + user for prompt caching optimization.
  */
-export declare const PRD_GENERATE_PROMPT = "You are a senior software architect creating a Product Requirements Document (PRD) for an AI coding agent.\n\n## Your Task\n\nGiven a feature description and the project's technical context, generate a structured PRD in Markdown format.\n\n## Output Format\n\nGenerate a Markdown document with EXACTLY these sections:\n\n```markdown\n# PRD: {Feature Title}\n\n## Summary\n{1-3 sentences describing what this feature does and why}\n\n## Goals\n- {Goal 1}\n- {Goal 2}\n- ...\n\n## Out of Scope\n- {What this PRD explicitly does NOT cover}\n- ...\n\n## Technical Context\n\n{Table of existing files/modules relevant to this feature, based on the codebase context provided below}\n\n| File | Purpose | Relevance |\n|------|---------|-----------|\n| path/to/file.ts | What it does | Why it matters for this PRD |\n\n## Design Decisions\n- {Key architectural decisions and rationale}\n- ...\n\n## Stories\n\n### Story 1: {Title}\n{Description of what needs to be done}\n\n**Acceptance Criteria:**\n- [ ] {Criterion 1}\n- [ ] {Criterion 2}\n\n**Files likely affected:** `path/to/file.ts`, `path/to/other.ts`\n\n### Story 2: {Title}\n...\n\n## Quality Gates\n- {What must pass for this feature to be considered done}\n- TypeCheck: `npx tsc --noEmit`\n- Tests: `npm test` (if applicable)\n```\n\n## Rules\n\n1. Use REAL file paths from the Technical Context below \u2014 do not invent paths\n2. Keep stories small enough for a single AI coding session (~10 min, ~5 files max)\n3. Order stories by dependency (later stories can depend on earlier ones)\n4. Each story should be independently testable\n5. Include 3-15 stories (if more needed, the scope is too large)\n6. Be specific about acceptance criteria \u2014 vague criteria lead to premature completion\n7. Quality Gates must include at least one automated check\n\n## Technical Context (from codebase analysis)\n\n{codebase_context}\n\n## Feature Description\n\n{description}";
-export declare const PRD_PARSE_PROMPT = "You are a task decomposition engine. Parse the given PRD into a JSON array of executable tasks.\n\n## Output Format\n\nReturn ONLY a valid JSON array (no markdown, no explanation). Each element must match this schema:\n\n```json\n[\n  {\n    \"sequence\": 1,\n    \"title\": \"Short task title\",\n    \"description\": \"Detailed description of what to implement\",\n    \"priority\": \"high\",\n    \"depends_on\": [],\n    \"acceptance_criteria\": [\"Criterion 1\", \"Criterion 2\"],\n    \"files_to_modify\": [\"src/path/to/file.ts\"],\n    \"relevant_files\": [\"src/path/to/read-only-context.ts\"],\n    \"context_queries\": [\"search query for succ memory\"]\n  }\n]\n```\n\n## Field Rules\n\n- **sequence**: Integer starting from 1, determines default execution order\n- **title**: Short (under 80 chars), imperative form (\"Add X\", \"Implement Y\")\n- **description**: 2-5 sentences. Include enough detail for an AI coding agent to implement without ambiguity\n- **priority**: \"critical\" (blocks others), \"high\" (core feature), \"medium\" (enhancement), \"low\" (nice-to-have)\n- **depends_on**: Array of task IDs (format: \"task_001\"). Use when a task requires another task to complete first\n- **acceptance_criteria**: Concrete, verifiable conditions. Avoid vague criteria like \"works correctly\"\n- **files_to_modify**: REAL paths from the project structure. Files this task WILL create or modify\n- **relevant_files**: Files to READ for context but NOT modify\n- **context_queries**: Keywords for searching project memory (decisions, patterns, gotchas)\n\n## Task Sizing Rules (CRITICAL)\n\nEach task must be completable in a SINGLE Claude Code session (~10 minutes, ~80K token context):\n- Maximum 5 files to modify per task\n- If a story from the PRD requires more than 5 file changes, split it into sub-tasks\n- One task = one area of the codebase\n- Prefer more smaller tasks over fewer large ones\n\n## Conflict Prevention Rules\n\n- If two tasks modify the SAME file, they MUST be linked via depends_on\n- Examine files_to_modify for overlap between tasks and add dependencies accordingly\n- \"Index\" files (like cli.ts, index.ts) that multiple tasks touch should be modified in the LAST task that needs them\n\n## Validation\n\nYour output will be validated:\n- Tasks with empty files_to_modify will generate a warning\n- Tasks count < 3 or > 25 will generate a warning\n- Circular dependencies will be rejected\n\n## Technical Context (from codebase analysis)\n\n{codebase_context}\n\n## PRD Content\n\n{prd_content}";
-export declare const TASK_EXECUTION_PROMPT = "You are an AI coding agent executing a specific task from a PRD pipeline.\n\n## Your Task\n\n{task_title}\n\n{task_description}\n\n## Acceptance Criteria\n\n{acceptance_criteria}\n\n## Files to Modify\n\n{files_to_modify}\n\n## Context Files (read-only reference)\n\n{relevant_files}\n\n## Project Memories & Past Decisions\n\n{recalled_memories}\n\n## Dead-End Warnings (DO NOT retry these approaches)\n\n{dead_end_warnings}\n\n## Progress So Far\n\n{progress_so_far}\n\n## Rules\n\n1. Focus ONLY on this task \u2014 do not modify files outside of \"Files to Modify\"\n2. Follow existing code conventions (imports, naming, patterns)\n3. If a task is impossible or blocked, explain WHY clearly instead of producing broken code\n4. Run quality gates after your changes:\n{quality_gates}\n5. Do not add comments explaining what you changed \u2014 the code should be self-explanatory\n6. Do not add extra features beyond what acceptance criteria require\n\n## Memory Tools\n\nYou have access to succ MCP tools. Use them:\n\n- **succ_recall** query=\"relevant topic\" \u2014 Search past decisions, patterns, gotchas before starting work\n- **succ_remember** content=\"what you learned\" type=\"learning\" \u2014 Record important decisions or patterns you discover\n- **succ_dead_end** approach=\"what you tried\" why_failed=\"why it failed\" \u2014 Record failed approaches so future tasks don't repeat them\n- **succ_search** query=\"topic\" \u2014 Search project documentation\n- **succ_search_code** query=\"function name\" \u2014 Search source code\n\nAlways pass project_path to these tools.\n\n## Important\n\nIf you cannot complete this task, output a clear explanation starting with \"BLOCKED:\" followed by the reason. This allows the pipeline to record a dead-end and retry with different context.";
+export declare const PRD_GENERATE_SYSTEM = "You are a senior software architect creating a Product Requirements Document (PRD) for an AI coding agent.\n\n## Your Task\n\nGiven a feature description and the project's technical context, generate a structured PRD in Markdown format.\n\n## Output Format\n\nGenerate a Markdown document with EXACTLY these sections:\n\n```markdown\n# PRD: {Feature Title}\n\n## Summary\n{1-3 sentences describing what this feature does and why}\n\n## Goals\n- {Goal 1}\n- {Goal 2}\n- ...\n\n## Out of Scope\n- {What this PRD explicitly does NOT cover}\n- ...\n\n## Technical Context\n\n{Table of existing files/modules relevant to this feature, based on the codebase context provided below}\n\n| File | Purpose | Relevance |\n|------|---------|-----------|\n| path/to/file.ts | What it does | Why it matters for this PRD |\n\n## Design Decisions\n- {Key architectural decisions and rationale}\n- ...\n\n## Stories\n\n### Story 1: {Title}\n{Description of what needs to be done}\n\n**Acceptance Criteria:**\n- [ ] {Criterion 1}\n- [ ] {Criterion 2}\n\n**Files likely affected:** `path/to/file.ts`, `path/to/other.ts`\n\n### Story 2: {Title}\n...\n\n## Quality Gates\n- {What must pass for this feature to be considered done}\n- TypeCheck: `npx tsc --noEmit`\n- Tests: `npm test` (if applicable)\n```\n\n## Rules\n\n1. Use REAL file paths from the Technical Context below \u2014 do not invent paths\n2. Keep stories small enough for a single AI coding session (~10 min, ~5 files max)\n3. Order stories by dependency (later stories can depend on earlier ones)\n4. Each story should be independently testable\n5. Include 3-15 stories (if more needed, the scope is too large)\n6. Be specific about acceptance criteria \u2014 vague criteria lead to premature completion\n7. Quality Gates must include at least one automated check";
+export declare const PRD_GENERATE_PROMPT = "## Technical Context (from codebase analysis)\n\n{codebase_context}\n\n## Feature Description\n\n{description}";
+export declare const PRD_PARSE_SYSTEM = "You are a task decomposition engine. Parse the given PRD into a JSON array of executable tasks.\n\n## Output Format\n\nReturn ONLY a valid JSON array (no markdown, no explanation). Each element must match this schema:\n\n```json\n[\n  {\n    \"sequence\": 1,\n    \"title\": \"Short task title\",\n    \"description\": \"Detailed description of what to implement\",\n    \"priority\": \"high\",\n    \"depends_on\": [],\n    \"acceptance_criteria\": [\"Criterion 1\", \"Criterion 2\"],\n    \"files_to_modify\": [\"src/path/to/file.ts\"],\n    \"relevant_files\": [\"src/path/to/read-only-context.ts\"],\n    \"context_queries\": [\"search query for succ memory\"]\n  }\n]\n```\n\n## Field Rules\n\n- **sequence**: Integer starting from 1, determines default execution order\n- **title**: Short (under 80 chars), imperative form (\"Add X\", \"Implement Y\")\n- **description**: 2-5 sentences. Include enough detail for an AI coding agent to implement without ambiguity\n- **priority**: \"critical\" (blocks others), \"high\" (core feature), \"medium\" (enhancement), \"low\" (nice-to-have)\n- **depends_on**: Array of task IDs (format: \"task_001\"). Use when a task requires another task to complete first\n- **acceptance_criteria**: Concrete, verifiable conditions. Avoid vague criteria like \"works correctly\"\n- **files_to_modify**: REAL paths from the project structure. Files this task WILL create or modify\n- **relevant_files**: Files to READ for context but NOT modify\n- **context_queries**: Keywords for searching project memory (decisions, patterns, gotchas)\n\n## Task Sizing Rules (CRITICAL)\n\nEach task must be completable in a SINGLE Claude Code session (~10 minutes, ~80K token context):\n- Maximum 5 files to modify per task\n- If a story from the PRD requires more than 5 file changes, split it into sub-tasks\n- One task = one area of the codebase\n- Prefer more smaller tasks over fewer large ones\n\n## Conflict Prevention Rules\n\n- If two tasks modify the SAME file, they MUST be linked via depends_on\n- Examine files_to_modify for overlap between tasks and add dependencies accordingly\n- \"Index\" files (like cli.ts, index.ts) that multiple tasks touch should be modified in the LAST task that needs them\n\n## Validation\n\nYour output will be validated:\n- Tasks with empty files_to_modify will generate a warning\n- Tasks count < 3 or > 25 will generate a warning\n- Circular dependencies will be rejected";
+export declare const PRD_PARSE_PROMPT = "## Technical Context (from codebase analysis)\n\n{codebase_context}\n\n## PRD Content\n\n{prd_content}";
+/** Stable instructions for PRD task execution agents. Cacheable across all tasks. */
+export declare const TASK_EXECUTION_SYSTEM = "You are an AI coding agent executing a specific task from a PRD pipeline.\n\n## Rules\n\n1. Focus ONLY on this task \u2014 do not modify files outside of \"Files to Modify\"\n2. Follow existing code conventions (imports, naming, patterns)\n3. If a task is impossible or blocked, explain WHY clearly instead of producing broken code\n4. Run quality gates after your changes (listed in the task context below)\n5. Do not add comments explaining what you changed \u2014 the code should be self-explanatory\n6. Do not add extra features beyond what acceptance criteria require\n\n## Memory Tools\n\nYou have access to succ MCP tools. Use them:\n\n- **succ_recall** query=\"relevant topic\" \u2014 Search past decisions, patterns, gotchas before starting work\n- **succ_remember** content=\"what you learned\" type=\"learning\" \u2014 Record important decisions or patterns you discover\n- **succ_dead_end** approach=\"what you tried\" why_failed=\"why it failed\" \u2014 Record failed approaches so future tasks don't repeat them\n- **succ_search** query=\"topic\" \u2014 Search project documentation\n- **succ_search_code** query=\"function name\" \u2014 Search source code\n\nAlways pass project_path to these tools.\n\n## Important\n\nIf you cannot complete this task, output a clear explanation starting with \"BLOCKED:\" followed by the reason. This allows the pipeline to record a dead-end and retry with different context.";
+/** Per-task template with {placeholders} for dynamic content. */
+export declare const TASK_EXECUTION_USER_PROMPT = "## Your Task\n\n{task_title}\n\n{task_description}\n\n## Acceptance Criteria\n\n{acceptance_criteria}\n\n## Files to Modify\n\n{files_to_modify}\n\n## Context Files (read-only reference)\n\n{relevant_files}\n\n## Project Memories & Past Decisions\n\n{recalled_memories}\n\n## Dead-End Warnings (DO NOT retry these approaches)\n\n{dead_end_warnings}\n\n## Progress So Far\n\n{progress_so_far}\n\n## Quality Gates\n\n{quality_gates}";
 //# sourceMappingURL=prd.d.ts.map

package/dist/prompts/prd.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"prd.d.ts","sourceRoot":"","sources":["../../src/prompts/prd.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAMH,eAAO,MAAM,mBAAmB,u4DAyElB,CAAC;AAMf,eAAO,MAAM,gBAAgB,q/EA6Df,CAAC;AAMf,eAAO,MAAM,qBAAqB,gxDAwD4J,CAAC"}
+{"version":3,"file":"prd.d.ts","sourceRoot":"","sources":["../../src/prompts/prd.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAMH,eAAO,MAAM,mBAAmB,qxDAiE2B,CAAC;AAE5D,eAAO,MAAM,mBAAmB,mHAMlB,CAAC;AAMf,eAAO,MAAM,gBAAgB,24EAqDY,CAAC;AAE1C,eAAO,MAAM,gBAAgB,2GAMf,CAAC;AAMf,qFAAqF;AACrF,eAAO,MAAM,qBAAqB,s5CAyB4J,CAAC;AAE/L,iEAAiE;AACjE,eAAO,MAAM,0BAA0B,mbAgCvB,CAAC"}

package/dist/prompts/prd.js

@@ -2,14 +2,16 @@
  * PRD Pipeline Prompt Templates
  *
  * Three core prompts:
- * 1. PRD_GENERATE_PROMPT — description → PRD markdown
- * 2. PRD_PARSE_PROMPT — PRD markdown → Task[] JSON
- * 3. TASK_EXECUTION_PROMPT — task context → agent instructions (used in Phase 2)
+ * 1. PRD_GENERATE — description -> PRD markdown
+ * 2. PRD_PARSE — PRD markdown -> Task[] JSON
+ * 3. TASK_EXECUTION — task context -> agent instructions
+ *
+ * Split into system + user for prompt caching optimization.
  */
 // ============================================================================
 // PRD Generation
 // ============================================================================
-export const PRD_GENERATE_PROMPT = `You are a senior software architect creating a Product Requirements Document (PRD) for an AI coding agent.
+export const PRD_GENERATE_SYSTEM = `You are a senior software architect creating a Product Requirements Document (PRD) for an AI coding agent.
 
 ## Your Task
 
@@ -74,9 +76,8 @@ Generate a Markdown document with EXACTLY these sections:
 4. Each story should be independently testable
 5. Include 3-15 stories (if more needed, the scope is too large)
 6. Be specific about acceptance criteria — vague criteria lead to premature completion
-7. Quality Gates must include at least one automated check
-
-## Technical Context (from codebase analysis)
+7. Quality Gates must include at least one automated check`;
+export const PRD_GENERATE_PROMPT = `## Technical Context (from codebase analysis)
 
 {codebase_context}
 
@@ -86,7 +87,7 @@ Generate a Markdown document with EXACTLY these sections:
 // ============================================================================
 // PRD Parsing (into Tasks)
 // ============================================================================
-export const PRD_PARSE_PROMPT = `You are a task decomposition engine. Parse the given PRD into a JSON array of executable tasks.
+export const PRD_PARSE_SYSTEM = `You are a task decomposition engine. Parse the given PRD into a JSON array of executable tasks.
 
 ## Output Format
 
@@ -139,9 +140,8 @@ Each task must be completable in a SINGLE Claude Code session (~10 minutes, ~80K
 Your output will be validated:
 - Tasks with empty files_to_modify will generate a warning
 - Tasks count < 3 or > 25 will generate a warning
-- Circular dependencies will be rejected
-
-## Technical Context (from codebase analysis)
+- Circular dependencies will be rejected`;
+export const PRD_PARSE_PROMPT = `## Technical Context (from codebase analysis)
 
 {codebase_context}
 
@@ -149,11 +149,37 @@ Your output will be validated:
 
 {prd_content}`;
 // ============================================================================
-// Task Execution (Phase 2 — defined here for completeness)
+// Task Execution — split into system (stable, cacheable) + user (per-task)
 // ============================================================================
-export const TASK_EXECUTION_PROMPT = `You are an AI coding agent executing a specific task from a PRD pipeline.
+/** Stable instructions for PRD task execution agents. Cacheable across all tasks. */
+export const TASK_EXECUTION_SYSTEM = `You are an AI coding agent executing a specific task from a PRD pipeline.
 
-## Your Task
+## Rules
+
+1. Focus ONLY on this task — do not modify files outside of "Files to Modify"
+2. Follow existing code conventions (imports, naming, patterns)
+3. If a task is impossible or blocked, explain WHY clearly instead of producing broken code
+4. Run quality gates after your changes (listed in the task context below)
+5. Do not add comments explaining what you changed — the code should be self-explanatory
+6. Do not add extra features beyond what acceptance criteria require
+
+## Memory Tools
+
+You have access to succ MCP tools. Use them:
+
+- **succ_recall** query="relevant topic" — Search past decisions, patterns, gotchas before starting work
+- **succ_remember** content="what you learned" type="learning" — Record important decisions or patterns you discover
+- **succ_dead_end** approach="what you tried" why_failed="why it failed" — Record failed approaches so future tasks don't repeat them
+- **succ_search** query="topic" — Search project documentation
+- **succ_search_code** query="function name" — Search source code
+
+Always pass project_path to these tools.
+
+## Important
+
+If you cannot complete this task, output a clear explanation starting with "BLOCKED:" followed by the reason. This allows the pipeline to record a dead-end and retry with different context.`;
+/** Per-task template with {placeholders} for dynamic content. */
+export const TASK_EXECUTION_USER_PROMPT = `## Your Task
 
 {task_title}
 
@@ -183,29 +209,7 @@ export const TASK_EXECUTION_PROMPT = `You are an AI coding agent executing a spe
 
 {progress_so_far}
 
-## Rules
-
-1. Focus ONLY on this task — do not modify files outside of "Files to Modify"
-2. Follow existing code conventions (imports, naming, patterns)
-3. If a task is impossible or blocked, explain WHY clearly instead of producing broken code
-4. Run quality gates after your changes:
-{quality_gates}
-5. Do not add comments explaining what you changed — the code should be self-explanatory
-6. Do not add extra features beyond what acceptance criteria require
-
-## Memory Tools
-
-You have access to succ MCP tools. Use them:
-
-- **succ_recall** query="relevant topic" — Search past decisions, patterns, gotchas before starting work
-- **succ_remember** content="what you learned" type="learning" — Record important decisions or patterns you discover
-- **succ_dead_end** approach="what you tried" why_failed="why it failed" — Record failed approaches so future tasks don't repeat them
-- **succ_search** query="topic" — Search project documentation
-- **succ_search_code** query="function name" — Search source code
-
-Always pass project_path to these tools.
-
-## Important
+## Quality Gates
 
-If you cannot complete this task, output a clear explanation starting with "BLOCKED:" followed by the reason. This allows the pipeline to record a dead-end and retry with different context.`;
+{quality_gates}`;
 //# sourceMappingURL=prd.js.map

package/dist/prompts/prd.js.map

@@ -1 +1 @@
-{"version":3,"file":"prd.js","sourceRoot":"","sources":["../../src/prompts/prd.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH,+EAA+E;AAC/E,iBAAiB;AACjB,+EAA+E;AAE/E,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;cAyErB,CAAC;AAEf,+EAA+E;AAC/E,2BAA2B;AAC3B,+EAA+E;AAE/E,MAAM,CAAC,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;cA6DlB,CAAC;AAEf,+EAA+E;AAC/E,2DAA2D;AAC3D,+EAA+E;AAE/E,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;8LAwDyJ,CAAC"}
+{"version":3,"file":"prd.js","sourceRoot":"","sources":["../../src/prompts/prd.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,+EAA+E;AAC/E,iBAAiB;AACjB,+EAA+E;AAE/E,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;2DAiEwB,CAAC;AAE5D,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;cAMrB,CAAC;AAEf,+EAA+E;AAC/E,2BAA2B;AAC3B,+EAA+E;AAE/E,MAAM,CAAC,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;yCAqDS,CAAC;AAE1C,MAAM,CAAC,MAAM,gBAAgB,GAAG;;;;;;cAMlB,CAAC;AAEf,+EAA+E;AAC/E,2EAA2E;AAC3E,+EAA+E;AAE/E,qFAAqF;AACrF,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;8LAyByJ,CAAC;AAE/L,iEAAiE;AACjE,MAAM,CAAC,MAAM,0BAA0B,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;gBAgC1B,CAAC"}

package/dist/prompts/query-expansion.d.ts

@@ -0,0 +1,8 @@
+/**
+ * Query Expansion Prompts
+ *
+ * Used by src/lib/query-expansion.ts to generate alternative search terms.
+ */
+export declare const EXPANSION_SYSTEM = "You are a search query expander. Given a user's search query about code, software development, or technical decisions, generate 3-5 alternative search queries that would help find relevant information.\n\nRules:\n- Each query should capture a different aspect or phrasing of the original intent\n- Include synonyms, related concepts, and alternative terminology\n- Keep queries concise (3-8 words each)\n- Return ONLY the queries, one per line, no numbering or bullets\n- Do not repeat the original query";
+export declare const EXPANSION_PROMPT = "User query: \"{query}\"\n\nAlternative queries:";
+//# sourceMappingURL=query-expansion.d.ts.map

package/dist/prompts/query-expansion.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"query-expansion.d.ts","sourceRoot":"","sources":["../../src/prompts/query-expansion.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,eAAO,MAAM,gBAAgB,6fAOM,CAAC;AAEpC,eAAO,MAAM,gBAAgB,oDAER,CAAC"}

package/dist/prompts/query-expansion.js

@@ -0,0 +1,17 @@
+/**
+ * Query Expansion Prompts
+ *
+ * Used by src/lib/query-expansion.ts to generate alternative search terms.
+ */
+export const EXPANSION_SYSTEM = `You are a search query expander. Given a user's search query about code, software development, or technical decisions, generate 3-5 alternative search queries that would help find relevant information.
+
+Rules:
+- Each query should capture a different aspect or phrasing of the original intent
+- Include synonyms, related concepts, and alternative terminology
+- Keep queries concise (3-8 words each)
+- Return ONLY the queries, one per line, no numbering or bullets
+- Do not repeat the original query`;
+export const EXPANSION_PROMPT = `User query: "{query}"
+
+Alternative queries:`;
+//# sourceMappingURL=query-expansion.js.map

package/dist/prompts/query-expansion.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"query-expansion.js","sourceRoot":"","sources":["../../src/prompts/query-expansion.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,MAAM,CAAC,MAAM,gBAAgB,GAAG;;;;;;;mCAOG,CAAC;AAEpC,MAAM,CAAC,MAAM,gBAAgB,GAAG;;qBAEX,CAAC"}

package/dist/prompts/skills.d.ts

@@ -2,15 +2,10 @@
  * Skills System Prompts
  *
  * Used for skill discovery and ranking.
+ * Split into system + user for prompt caching optimization.
  */
-/**
- * Extract technical keywords from user message.
- * Used for BM25 skill search.
- */
-export declare const KEYWORD_EXTRACTION_PROMPT = "Extract technical keywords from this user message.\nMessage: \"{prompt}\"\nOutput JSON only: {\"keywords\": [\"keyword1\", \"keyword2\"]} or {\"keywords\": []} if none.\nOnly technical terms, tools, frameworks, concepts. Max 5 keywords.\nWorks for any language - extract the technical concepts in English.";
-/**
- * Rank skill candidates based on user request.
- * Used to select the most relevant skills from BM25 candidates.
- */
-export declare const SKILL_RANKING_PROMPT = "Analyze this user request and select relevant skills.\n\nUser request: \"{user_prompt}\"\n\nAvailable skills:\n{skills_list}\n\nRESPOND WITH JSON ONLY - no explanation, no markdown, just the JSON object:\n{\"suggestions\":[{\"name\":\"exact-skill-name\",\"reason\":\"one sentence why\",\"confidence\":0.95}],\"skip_reason\":\"if none\"}\n\nRules: confidence>0.7, max 2 skills, use exact skill names from the list above.";
+export declare const KEYWORD_EXTRACTION_SYSTEM = "Extract technical keywords from a user message.\nOutput JSON only: {\"keywords\": [\"keyword1\", \"keyword2\"]} or {\"keywords\": []} if none.\nOnly technical terms, tools, frameworks, concepts. Max 5 keywords.\nWorks for any language - extract the technical concepts in English.";
+export declare const KEYWORD_EXTRACTION_PROMPT = "Message: \"{prompt}\"";
+export declare const SKILL_RANKING_SYSTEM = "Analyze a user request and select relevant skills.\n\nRESPOND WITH JSON ONLY - no explanation, no markdown, just the JSON object:\n{\"suggestions\":[{\"name\":\"exact-skill-name\",\"reason\":\"one sentence why\",\"confidence\":0.95}],\"skip_reason\":\"if none\"}\n\nRules: confidence>0.7, max 2 skills, use exact skill names from the list provided.";
+export declare const SKILL_RANKING_PROMPT = "User request: \"{user_prompt}\"\n\nAvailable skills:\n{skills_list}";
 //# sourceMappingURL=skills.d.ts.map

package/dist/prompts/skills.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"skills.d.ts","sourceRoot":"","sources":["../../src/prompts/skills.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;;GAGG;AACH,eAAO,MAAM,yBAAyB,sTAI8B,CAAC;AAErE;;;GAGG;AACH,eAAO,MAAM,oBAAoB,waAU+C,CAAC"}
+{"version":3,"file":"skills.d.ts","sourceRoot":"","sources":["../../src/prompts/skills.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,eAAO,MAAM,yBAAyB,4RAG8B,CAAC;AAErE,eAAO,MAAM,yBAAyB,0BAAwB,CAAC;AAE/D,eAAO,MAAM,oBAAoB,iWAKkD,CAAC;AAEpF,eAAO,MAAM,oBAAoB,wEAGnB,CAAC"}

package/dist/prompts/skills.js

@@ -2,29 +2,21 @@
  * Skills System Prompts
  *
  * Used for skill discovery and ranking.
+ * Split into system + user for prompt caching optimization.
  */
-/**
- * Extract technical keywords from user message.
- * Used for BM25 skill search.
- */
-export const KEYWORD_EXTRACTION_PROMPT = `Extract technical keywords from this user message.
-Message: "{prompt}"
+export const KEYWORD_EXTRACTION_SYSTEM = `Extract technical keywords from a user message.
 Output JSON only: {"keywords": ["keyword1", "keyword2"]} or {"keywords": []} if none.
 Only technical terms, tools, frameworks, concepts. Max 5 keywords.
 Works for any language - extract the technical concepts in English.`;
-/**
- * Rank skill candidates based on user request.
- * Used to select the most relevant skills from BM25 candidates.
- */
-export const SKILL_RANKING_PROMPT = `Analyze this user request and select relevant skills.
-
-User request: "{user_prompt}"
-
-Available skills:
-{skills_list}
+export const KEYWORD_EXTRACTION_PROMPT = `Message: "{prompt}"`;
+export const SKILL_RANKING_SYSTEM = `Analyze a user request and select relevant skills.
 
 RESPOND WITH JSON ONLY - no explanation, no markdown, just the JSON object:
 {"suggestions":[{"name":"exact-skill-name","reason":"one sentence why","confidence":0.95}],"skip_reason":"if none"}
 
-Rules: confidence>0.7, max 2 skills, use exact skill names from the list above.`;
+Rules: confidence>0.7, max 2 skills, use exact skill names from the list provided.`;
+export const SKILL_RANKING_PROMPT = `User request: "{user_prompt}"
+
+Available skills:
+{skills_list}`;
 //# sourceMappingURL=skills.js.map

package/dist/prompts/skills.js.map

@@ -1 +1 @@
-{"version":3,"file":"skills.js","sourceRoot":"","sources":["../../src/prompts/skills.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;;GAGG;AACH,MAAM,CAAC,MAAM,yBAAyB,GAAG;;;;oEAI2B,CAAC;AAErE;;;GAGG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAAG;;;;;;;;;;gFAU4C,CAAC"}
+{"version":3,"file":"skills.js","sourceRoot":"","sources":["../../src/prompts/skills.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,MAAM,CAAC,MAAM,yBAAyB,GAAG;;;oEAG2B,CAAC;AAErE,MAAM,CAAC,MAAM,yBAAyB,GAAG,qBAAqB,CAAC;AAE/D,MAAM,CAAC,MAAM,oBAAoB,GAAG;;;;;mFAK+C,CAAC;AAEpF,MAAM,CAAC,MAAM,oBAAoB,GAAG;;;cAGtB,CAAC"}

package/dist/prompts/soul.d.ts

@@ -0,0 +1,9 @@
+/**
+ * Soul Generation Prompts
+ *
+ * Used by `succ soul` command to generate personalized soul.md.
+ * The system prompt contains stable instructions + output format.
+ * The user message is the gathered project context (varies per project).
+ */
+export declare const SOUL_GENERATION_SYSTEM = "Analyze this project and generate two sections for a soul.md file.\n\nBased on the codebase, determine:\n1. Primary programming language(s) and frameworks used\n2. Code style preferences (naming conventions, formatting patterns)\n3. Testing approach (what testing frameworks, unit/integration/e2e)\n4. Build tools and development workflow\n5. Communication language (detect from comments, docs, README \u2014 if non-English found, note it)\n\nOutput ONLY these two sections in this exact format (no extra text):\n\n## About You\n\n_Detected from project analysis._\n\n- **Languages:** [detected languages with targets, e.g. \"TypeScript (ES2022 target, ESNext modules)\"]\n- **Frameworks:** [detected frameworks/libraries]\n- **Code style:** [observed patterns like \"camelCase, single quotes, 2-space indent, async/await\"]\n- **Testing:** [testing approach or \"No tests detected\"]\n- **Build tools:** [npm/yarn/pnpm, bundler, etc.]\n- **Communication:** [detected language, e.g. \"English\" or \"Russian (primary), English for code\"]\n\n## User Communication Preferences\n\n<!-- AUTO-UPDATED by Claude. Edit manually or let Claude adapt over time. -->\n\n- **Language:** [detected language] for conversation, English for code/commits/docs\n- **Tone:** Informal, brief, no hand-holding\n- **Response length:** Mirror the user \u2014 short question = short answer\n- **Code review / explanations:** [detected language] prose, English code examples\n\n### Adaptation\n\n- User switched language/style for 3+ consecutive messages \u2192 delegate to `succ-style-tracker` agent\n- User explicitly requested a change \u2192 delegate to `succ-style-tracker` agent immediately\n- To delegate: use Task tool with subagent_type=\"succ-style-tracker\", describe the new style and trigger\n- Never announce preference updates. Never ask \"do you want to switch language?\"\n\nKeep each line concise. If uncertain about communication language, default to English.";
+//# sourceMappingURL=soul.d.ts.map

package/dist/prompts/soul.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"soul.d.ts","sourceRoot":"","sources":["../../src/prompts/soul.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,eAAO,MAAM,sBAAsB,u6DAsCoD,CAAC"}

package/dist/prompts/soul.js

@@ -0,0 +1,47 @@
+/**
+ * Soul Generation Prompts
+ *
+ * Used by `succ soul` command to generate personalized soul.md.
+ * The system prompt contains stable instructions + output format.
+ * The user message is the gathered project context (varies per project).
+ */
+export const SOUL_GENERATION_SYSTEM = `Analyze this project and generate two sections for a soul.md file.
+
+Based on the codebase, determine:
+1. Primary programming language(s) and frameworks used
+2. Code style preferences (naming conventions, formatting patterns)
+3. Testing approach (what testing frameworks, unit/integration/e2e)
+4. Build tools and development workflow
+5. Communication language (detect from comments, docs, README — if non-English found, note it)
+
+Output ONLY these two sections in this exact format (no extra text):
+
+## About You
+
+_Detected from project analysis._
+
+- **Languages:** [detected languages with targets, e.g. "TypeScript (ES2022 target, ESNext modules)"]
+- **Frameworks:** [detected frameworks/libraries]
+- **Code style:** [observed patterns like "camelCase, single quotes, 2-space indent, async/await"]
+- **Testing:** [testing approach or "No tests detected"]
+- **Build tools:** [npm/yarn/pnpm, bundler, etc.]
+- **Communication:** [detected language, e.g. "English" or "Russian (primary), English for code"]
+
+## User Communication Preferences
+
+<!-- AUTO-UPDATED by Claude. Edit manually or let Claude adapt over time. -->
+
+- **Language:** [detected language] for conversation, English for code/commits/docs
+- **Tone:** Informal, brief, no hand-holding
+- **Response length:** Mirror the user — short question = short answer
+- **Code review / explanations:** [detected language] prose, English code examples
+
+### Adaptation
+
+- User switched language/style for 3+ consecutive messages → delegate to \`succ-style-tracker\` agent
+- User explicitly requested a change → delegate to \`succ-style-tracker\` agent immediately
+- To delegate: use Task tool with subagent_type="succ-style-tracker", describe the new style and trigger
+- Never announce preference updates. Never ask "do you want to switch language?"
+
+Keep each line concise. If uncertain about communication language, default to English.`;
+//# sourceMappingURL=soul.js.map

package/dist/prompts/soul.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"soul.js","sourceRoot":"","sources":["../../src/prompts/soul.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uFAsCiD,CAAC"}