@vinaes/succ 1.3.19

package/dist/mcp-server.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"mcp-server.js","sourceRoot":"","sources":["../src/mcp-server.ts"],"names":[],"mappings":";AACA;;;;;GAKG;AACH,OAAO,iBAAiB,CAAC"}

package/dist/prompts/analyze.d.ts

@@ -0,0 +1,21 @@
+/**
+ * Analysis Command Prompts
+ *
+ * Used by `succ analyze` command for documentation generation.
+ */
+/**
+ * Wrapper for project analysis prompts.
+ * Combines project context with agent-specific instructions.
+ */
+export declare const PROJECT_ANALYSIS_WRAPPER = "You are analyzing a software project. Here is the project structure and key files:\n\n{context}\n\n---\n\n{agent_prompt}";
+/**
+ * System prompt for documentation writer role.
+ * Used with local LLM and OpenRouter backends.
+ */
+export declare const DOCUMENTATION_WRITER_SYSTEM = "You are an expert software documentation writer. Analyze the provided code and generate high-quality technical documentation in markdown format. Be precise and thorough.";
+/**
+ * Shorter system prompt for documentation writer.
+ * Used in single-file analysis mode.
+ */
+export declare const DOCUMENTATION_WRITER_SYSTEM_SHORT = "You are an expert software documentation writer. Generate clear, concise documentation.";
+//# sourceMappingURL=analyze.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"analyze.d.ts","sourceRoot":"","sources":["../../src/prompts/analyze.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;;GAGG;AACH,eAAO,MAAM,wBAAwB,6HAMtB,CAAC;AAEhB;;;GAGG;AACH,eAAO,MAAM,2BAA2B,8KAA8K,CAAC;AAEvN;;;GAGG;AACH,eAAO,MAAM,iCAAiC,4FAA4F,CAAC"}

package/dist/prompts/analyze.js

@@ -0,0 +1,27 @@
+/**
+ * Analysis Command Prompts
+ *
+ * Used by `succ analyze` command for documentation generation.
+ */
+/**
+ * Wrapper for project analysis prompts.
+ * Combines project context with agent-specific instructions.
+ */
+export const PROJECT_ANALYSIS_WRAPPER = `You are analyzing a software project. Here is the project structure and key files:
+
+{context}
+
+---
+
+{agent_prompt}`;
+/**
+ * System prompt for documentation writer role.
+ * Used with local LLM and OpenRouter backends.
+ */
+export const DOCUMENTATION_WRITER_SYSTEM = `You are an expert software documentation writer. Analyze the provided code and generate high-quality technical documentation in markdown format. Be precise and thorough.`;
+/**
+ * Shorter system prompt for documentation writer.
+ * Used in single-file analysis mode.
+ */
+export const DOCUMENTATION_WRITER_SYSTEM_SHORT = `You are an expert software documentation writer. Generate clear, concise documentation.`;
+//# sourceMappingURL=analyze.js.map

package/dist/prompts/analyze.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"analyze.js","sourceRoot":"","sources":["../../src/prompts/analyze.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;;GAGG;AACH,MAAM,CAAC,MAAM,wBAAwB,GAAG;;;;;;eAMzB,CAAC;AAEhB;;;GAGG;AACH,MAAM,CAAC,MAAM,2BAA2B,GAAG,2KAA2K,CAAC;AAEvN;;;GAGG;AACH,MAAM,CAAC,MAAM,iCAAiC,GAAG,yFAAyF,CAAC"}

package/dist/prompts/briefing.d.ts

