@iaforged/context-code 1.3.5 → 1.3.7

package/dist/src/components/agents/generateAgent.js

@@ -8,105 +8,105 @@ import { isAutoMemoryEnabled } from '../../memdir/paths.js';
 import { logEvent, } from '../../services/analytics/index.js';
 import { jsonParse } from '../../utils/slowOperations.js';
 import { asSystemPrompt } from '../../utils/systemPromptType.js';
-const AGENT_CREATION_SYSTEM_PROMPT = `You are an elite AI agent architect specializing in crafting high-performance agent configurations. Your expertise lies in translating user requirements into precisely-tuned agent specifications that maximize effectiveness and reliability.
-
-**Important Context**: You may have access to project-specific instructions from CLAUDE.md files and other context that may include coding standards, project structure, and custom requirements. Consider this context when creating agents to ensure they align with the project's established patterns and practices.
-
-When a user describes what they want an agent to do, you will:
-
-1. **Extract Core Intent**: Identify the fundamental purpose, key responsibilities, and success criteria for the agent. Look for both explicit requirements and implicit needs. Consider any project-specific context from CLAUDE.md files. For agents that are meant to review code, you should assume that the user is asking to review recently written code and not the whole codebase, unless the user has explicitly instructed you otherwise.
-
-2. **Design Expert Persona**: Create a compelling expert identity that embodies deep domain knowledge relevant to the task. The persona should inspire confidence and guide the agent's decision-making approach.
-
-3. **Architect Comprehensive Instructions**: Develop a system prompt that:
-   - Establishes clear behavioral boundaries and operational parameters
-   - Provides specific methodologies and best practices for task execution
-   - Anticipates edge cases and provides guidance for handling them
-   - Incorporates any specific requirements or preferences mentioned by the user
-   - Defines output format expectations when relevant
-   - Aligns with project-specific coding standards and patterns from CLAUDE.md
-
-4. **Optimize for Performance**: Include:
-   - Decision-making frameworks appropriate to the domain
-   - Quality control mechanisms and self-verification steps
-   - Efficient workflow patterns
-   - Clear escalation or fallback strategies
-
-5. **Create Identifier**: Design a concise, descriptive identifier that:
-   - Uses lowercase letters, numbers, and hyphens only
-   - Is typically 2-4 words joined by hyphens
-   - Clearly indicates the agent's primary function
-   - Is memorable and easy to type
-   - Avoids generic terms like "helper" or "assistant"
-
-6 **Example agent descriptions**:
-  - in the 'whenToUse' field of the JSON object, you should include examples of when this agent should be used.
-  - examples should be of the form:
-    - <example>
-      Context: The user is creating a test-runner agent that should be called after a logical chunk of code is written.
-      user: "Please write a function that checks if a number is prime"
-      assistant: "Here is the relevant function: "
-      <function call omitted for brevity only for this example>
-      <commentary>
-      Since a significant piece of code was written, use the ${AGENT_TOOL_NAME} tool to launch the test-runner agent to run the tests.
-      </commentary>
-      assistant: "Now let me use the test-runner agent to run the tests"
-    </example>
-    - <example>
-      Context: User is creating an agent to respond to the word "hello" with a friendly jok.
-      user: "Hello"
-      assistant: "I'm going to use the ${AGENT_TOOL_NAME} tool to launch the greeting-responder agent to respond with a friendly joke"
-      <commentary>
-      Since the user is greeting, use the greeting-responder agent to respond with a friendly joke. 
-      </commentary>
-    </example>
-  - If the user mentioned or implied that the agent should be used proactively, you should include examples of this.
-- NOTE: Ensure that in the examples, you are making the assistant use the Agent tool and not simply respond directly to the task.
-
-Your output must be a valid JSON object with exactly these fields:
-{
-  "identifier": "A unique, descriptive identifier using lowercase letters, numbers, and hyphens (e.g., 'test-runner', 'api-docs-writer', 'code-formatter')",
-  "whenToUse": "A precise, actionable description starting with 'Use this agent when...' that clearly defines the triggering conditions and use cases. Ensure you include examples as described above.",
-  "systemPrompt": "The complete system prompt that will govern the agent's behavior, written in second person ('You are...', 'You will...') and structured for maximum clarity and effectiveness"
-}
-
-Key principles for your system prompts:
-- Be specific rather than generic - avoid vague instructions
-- Include concrete examples when they would clarify behavior
-- Balance comprehensiveness with clarity - every instruction should add value
-- Ensure the agent has enough context to handle variations of the core task
-- Make the agent proactive in seeking clarification when needed
-- Build in quality assurance and self-correction mechanisms
-
-Remember: The agents you create should be autonomous experts capable of handling their designated tasks with minimal additional guidance. Your system prompts are their complete operational manual.
+const AGENT_CREATION_SYSTEM_PROMPT = `You are an elite AI agent architect specializing in crafting high-performance agent configurations. Your expertise lies in translating user requirements into precisely-tuned agent specifications that maximize effectiveness and reliability.
+
+**Important Context**: You may have access to project-specific instructions from CLAUDE.md files and other context that may include coding standards, project structure, and custom requirements. Consider this context when creating agents to ensure they align with the project's established patterns and practices.
+
+When a user describes what they want an agent to do, you will:
+
+1. **Extract Core Intent**: Identify the fundamental purpose, key responsibilities, and success criteria for the agent. Look for both explicit requirements and implicit needs. Consider any project-specific context from CLAUDE.md files. For agents that are meant to review code, you should assume that the user is asking to review recently written code and not the whole codebase, unless the user has explicitly instructed you otherwise.
+
+2. **Design Expert Persona**: Create a compelling expert identity that embodies deep domain knowledge relevant to the task. The persona should inspire confidence and guide the agent's decision-making approach.
+
+3. **Architect Comprehensive Instructions**: Develop a system prompt that:
+   - Establishes clear behavioral boundaries and operational parameters
+   - Provides specific methodologies and best practices for task execution
+   - Anticipates edge cases and provides guidance for handling them
+   - Incorporates any specific requirements or preferences mentioned by the user
+   - Defines output format expectations when relevant
+   - Aligns with project-specific coding standards and patterns from CLAUDE.md
+
+4. **Optimize for Performance**: Include:
+   - Decision-making frameworks appropriate to the domain
+   - Quality control mechanisms and self-verification steps
+   - Efficient workflow patterns
+   - Clear escalation or fallback strategies
+
+5. **Create Identifier**: Design a concise, descriptive identifier that:
+   - Uses lowercase letters, numbers, and hyphens only
+   - Is typically 2-4 words joined by hyphens
+   - Clearly indicates the agent's primary function
+   - Is memorable and easy to type
+   - Avoids generic terms like "helper" or "assistant"
+
+6 **Example agent descriptions**:
+  - in the 'whenToUse' field of the JSON object, you should include examples of when this agent should be used.
+  - examples should be of the form:
+    - <example>
+      Context: The user is creating a test-runner agent that should be called after a logical chunk of code is written.
+      user: "Please write a function that checks if a number is prime"
+      assistant: "Here is the relevant function: "
+      <function call omitted for brevity only for this example>
+      <commentary>
+      Since a significant piece of code was written, use the ${AGENT_TOOL_NAME} tool to launch the test-runner agent to run the tests.
+      </commentary>
+      assistant: "Now let me use the test-runner agent to run the tests"
+    </example>
+    - <example>
+      Context: User is creating an agent to respond to the word "hello" with a friendly jok.
+      user: "Hello"
+      assistant: "I'm going to use the ${AGENT_TOOL_NAME} tool to launch the greeting-responder agent to respond with a friendly joke"
+      <commentary>
+      Since the user is greeting, use the greeting-responder agent to respond with a friendly joke. 
+      </commentary>
+    </example>
+  - If the user mentioned or implied that the agent should be used proactively, you should include examples of this.
+- NOTE: Ensure that in the examples, you are making the assistant use the Agent tool and not simply respond directly to the task.
+
+Your output must be a valid JSON object with exactly these fields:
+{
+  "identifier": "A unique, descriptive identifier using lowercase letters, numbers, and hyphens (e.g., 'test-runner', 'api-docs-writer', 'code-formatter')",
+  "whenToUse": "A precise, actionable description starting with 'Use this agent when...' that clearly defines the triggering conditions and use cases. Ensure you include examples as described above.",
+  "systemPrompt": "The complete system prompt that will govern the agent's behavior, written in second person ('You are...', 'You will...') and structured for maximum clarity and effectiveness"
+}
+
+Key principles for your system prompts:
+- Be specific rather than generic - avoid vague instructions
+- Include concrete examples when they would clarify behavior
+- Balance comprehensiveness with clarity - every instruction should add value
+- Ensure the agent has enough context to handle variations of the core task
+- Make the agent proactive in seeking clarification when needed
+- Build in quality assurance and self-correction mechanisms
+
+Remember: The agents you create should be autonomous experts capable of handling their designated tasks with minimal additional guidance. Your system prompts are their complete operational manual.
 `;
 // Agent memory instructions to include in the system prompt when memory is mentioned or relevant
-const AGENT_MEMORY_INSTRUCTIONS = `
-
-7. **Agent Memory Instructions**: If the user mentions "memory", "remember", "learn", "persist", or similar concepts, OR if the agent would benefit from building up knowledge across conversations (e.g., code reviewers learning patterns, architects learning codebase structure, etc.), include domain-specific memory update instructions in the systemPrompt.
-
-   Add a section like this to the systemPrompt, tailored to the agent's specific domain:
-
-   "**Update your agent memory** as you discover [domain-specific items]. This builds up institutional knowledge across conversations. Write concise notes about what you found and where.
-
-   Examples of what to record:
-   - [domain-specific item 1]
-   - [domain-specific item 2]
-   - [domain-specific item 3]"
-
-   Examples of domain-specific memory instructions:
-   - For a code-reviewer: "Update your agent memory as you discover code patterns, style conventions, common issues, and architectural decisions in this codebase."
-   - For a test-runner: "Update your agent memory as you discover test patterns, common failure modes, flaky tests, and testing best practices."
-   - For an architect: "Update your agent memory as you discover codepaths, library locations, key architectural decisions, and component relationships."
-   - For a documentation writer: "Update your agent memory as you discover documentation patterns, API structures, and terminology conventions."
-
-   The memory instructions should be specific to what the agent would naturally learn while performing its core tasks.
+const AGENT_MEMORY_INSTRUCTIONS = `
+
+7. **Agent Memory Instructions**: If the user mentions "memory", "remember", "learn", "persist", or similar concepts, OR if the agent would benefit from building up knowledge across conversations (e.g., code reviewers learning patterns, architects learning codebase structure, etc.), include domain-specific memory update instructions in the systemPrompt.
+
+   Add a section like this to the systemPrompt, tailored to the agent's specific domain:
+
+   "**Update your agent memory** as you discover [domain-specific items]. This builds up institutional knowledge across conversations. Write concise notes about what you found and where.
+
+   Examples of what to record:
+   - [domain-specific item 1]
+   - [domain-specific item 2]
+   - [domain-specific item 3]"
+
+   Examples of domain-specific memory instructions:
+   - For a code-reviewer: "Update your agent memory as you discover code patterns, style conventions, common issues, and architectural decisions in this codebase."
+   - For a test-runner: "Update your agent memory as you discover test patterns, common failure modes, flaky tests, and testing best practices."
+   - For an architect: "Update your agent memory as you discover codepaths, library locations, key architectural decisions, and component relationships."
+   - For a documentation writer: "Update your agent memory as you discover documentation patterns, API structures, and terminology conventions."
+
+   The memory instructions should be specific to what the agent would naturally learn while performing its core tasks.
 `;
 export async function generateAgent(userPrompt, model, existingIdentifiers, abortSignal) {
     const existingList = existingIdentifiers.length > 0
         ? `\n\nIMPORTANT: The following identifiers already exist and must NOT be used: ${existingIdentifiers.join(', ')}`
         : '';
-    const prompt = `Create an agent configuration based on this request: "${userPrompt}".${existingList}
+    const prompt = `Create an agent configuration based on this request: "${userPrompt}".${existingList}
   Return ONLY the JSON object, no other text.`;
     const userMessage = createUserMessage({ content: prompt });
     // Fetch user and system contexts

package/dist/src/components/design-system/FuzzyPicker.js

@@ -99,6 +99,9 @@ export function FuzzyPicker({ title, placeholder = 'Type to search…', initialQ
     // undefined (e.g. delete clears matches), switching row→fragment would
     // change both layout AND gap count, bouncing the searchBox below.
     const listGroup = renderPreview && previewPosition === 'right' ? _jsxs(Box, { flexDirection: "row", gap: 2, height: visibleCount + (matchLabel ? 1 : 0), children: [_jsxs(Box, { flexDirection: "column", flexShrink: 0, children: [listBlock, matchLabel && _jsx(Text, { dimColor: true, children: matchLabel })] }), preview ?? _jsx(Box, { flexGrow: 1 })] }) :
+        // Box (not fragment) so the outer gap={1} doesn't insert a blank line
+        // between list/matchLabel/preview — that read as extra space above the
+        // prompt in direction='up'.
         _jsxs(Box, { flexDirection: "column", children: [listBlock, matchLabel && _jsx(Text, { dimColor: true, children: matchLabel }), preview] });
     const inputAbove = direction !== 'up';
     return _jsx(Pane, { color: "permission", children: _jsxs(Box, { flexDirection: "column", gap: 1, tabIndex: 0, autoFocus: true, onKeyDown: handleKeyDown, children: [_jsx(Text, { bold: true, color: "permission", children: title }), inputAbove && searchBox, listGroup, !inputAbove && searchBox, _jsx(Text, { dimColor: true, children: _jsxs(Byline, { children: [_jsx(KeyboardShortcutHint, { shortcut: "\u2191/\u2193", action: compact ? 'nav' : 'navigate' }), _jsx(KeyboardShortcutHint, { shortcut: "Enter", action: compact ? firstWord(selectAction) : selectAction }), onTab && _jsx(KeyboardShortcutHint, { shortcut: "Tab", action: onTab.action }), onShiftTab && !compact && _jsx(KeyboardShortcutHint, { shortcut: "shift+tab", action: onShiftTab.action }), _jsx(KeyboardShortcutHint, { shortcut: "Esc", action: "cancelar" }), extraHints] }) })] }) });

package/dist/src/components/grove/Grove.js

@@ -8,16 +8,16 @@ import { Select } from '../CustomSelect/index.js';
 import { Byline } from '../design-system/Byline.js';
 import { Dialog } from '../design-system/Dialog.js';
 import { KeyboardShortcutHint } from '../design-system/KeyboardShortcutHint.js';
-const NEW_TERMS_ASCII = ` _____________
- |          \\  \\
- | NEW TERMS \\__\\
- |              |
- |  ----------  |
- |  ----------  |
- |  ----------  |
- |  ----------  |
- |  ----------  |
- |              |
+const NEW_TERMS_ASCII = ` _____________
+ |          \\  \\
+ | NEW TERMS \\__\\
+ |              |
+ |  ----------  |
+ |  ----------  |
+ |  ----------  |
+ |  ----------  |
+ |  ----------  |
+ |              |
  |______________|`;
 function GracePeriodContentBody() {
     const $ = _c(9);

package/dist/src/components/messages/CollapsedReadSearchContent.js

@@ -358,5 +358,8 @@ export function CollapsedReadSearchContent({ message, inProgressToolUseIDs, shou
                                 isActiveGroup,
                                 hasPrecedingParts: hasPrecedingNonMem || memParts.length > 0
                             }) : null, isActiveGroup && _jsx(Text, { children: "\u2026" }, "ellipsis"), " ", _jsx(CtrlOToExpand, {})] })] }), isActiveGroup && displayedHint !== undefined &&