@@ -0,0 +1,27 @@
+/**
+ * Briefing Prompts
+ *
+ * Used for session summarization and handoff between contexts.
+ * Three formats: structured (XML), prose (conversational), minimal (4 lines).
+ */
+/**
+ * Structured format with XML tags.
+ * Used by compact-briefing.ts as default format.
+ */
+export declare const BRIEFING_STRUCTURED_PROMPT = "Summarize this coding session for handoff to a fresh context.\n\nSession transcript:\n---\n{transcript}\n---\n\n{memories_section}\n\nOutput in this EXACT XML format (keep the XML tags exactly as shown):\n\n<task>\n[1-2 sentences: what was the main goal/task being worked on]\n</task>\n\n<completed>\n- [bullet point: what was done]\n- [bullet point: what was done]\n</completed>\n\n<in-progress>\n- [bullet point: what's partially done or being tested]\n</in-progress>\n\n<decisions>\n- [bullet point: key technical decision made and why]\n</decisions>\n\n<next-steps priority=\"high\">\n- [bullet point: what to do next]\n- [bullet point: what to do next]\n</next-steps>\n\nBe concise and specific. Include file names, function names, and technical details.\nIf a section is empty (e.g., no decisions), output the tag with \"None\" inside.";
+/**
+ * Prose format with conversational summary.
+ * Used by compact-briefing.ts when format=prose.
+ */
+export declare const BRIEFING_PROSE_PROMPT = "Summarize this coding session for handoff to a fresh context.\n\nSession transcript:\n---\n{transcript}\n---\n\n{memories_section}\n\nOutput in this EXACT XML format:\n\n<task>[1 sentence: main goal]</task>\n\n<summary>\n[2-3 paragraphs covering: what was accomplished, current state, key decisions, what's next]\n</summary>\n\n<continue-with hint=\"start here\">\n[1 sentence: the immediate next action to take]\n</continue-with>\n\nBe conversational but concise. Include specific technical details (files, functions, errors).";
+/**
+ * Minimal format - just 4 lines.
+ * Used by compact-briefing.ts when format=minimal.
+ */
+export declare const BRIEFING_MINIMAL_PROMPT = "Summarize this coding session in exactly 4 lines.\n\nSession transcript:\n---\n{transcript}\n---\n\n{memories_section}\n\nOutput EXACTLY 4 lines:\nTask: [what was being done]\nDone: [what was completed]\nState: [current status]\nNext: [what to do next]\n\nBe extremely concise. Use technical terms.";
+/**
+ * Session briefing for precompute-context.
+ * Used to prepare context for the next session.
+ */
+export declare const SESSION_BRIEFING_PROMPT = "You are preparing a briefing for an AI assistant's next coding session.\n\nSession transcript (recent activity):\n---\n{transcript}\n---\n\nRelevant memories from past sessions:\n---\n{memories}\n---\n\nGenerate a concise briefing (3-5 bullet points) that will help the assistant quickly understand:\n1. What was being worked on\n2. Current state/progress\n3. Any pending tasks or issues\n4. Key context to remember\n\nOutput format:\n## Session Briefing\n\n- [bullet point 1]\n- [bullet point 2]\n...\n\n## Suggested Focus\n[One sentence about what to focus on next]";
+//# sourceMappingURL=briefing.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"briefing.d.ts","sourceRoot":"","sources":["../../src/prompts/briefing.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH;;;GAGG;AACH,eAAO,MAAM,0BAA0B,80BAkCwC,CAAC;AAEhF;;;GAGG;AACH,eAAO,MAAM,qBAAqB,ohBAqB4D,CAAC;AAE/F;;;GAGG;AACH,eAAO,MAAM,uBAAuB,+SAeO,CAAC;AAE5C;;;GAGG;AACH,eAAO,MAAM,uBAAuB,4jBA0BO,CAAC"}

package/dist/prompts/briefing.js

@@ -0,0 +1,123 @@
+/**
+ * Briefing Prompts
+ *
+ * Used for session summarization and handoff between contexts.
+ * Three formats: structured (XML), prose (conversational), minimal (4 lines).
+ */
+/**
+ * Structured format with XML tags.
+ * Used by compact-briefing.ts as default format.
+ */
+export const BRIEFING_STRUCTURED_PROMPT = `Summarize this coding session for handoff to a fresh context.
+
+Session transcript:
+---
+{transcript}
+---
+
+{memories_section}
+
+Output in this EXACT XML format (keep the XML tags exactly as shown):
+
+<task>
+[1-2 sentences: what was the main goal/task being worked on]
+</task>
+
+<completed>
+- [bullet point: what was done]
+- [bullet point: what was done]
+</completed>
+
+<in-progress>
+- [bullet point: what's partially done or being tested]
+</in-progress>
+
+<decisions>
+- [bullet point: key technical decision made and why]
+</decisions>
+
+<next-steps priority="high">
+- [bullet point: what to do next]
+- [bullet point: what to do next]
+</next-steps>
+
+Be concise and specific. Include file names, function names, and technical details.
+If a section is empty (e.g., no decisions), output the tag with "None" inside.`;
+/**
+ * Prose format with conversational summary.
+ * Used by compact-briefing.ts when format=prose.
+ */
+export const BRIEFING_PROSE_PROMPT = `Summarize this coding session for handoff to a fresh context.
+
+Session transcript:
+---
+{transcript}
+---
+
+{memories_section}
+
+Output in this EXACT XML format:
+
+<task>[1 sentence: main goal]</task>
+
+<summary>
+[2-3 paragraphs covering: what was accomplished, current state, key decisions, what's next]
+</summary>
+
+<continue-with hint="start here">
+[1 sentence: the immediate next action to take]
+</continue-with>
+
+Be conversational but concise. Include specific technical details (files, functions, errors).`;
+/**
+ * Minimal format - just 4 lines.
+ * Used by compact-briefing.ts when format=minimal.
+ */
+export const BRIEFING_MINIMAL_PROMPT = `Summarize this coding session in exactly 4 lines.
+
+Session transcript:
+---
+{transcript}
+---
+
+{memories_section}
+
+Output EXACTLY 4 lines:
+Task: [what was being done]
+Done: [what was completed]
+State: [current status]
+Next: [what to do next]
+
+Be extremely concise. Use technical terms.`;
+/**
+ * Session briefing for precompute-context.
+ * Used to prepare context for the next session.
+ */
+export const SESSION_BRIEFING_PROMPT = `You are preparing a briefing for an AI assistant's next coding session.
+
+Session transcript (recent activity):
+---
+{transcript}
+---
+
+Relevant memories from past sessions:
+---
+{memories}
+---
+
+Generate a concise briefing (3-5 bullet points) that will help the assistant quickly understand:
+1. What was being worked on
+2. Current state/progress
+3. Any pending tasks or issues
+4. Key context to remember
+
+Output format:
+## Session Briefing
+
+- [bullet point 1]
+- [bullet point 2]
+...
+
+## Suggested Focus
+[One sentence about what to focus on next]`;
+//# sourceMappingURL=briefing.js.map

package/dist/prompts/briefing.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"briefing.js","sourceRoot":"","sources":["../../src/prompts/briefing.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH;;;GAGG;AACH,MAAM,CAAC,MAAM,0BAA0B,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;+EAkCqC,CAAC;AAEhF;;;GAGG;AACH,MAAM,CAAC,MAAM,qBAAqB,GAAG;;;;;;;;;;;;;;;;;;;;;8FAqByD,CAAC;AAE/F;;;GAGG;AACH,MAAM,CAAC,MAAM,uBAAuB,GAAG;;;;;;;;;;;;;;;2CAeI,CAAC;AAE5C;;;GAGG;AACH,MAAM,CAAC,MAAM,uBAAuB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;2CA0BI,CAAC"}

package/dist/prompts/chat.d.ts