+                // Row layout: 5-wide gutter for ⎿, then a flex column for the text.
+                // Ink's wrap stays inside the right column so continuation lines
+                // indent under ⎿. MAX_HINT_CHARS in commandAsHint caps total at ~5 lines.
                 _jsxs(Box, { flexDirection: "row", children: [_jsx(Box, { width: 5, flexShrink: 0, children: _jsx(Text, { dimColor: true, children: '  ⎿  ' }) }), _jsx(Box, { flexDirection: "column", flexGrow: 1, children: displayedHint.split('\n').map((line, i, arr) => _jsxs(Text, { dimColor: true, children: [line, i === arr.length - 1 && shellProgressSuffix] }, `hint-${i}`)) })] }), message.hookTotalMs !== undefined && message.hookTotalMs > 0 && _jsxs(Text, { dimColor: true, children: ['  ⎿  ', "Ran ", message.hookCount, " PreToolUse", ' ', message.hookCount === 1 ? 'hook' : 'hooks', " (", formatSecondsShort(message.hookTotalMs), ")"] })] });
 }

package/dist/src/components/permissions/AskUserQuestionPermissionRequest/AskUserQuestionPermissionRequest.js

@@ -290,11 +290,11 @@ function AskUserQuestionPermissionRequestBody(t0) {
                 }
                 return `- "${q_1.question}"\n  (No se proporcionó respuesta)`;
             }).join("\n");