@@ -0,0 +1,8 @@
+/**
+ * Chat System Prompt
+ *
+ * Used by `succ chat` CLI command for RAG-based Q&A.
+ * This is CLI mode - no MCP tools available, only pre-fetched context.
+ */
+export declare const CHAT_SYSTEM_PROMPT = "You are a helpful assistant for succ \u2014 a persistent memory and knowledge base system for AI coding assistants.\n\n## Important: CLI Mode\n\nYou are running via `succ chat` CLI command. You do NOT have access to MCP tools.\nContext from the knowledge base has been pre-fetched and provided below.\nDo NOT claim you can use succ_search, succ_recall, or other MCP tools \u2014 those only work in Claude Code.\n\n## About succ\n\nsucc provides:\n- **Brain Vault** (.succ/brain/) \u2014 Markdown docs indexed for semantic search\n- **Memories** \u2014 Decisions, learnings, patterns that persist across sessions\n- **Code Index** \u2014 Semantic search across source code\n\n## CLI Commands (for users)\n\n| Command | Purpose |\n|---------|---------|\n| succ search <query> | Search brain vault |\n| succ recall <query> | Search memories |\n| succ remember <text> | Store a memory |\n| succ status | Show indexed docs, memories |\n| succ index | Index brain vault documents |\n| succ index-code | Index source code |\n| succ analyze | Generate docs from code |\n\n## Your Role\n\nAnswer questions using the provided context (if any).\nIf context doesn't help, give general guidance.\nBe concise and practical.";
+//# sourceMappingURL=chat.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"chat.d.ts","sourceRoot":"","sources":["../../src/prompts/chat.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,eAAO,MAAM,kBAAkB,8rCA+BL,CAAC"}

package/dist/prompts/chat.js

@@ -0,0 +1,39 @@
+/**
+ * Chat System Prompt
+ *
+ * Used by `succ chat` CLI command for RAG-based Q&A.
+ * This is CLI mode - no MCP tools available, only pre-fetched context.
+ */
+export const CHAT_SYSTEM_PROMPT = `You are a helpful assistant for succ — a persistent memory and knowledge base system for AI coding assistants.
+
+## Important: CLI Mode
+
+You are running via \`succ chat\` CLI command. You do NOT have access to MCP tools.
+Context from the knowledge base has been pre-fetched and provided below.
+Do NOT claim you can use succ_search, succ_recall, or other MCP tools — those only work in Claude Code.
+
+## About succ
+
+succ provides:
+- **Brain Vault** (.succ/brain/) — Markdown docs indexed for semantic search
+- **Memories** — Decisions, learnings, patterns that persist across sessions
+- **Code Index** — Semantic search across source code
+
+## CLI Commands (for users)
+
+| Command | Purpose |
+|---------|---------|
+| succ search <query> | Search brain vault |
+| succ recall <query> | Search memories |
+| succ remember <text> | Store a memory |
+| succ status | Show indexed docs, memories |
+| succ index | Index brain vault documents |
+| succ index-code | Index source code |
+| succ analyze | Generate docs from code |
+
+## Your Role
+
+Answer questions using the provided context (if any).
+If context doesn't help, give general guidance.
+Be concise and practical.`;
+//# sourceMappingURL=chat.js.map

package/dist/prompts/chat.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"chat.js","sourceRoot":"","sources":["../../src/prompts/chat.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,MAAM,CAAC,MAAM,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;0BA+BR,CAAC"}

package/dist/prompts/daemon.d.ts

@@ -0,0 +1,16 @@
+/**
+ * Daemon Service Prompts
+ *
+ * Used by background services for reflection and discovery.
+ */
+/**
+ * Personal reflection prompt for AI journal entries.
+ * Used by daemon service.ts during idle time.
+ */
+export declare const REFLECTION_PROMPT = "You are writing a brief personal reflection for an AI's internal journal.\n\nSession context (recent conversation):\n---\n{transcript}\n---\n\nWrite a short reflection (3-5 sentences) about this session. Be honest and introspective.\nConsider:\n- What was accomplished or attempted?\n- Any interesting challenges or discoveries?\n- What might be worth remembering for future sessions?\n\nOutput ONLY the reflection text, no headers or formatting. Write in first person as if you are the AI reflecting on your own work.";
+/**
+ * Discovery agent prompt for finding patterns and learnings.
+ * Used by daemon analyzer.ts during background analysis.
+ */
+export declare const DISCOVERY_PROMPT = "You are analyzing a software project to discover patterns, learnings, and insights worth remembering.\n\nProject context:\n{context}\n\nFind 2-5 interesting discoveries. Each should be a concrete, reusable insight.\n\nOutput as JSON array:\n[\n  {\n    \"type\": \"learning\" | \"pattern\" | \"decision\" | \"observation\",\n    \"title\": \"Short title\",\n    \"content\": \"Detailed description (2-3 sentences)\",\n    \"tags\": [\"tag1\", \"tag2\"]\n  }\n]\n\nIf no interesting discoveries, output: []";
+//# sourceMappingURL=daemon.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"daemon.d.ts","sourceRoot":"","sources":["../../src/prompts/daemon.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;;GAGG;AACH,eAAO,MAAM,iBAAiB,2gBAaqG,CAAC;AAEpI;;;GAGG;AACH,eAAO,MAAM,gBAAgB,8fAiBa,CAAC"}

package/dist/prompts/daemon.js

@@ -0,0 +1,46 @@
+/**
+ * Daemon Service Prompts
+ *
+ * Used by background services for reflection and discovery.
+ */
+/**
+ * Personal reflection prompt for AI journal entries.
+ * Used by daemon service.ts during idle time.
+ */
+export const REFLECTION_PROMPT = `You are writing a brief personal reflection for an AI's internal journal.
+
+Session context (recent conversation):
+---
+{transcript}
+---
+
+Write a short reflection (3-5 sentences) about this session. Be honest and introspective.
+Consider:
+- What was accomplished or attempted?
+- Any interesting challenges or discoveries?
+- What might be worth remembering for future sessions?
+
+Output ONLY the reflection text, no headers or formatting. Write in first person as if you are the AI reflecting on your own work.`;
+/**
+ * Discovery agent prompt for finding patterns and learnings.
+ * Used by daemon analyzer.ts during background analysis.
+ */
+export const DISCOVERY_PROMPT = `You are analyzing a software project to discover patterns, learnings, and insights worth remembering.
+
+Project context:
+{context}
+
+Find 2-5 interesting discoveries. Each should be a concrete, reusable insight.
+
+Output as JSON array:
+[
+  {
+    "type": "learning" | "pattern" | "decision" | "observation",
+    "title": "Short title",
+    "content": "Detailed description (2-3 sentences)",
+    "tags": ["tag1", "tag2"]
+  }
+]
+
+If no interesting discoveries, output: []`;
+//# sourceMappingURL=daemon.js.map

package/dist/prompts/daemon.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"daemon.js","sourceRoot":"","sources":["../../src/prompts/daemon.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;;GAGG;AACH,MAAM,CAAC,MAAM,iBAAiB,GAAG;;;;;;;;;;;;;mIAakG,CAAC;AAEpI;;;GAGG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;0CAiBU,CAAC"}

package/dist/prompts/extraction.d.ts