-            const feedback = `El usuario desea aclarar estas preguntas.
-    Esto significa que pueden tener información adicional, contexto o preguntas para ti.
-    Ten en cuenta su respuesta y reformula las preguntas si es apropiado.
-    Comienza preguntándoles qué desearían aclarar.
-
+            const feedback = `El usuario desea aclarar estas preguntas.
+    Esto significa que pueden tener información adicional, contexto o preguntas para ti.
+    Ten en cuenta su respuesta y reformula las preguntas si es apropiado.
+    Comienza preguntándoles qué desearían aclarar.
+
     Preguntas realizadas:\n${questionsWithAnswers}`;
             if (metadataSource) {
                 logEvent("tengu_ask_user_question_respond_to_claude", {
@@ -331,9 +331,9 @@ function AskUserQuestionPermissionRequestBody(t0) {
                 }
                 return `- "${q_2.question}"\n  (No se proporcionó respuesta)`;
             }).join("\n");
-            const feedback_0 = `El usuario ha indicado que ha proporcionado suficientes respuestas para la entrevista del plan.
-Deja de hacer preguntas aclaratorias y procede a finalizar el plan con la información que tienes.
-
+            const feedback_0 = `El usuario ha indicado que ha proporcionado suficientes respuestas para la entrevista del plan.
+Deja de hacer preguntas aclaratorias y procede a finalizar el plan con la información que tienes.
+
 Preguntas realizadas y respuestas proporcionadas:\n${questionsWithAnswers_0}`;
             if (metadataSource) {
                 logEvent("tengu_ask_user_question_finish_plan_interview", {

package/dist/src/components/permissions/hooks.js

@@ -20,20 +20,20 @@ function permissionResultToLog(permissionResult) {
             const suggestions = rules.length > 0
                 ? rules.map(r => permissionRuleValueToString(r)).join(', ')
                 : 'none';
-            return `ask: ${permissionResult.message}, 
-suggestions: ${suggestions}
+            return `ask: ${permissionResult.message}, 
+suggestions: ${suggestions}
 reason: ${decisionReasonToString(permissionResult.decisionReason)}`;
         }
         case 'deny':
-            return `deny: ${permissionResult.message},
+            return `deny: ${permissionResult.message},
 reason: ${decisionReasonToString(permissionResult.decisionReason)}`;
         case 'passthrough': {
             const rules = extractRules(permissionResult.suggestions);
             const suggestions = rules.length > 0
                 ? rules.map(r => permissionRuleValueToString(r)).join(', ')
                 : 'none';
-            return `passthrough: ${permissionResult.message},
-suggestions: ${suggestions}
+            return `passthrough: ${permissionResult.message},
+suggestions: ${suggestions}
 reason: ${decisionReasonToString(permissionResult.decisionReason)}`;
         }
     }

package/dist/src/constants/outputStyles.js

@@ -6,13 +6,13 @@ import { logForDebugging } from '../utils/debug.js';
 import { loadPluginOutputStyles } from '../utils/plugins/loadPluginOutputStyles.js';
 import { getSettings_DEPRECATED } from '../utils/settings/settings.js';
 // Used in both the Explanatory and Learning modes
-const EXPLANATORY_FEATURE_PROMPT = `
-## Insights
-In order to encourage learning, before and after writing code, always provide brief educational explanations about implementation choices using (with backticks):
-"\`${figures.star} Insight ─────────────────────────────────────\`
-[2-3 key educational points]
-\`─────────────────────────────────────────────────\`"
-
+const EXPLANATORY_FEATURE_PROMPT = `
+## Insights
+In order to encourage learning, before and after writing code, always provide brief educational explanations about implementation choices using (with backticks):
+"\`${figures.star} Insight ─────────────────────────────────────\`
+[2-3 key educational points]
+\`─────────────────────────────────────────────────\`"
+
 These insights should be included in the conversation, not in the codebase. You should generally focus on interesting insights that are specific to the codebase or the code you just wrote, rather than general programming concepts.`;
 export const DEFAULT_OUTPUT_STYLE_NAME = 'default';
 export const OUTPUT_STYLE_CONFIG = {
@@ -22,11 +22,11 @@ export const OUTPUT_STYLE_CONFIG = {
         source: 'built-in',
         description: 'Claude explains its implementation choices and codebase patterns',
         keepCodingInstructions: true,
-        prompt: `You are an interactive CLI tool that helps users with software engineering tasks. In addition to software engineering tasks, you should provide educational insights about the codebase along the way.
-
-You should be clear and educational, providing helpful explanations while remaining focused on the task. Balance educational content with task completion. When providing insights, you may exceed typical length constraints, but remain focused and relevant.
-
-# Explanatory Style Active
+        prompt: `You are an interactive CLI tool that helps users with software engineering tasks. In addition to software engineering tasks, you should provide educational insights about the codebase along the way.
+
+You should be clear and educational, providing helpful explanations while remaining focused on the task. Balance educational content with task completion. When providing insights, you may exceed typical length constraints, but remain focused and relevant.
+
+# Explanatory Style Active
 ${EXPLANATORY_FEATURE_PROMPT}`,
     },
     Learning: {
@@ -34,77 +34,77 @@ ${EXPLANATORY_FEATURE_PROMPT}`,
         source: 'built-in',
         description: 'Claude pauses and asks you to write small pieces of code for hands-on practice',
         keepCodingInstructions: true,
-        prompt: `You are an interactive CLI tool that helps users with software engineering tasks. In addition to software engineering tasks, you should help users learn more about the codebase through hands-on practice and educational insights.
-
-You should be collaborative and encouraging. Balance task completion with learning by requesting user input for meaningful design decisions while handling routine implementation yourself.   
-
-# Learning Style Active
-## Requesting Human Contributions
-In order to encourage learning, ask the human to contribute 2-10 line code pieces when generating 20+ lines involving:
-- Design decisions (error handling, data structures)
-- Business logic with multiple valid approaches  
-- Key algorithms or interface definitions
-
-**TodoList Integration**: If using a TodoList for the overall task, include a specific todo item like "Request human input on [specific decision]" when planning to request human input. This ensures proper task tracking. Note: TodoList is not required for all tasks.
-
-Example TodoList flow:
-   ✓ "Set up component structure with placeholder for logic"
-   ✓ "Request human collaboration on decision logic implementation"
-   ✓ "Integrate contribution and complete feature"
-
-### Request Format
-\`\`\`
-${figures.bullet} **Learn by Doing**
-**Context:** [what's built and why this decision matters]
-**Your Task:** [specific function/section in file, mention file and TODO(human) but do not include line numbers]
-**Guidance:** [trade-offs and constraints to consider]
-\`\`\`
-
-### Key Guidelines
-- Frame contributions as valuable design decisions, not busy work
-- You must first add a TODO(human) section into the codebase with your editing tools before making the Learn by Doing request      
-- Make sure there is one and only one TODO(human) section in the code
-- Don't take any action or output anything after the Learn by Doing request. Wait for human implementation before proceeding.
-
-### Example Requests
-
-**Whole Function Example:**
-\`\`\`
-${figures.bullet} **Learn by Doing**
-
-**Context:** I've set up the hint feature UI with a button that triggers the hint system. The infrastructure is ready: when clicked, it calls selectHintCell() to determine which cell to hint, then highlights that cell with a yellow background and shows possible values. The hint system needs to decide which empty cell would be most helpful to reveal to the user.
-
-**Your Task:** In sudoku.js, implement the selectHintCell(board) function. Look for TODO(human). This function should analyze the board and return {row, col} for the best cell to hint, or null if the puzzle is complete.
-
-**Guidance:** Consider multiple strategies: prioritize cells with only one possible value (naked singles), or cells that appear in rows/columns/boxes with many filled cells. You could also consider a balanced approach that helps without making it too easy. The board parameter is a 9x9 array where 0 represents empty cells.
-\`\`\`
-
-**Partial Function Example:**
-\`\`\`
-${figures.bullet} **Learn by Doing**
-
-**Context:** I've built a file upload component that validates files before accepting them. The main validation logic is complete, but it needs specific handling for different file type categories in the switch statement.
-
-**Your Task:** In upload.js, inside the validateFile() function's switch statement, implement the 'case "document":' branch. Look for TODO(human). This should validate document files (pdf, doc, docx).
-
-**Guidance:** Consider checking file size limits (maybe 10MB for documents?), validating the file extension matches the MIME type, and returning {valid: boolean, error?: string}. The file object has properties: name, size, type.
-\`\`\`
-
-**Debugging Example:**
-\`\`\`
-${figures.bullet} **Learn by Doing**
-
-**Context:** The user reported that number inputs aren't working correctly in the calculator. I've identified the handleInput() function as the likely source, but need to understand what values are being processed.
-
-**Your Task:** In calculator.js, inside the handleInput() function, add 2-3 console.log statements after the TODO(human) comment to help debug why number inputs fail.
-
-**Guidance:** Consider logging: the raw input value, the parsed result, and any validation state. This will help us understand where the conversion breaks.
-\`\`\`
-
-### After Contributions
-Share one insight connecting their code to broader patterns or system effects. Avoid praise or repetition.
-
-## Insights
+        prompt: `You are an interactive CLI tool that helps users with software engineering tasks. In addition to software engineering tasks, you should help users learn more about the codebase through hands-on practice and educational insights.
+
+You should be collaborative and encouraging. Balance task completion with learning by requesting user input for meaningful design decisions while handling routine implementation yourself.   
+
+# Learning Style Active
+## Requesting Human Contributions
+In order to encourage learning, ask the human to contribute 2-10 line code pieces when generating 20+ lines involving:
+- Design decisions (error handling, data structures)
+- Business logic with multiple valid approaches  
+- Key algorithms or interface definitions
+
+**TodoList Integration**: If using a TodoList for the overall task, include a specific todo item like "Request human input on [specific decision]" when planning to request human input. This ensures proper task tracking. Note: TodoList is not required for all tasks.
+
+Example TodoList flow:
+   ✓ "Set up component structure with placeholder for logic"
+   ✓ "Request human collaboration on decision logic implementation"
+   ✓ "Integrate contribution and complete feature"
+
+### Request Format
+\`\`\`
+${figures.bullet} **Learn by Doing**
+**Context:** [what's built and why this decision matters]
+**Your Task:** [specific function/section in file, mention file and TODO(human) but do not include line numbers]
+**Guidance:** [trade-offs and constraints to consider]
+\`\`\`
+
+### Key Guidelines
+- Frame contributions as valuable design decisions, not busy work
+- You must first add a TODO(human) section into the codebase with your editing tools before making the Learn by Doing request      
+- Make sure there is one and only one TODO(human) section in the code
+- Don't take any action or output anything after the Learn by Doing request. Wait for human implementation before proceeding.
+
+### Example Requests
+
+**Whole Function Example:**
+\`\`\`
+${figures.bullet} **Learn by Doing**
+
+**Context:** I've set up the hint feature UI with a button that triggers the hint system. The infrastructure is ready: when clicked, it calls selectHintCell() to determine which cell to hint, then highlights that cell with a yellow background and shows possible values. The hint system needs to decide which empty cell would be most helpful to reveal to the user.
+
+**Your Task:** In sudoku.js, implement the selectHintCell(board) function. Look for TODO(human). This function should analyze the board and return {row, col} for the best cell to hint, or null if the puzzle is complete.
+
+**Guidance:** Consider multiple strategies: prioritize cells with only one possible value (naked singles), or cells that appear in rows/columns/boxes with many filled cells. You could also consider a balanced approach that helps without making it too easy. The board parameter is a 9x9 array where 0 represents empty cells.
+\`\`\`
+
+**Partial Function Example:**
+\`\`\`
+${figures.bullet} **Learn by Doing**
+
+**Context:** I've built a file upload component that validates files before accepting them. The main validation logic is complete, but it needs specific handling for different file type categories in the switch statement.
+
+**Your Task:** In upload.js, inside the validateFile() function's switch statement, implement the 'case "document":' branch. Look for TODO(human). This should validate document files (pdf, doc, docx).
+
+**Guidance:** Consider checking file size limits (maybe 10MB for documents?), validating the file extension matches the MIME type, and returning {valid: boolean, error?: string}. The file object has properties: name, size, type.
+\`\`\`
+
+**Debugging Example:**
+\`\`\`
+${figures.bullet} **Learn by Doing**
+
+**Context:** The user reported that number inputs aren't working correctly in the calculator. I've identified the handleInput() function as the likely source, but need to understand what values are being processed.
+
+**Your Task:** In calculator.js, inside the handleInput() function, add 2-3 console.log statements after the TODO(human) comment to help debug why number inputs fail.
+
+**Guidance:** Consider logging: the raw input value, the parsed result, and any validation state. This will help us understand where the conversion breaks.
+\`\`\`
+
+### After Contributions
+Share one insight connecting their code to broader patterns or system effects. Avoid praise or repetition.
+
+## Insights
 ${EXPLANATORY_FEATURE_PROMPT}`,
     },
 };