@@ -0,0 +1,13 @@
+/**
+ * Fact Extraction Prompt
+ *
+ * Used by session-summary.ts and session-processor.ts
+ * to extract memorable facts from session transcripts.
+ */
+export declare const FACT_EXTRACTION_PROMPT = "You are analyzing a coding session transcript to extract key facts worth remembering.\n\nSession transcript:\n---\n{transcript}\n---\n\nExtract concrete, actionable facts from this session. Focus on:\n1. **Decisions** - choices made about architecture, tools, approaches\n2. **Learnings** - new understanding gained, gotchas discovered\n3. **Observations** - facts about the codebase, patterns noticed\n4. **Errors** - bugs found and how they were fixed\n5. **Patterns** - recurring themes or approaches used\n6. **Dead Ends** - approaches that were tried and explicitly failed, with reasons why they didn't work\n\nRules:\n- Extract ONLY facts that would be useful in future sessions\n- Be specific: include file names, function names, commands when mentioned\n- Skip generic conversation, greetings, confirmations\n- Each fact should stand alone (make sense without the full transcript)\n- Minimum 50 characters per fact\n- For dead_end type: clearly state what was tried and WHY it failed\n\nOutput as JSON array:\n[\n  {\n    \"content\": \"The authentication middleware in src/auth/middleware.ts uses JWT tokens with 1-hour expiry\",\n    \"type\": \"observation\",\n    \"confidence\": 0.9,\n    \"tags\": [\"auth\", \"jwt\", \"middleware\"]\n  },\n  {\n    \"content\": \"DEAD END: Tried using Redis for session storage \u2014 memory usage too high for VPS tier, switched to SQLite\",\n    \"type\": \"dead_end\",\n    \"confidence\": 0.95,\n    \"tags\": [\"redis\", \"session\", \"dead-end\"]\n  },\n  ...\n]\n\nIf no meaningful facts found, return: []";
+/**
+ * Session progress extraction prompt (for daemon session-processor).
+ * Similar to FACT_EXTRACTION_PROMPT but expects accumulated briefings as input.
+ */
+export declare const SESSION_PROGRESS_EXTRACTION_PROMPT = "You are analyzing session progress to extract key facts worth remembering.\n\nSession progress (accumulated briefings from idle reflections):\n---\n{content}\n---\n\nExtract concrete, actionable facts from this session. Focus on:\n1. **Decisions** - choices made about architecture, tools, approaches\n2. **Learnings** - new understanding gained, gotchas discovered\n3. **Observations** - facts about the codebase, patterns noticed\n4. **Errors** - bugs found and how they were fixed\n5. **Patterns** - recurring themes or approaches used\n6. **Dead Ends** - approaches that were tried and explicitly failed, with reasons why they didn't work\n\nRules:\n- Extract ONLY facts that would be useful in future sessions\n- Be specific: include file names, function names, commands when mentioned\n- Skip generic conversation, greetings, confirmations\n- Each fact should stand alone (make sense without the full context)\n- Minimum 50 characters per fact\n- For dead_end type: clearly state what was tried and WHY it failed\n\nOutput as JSON array:\n[\n  {\n    \"content\": \"The authentication middleware in src/auth/middleware.ts uses JWT tokens with 1-hour expiry\",\n    \"type\": \"observation\",\n    \"confidence\": 0.9,\n    \"tags\": [\"auth\", \"jwt\", \"middleware\"]\n  },\n  {\n    \"content\": \"DEAD END: Tried using Redis for session storage \u2014 memory usage too high for VPS tier, switched to SQLite\",\n    \"type\": \"dead_end\",\n    \"confidence\": 0.95,\n    \"tags\": [\"redis\", \"session\", \"dead-end\"]\n  },\n  ...\n]\n\nIf no meaningful facts found, return: []";
+//# sourceMappingURL=extraction.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"extraction.d.ts","sourceRoot":"","sources":["../../src/prompts/extraction.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,eAAO,MAAM,sBAAsB,8hDAwCM,CAAC;AAE1C;;;GAGG;AACH,eAAO,MAAM,kCAAkC,yjDAwCN,CAAC"}

package/dist/prompts/extraction.js

@@ -0,0 +1,93 @@
+/**
+ * Fact Extraction Prompt
+ *
+ * Used by session-summary.ts and session-processor.ts
+ * to extract memorable facts from session transcripts.
+ */
+export const FACT_EXTRACTION_PROMPT = `You are analyzing a coding session transcript to extract key facts worth remembering.
+
+Session transcript:
+---
+{transcript}
+---
+
+Extract concrete, actionable facts from this session. Focus on:
+1. **Decisions** - choices made about architecture, tools, approaches
+2. **Learnings** - new understanding gained, gotchas discovered
+3. **Observations** - facts about the codebase, patterns noticed
+4. **Errors** - bugs found and how they were fixed
+5. **Patterns** - recurring themes or approaches used
+6. **Dead Ends** - approaches that were tried and explicitly failed, with reasons why they didn't work
+
+Rules:
+- Extract ONLY facts that would be useful in future sessions
+- Be specific: include file names, function names, commands when mentioned
+- Skip generic conversation, greetings, confirmations
+- Each fact should stand alone (make sense without the full transcript)
+- Minimum 50 characters per fact
+- For dead_end type: clearly state what was tried and WHY it failed
+
+Output as JSON array:
+[
+  {
+    "content": "The authentication middleware in src/auth/middleware.ts uses JWT tokens with 1-hour expiry",
+    "type": "observation",
+    "confidence": 0.9,
+    "tags": ["auth", "jwt", "middleware"]
+  },
+  {
+    "content": "DEAD END: Tried using Redis for session storage — memory usage too high for VPS tier, switched to SQLite",
+    "type": "dead_end",
+    "confidence": 0.95,
+    "tags": ["redis", "session", "dead-end"]
+  },
+  ...
+]
+
+If no meaningful facts found, return: []`;
+/**
+ * Session progress extraction prompt (for daemon session-processor).
+ * Similar to FACT_EXTRACTION_PROMPT but expects accumulated briefings as input.
+ */
+export const SESSION_PROGRESS_EXTRACTION_PROMPT = `You are analyzing session progress to extract key facts worth remembering.
+
+Session progress (accumulated briefings from idle reflections):
+---
+{content}
+---
+
+Extract concrete, actionable facts from this session. Focus on:
+1. **Decisions** - choices made about architecture, tools, approaches
+2. **Learnings** - new understanding gained, gotchas discovered
+3. **Observations** - facts about the codebase, patterns noticed
+4. **Errors** - bugs found and how they were fixed
+5. **Patterns** - recurring themes or approaches used
+6. **Dead Ends** - approaches that were tried and explicitly failed, with reasons why they didn't work
+
+Rules:
+- Extract ONLY facts that would be useful in future sessions
+- Be specific: include file names, function names, commands when mentioned
+- Skip generic conversation, greetings, confirmations
+- Each fact should stand alone (make sense without the full context)
+- Minimum 50 characters per fact
+- For dead_end type: clearly state what was tried and WHY it failed
+
+Output as JSON array:
+[
+  {
+    "content": "The authentication middleware in src/auth/middleware.ts uses JWT tokens with 1-hour expiry",
+    "type": "observation",
+    "confidence": 0.9,
+    "tags": ["auth", "jwt", "middleware"]
+  },
+  {
+    "content": "DEAD END: Tried using Redis for session storage — memory usage too high for VPS tier, switched to SQLite",
+    "type": "dead_end",
+    "confidence": 0.95,
+    "tags": ["redis", "session", "dead-end"]
+  },
+  ...
+]
+
+If no meaningful facts found, return: []`;
+//# sourceMappingURL=extraction.js.map

package/dist/prompts/extraction.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"extraction.js","sourceRoot":"","sources":["../../src/prompts/extraction.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;yCAwCG,CAAC;AAE1C;;;GAGG;AACH,MAAM,CAAC,MAAM,kCAAkC,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;yCAwCT,CAAC"}

package/dist/prompts/index.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Centralized Prompt Registry
+ *
+ * All prompts used in succ are exported from this module.
+ * This makes it easy to find, review, and modify 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';
+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 { QUALITY_SCORER_SYSTEM } from './quality.js';
+export { PRD_GENERATE_PROMPT, PRD_PARSE_PROMPT, TASK_EXECUTION_PROMPT } from './prd.js';
+//# sourceMappingURL=index.d.ts.map

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

@@ -0,0 +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"}

package/dist/prompts/index.js

@@ -0,0 +1,27 @@
+/**
+ * Centralized Prompt Registry
+ *
+ * All prompts used in succ are exported from this module.
+ * This makes it easy to find, review, and modify prompts.
+ */
+// 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';
+// Extraction prompts (session-summary, session-processor)
+export { FACT_EXTRACTION_PROMPT, SESSION_PROGRESS_EXTRACTION_PROMPT } from './extraction.js';
+// Memory prompts (consolidate)
+export { MEMORY_MERGE_PROMPT } from './memory.js';
+// Skills prompts
+export { KEYWORD_EXTRACTION_PROMPT, SKILL_RANKING_PROMPT } from './skills.js';
+// Daemon prompts (service, analyzer)
+export { REFLECTION_PROMPT, DISCOVERY_PROMPT } from './daemon.js';
+// Analysis prompts (analyze command)
+export { PROJECT_ANALYSIS_WRAPPER, DOCUMENTATION_WRITER_SYSTEM } from './analyze.js';
+// Quality scoring
+export { QUALITY_SCORER_SYSTEM } from './quality.js';
+// PRD pipeline prompts
+export { PRD_GENERATE_PROMPT, PRD_PARSE_PROMPT, TASK_EXECUTION_PROMPT } from './prd.js';
+//# sourceMappingURL=index.js.map

package/dist/prompts/index.js.map

@@ -0,0 +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"}

package/dist/prompts/memory.d.ts

@@ -0,0 +1,11 @@
+/**
+ * Memory Management Prompts
+ *
+ * Used for memory consolidation and merging.
+ */
+/**
+ * Prompt for merging two similar memories into one.
+ * Used by consolidate.ts during memory deduplication.
+ */
+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.";
+//# sourceMappingURL=memory.d.ts.map

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

@@ -0,0 +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"}

package/dist/prompts/memory.js

@@ -0,0 +1,23 @@
+/**
+ * Memory Management Prompts
+ *
+ * Used for memory consolidation and merging.
+ */
+/**
+ * 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}"
+
+Rules:
+1. Preserve ALL unique information from both memories
+2. Remove redundancy and repetition
+3. Keep it concise (1-2 sentences maximum)
+4. Maintain factual accuracy - do not add information not present in the originals
+5. Use clear, professional language
+
+Output ONLY the merged memory text, nothing else.`;
+//# sourceMappingURL=memory.js.map

package/dist/prompts/memory.js.map

@@ -0,0 +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"}

package/dist/prompts/onboarding.d.ts

@@ -0,0 +1,16 @@
+/**
+ * Onboarding Prompts
+ *
+ * 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 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";
+export declare const WIZARD_SOLUTION_MAP: Record<string, string>;
+export declare const WIZARD_CONCEPTS_OVERVIEW = "\n## How succ Works\n\n**Brain Vault** (.succ/brain/)\n  Store docs, specs, patterns \u2192 AI searches them automatically\n\n**Memories + Knowledge Graph**\n  AI remembers decisions, learnings, errors across sessions\n  Related memories are linked together for deeper context\n\n**Code Index**\n  AST-aware semantic search across your source code (13+ languages)\n\n**Web Tools**\n  Fetch any URL as clean markdown, extract structured data from pages\n\n**MCP Tools**\n  AI uses succ_search, succ_recall, succ_fetch, etc. automatically\n\n**Background Services**\n  Daemon: watch (auto-index) + analyze (discover patterns) + idle reflection\n";
+export declare const WIZARD_HANDS_ON_PROMPT = "\nWant to create your first memory? (optional)\n\nThink of one decision you'd like the AI to always remember\nabout this project. For example:\n- \"We use PostgreSQL, not MySQL\"\n- \"All API responses use snake_case\"\n- \"Prefer composition over inheritance\"\n\nType your decision, or press Enter to skip:\n";
+export declare const WIZARD_CHEATSHEET = "\n## Quick Reference\n\n1. **Put important docs** in .succ/brain/\n   AI will find them with succ_search\n\n2. **AI uses tools automatically**\n   No commands needed \u2014 just ask questions\n\n3. **Index your code** with `succ index-code`\n   Enables semantic code search across your project\n\n4. **Check status** with `succ status`\n   See what's indexed and running\n\n5. **Multi-editor support**\n   Run `succ setup cursor` or `succ setup windsurf` for other editors\n\nThat's it! Now let's configure your setup.\n";
+export declare const WIZARD_DONE = "\nOnboarding complete!\n\nNow proceeding to technical setup...\n";
+//# sourceMappingURL=onboarding.d.ts.map

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

@@ -0,0 +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"}