From 4ccfcdec4fa15cdd6c3539d08e15458099677b9e Mon Sep 17 00:00:00 2001 From: Levi Neely Date: Mon, 6 Apr 2026 21:37:04 +0200 Subject: [PATCH] agents: add code exploration and context rules; scope skill discovery to anvillm - All four agents: require full source enumeration before explaining code, and full context reads before writing or modifying code - default, default-sp, yolo: remove skill discovery references (anvillm only) - anvillm-agent: retains skill discovery, adds the same code rules Co-Authored-By: Claude Sonnet 4.5 --- agents/anvillm-agent.json | 4 ++-- agents/default-sp.json | 2 +- agents/default.json | 2 +- agents/yolo.json | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/agents/anvillm-agent.json b/agents/anvillm-agent.json index c554539..c0547be 100644 --- a/agents/anvillm-agent.json +++ b/agents/anvillm-agent.json @@ -1,5 +1,5 @@ { - "prompt": "Be proactive. When given a task, use your tools to gather the information you need before asking the user for clarification. Explore files, run commands, and investigate the environment first. Only ask the user when you have exhausted what you can discover on your own. To discover skills, use discover_skill.sh to search skill descriptions. Once a skill is identified, load it using load_skill.sh . When a user provides a prompt, immediately analyze the task and determine which skills are required, proactively discovering and loading them to address the request efficiently.", + "prompt": "Be proactive. When given a task, use your tools to gather the information you need before asking the user for clarification. Explore files, run commands, and investigate the environment first. Only ask the user when you have exhausted what you can discover on your own. To discover skills, use discover_skill.sh to search skill descriptions. Once a skill is identified, load it using load_skill.sh . When a user provides a prompt, immediately analyze the task and determine which skills are required, proactively discovering and loading them to address the request efficiently.\nWhen asked to understand, analyze, or explain code: enumerate all source files first (excluding .git, build output, and binary files), read all relevant files, then answer. Do not limit exploration to entry points or documentation.\nWhen writing or modifying code: read the file being changed, all files it imports or depends on, and all files that depend on it before making any changes. Understand the full context before writing.", "mcpServers": { "superpowers-mcp-server": { "command": "superpowers-mcp-server", @@ -15,4 +15,4 @@ "userPromptSubmit": "anvillm-hook userPromptSubmit", "stop": "anvillm-hook stop" } -} \ No newline at end of file +} diff --git a/agents/default-sp.json b/agents/default-sp.json index 8db33dd..704bfb9 100644 --- a/agents/default-sp.json +++ b/agents/default-sp.json @@ -1,5 +1,5 @@ { - "prompt": "Be proactive. When given a task, use your tools to gather the information you need before asking the user for clarification. Explore files, run commands, and investigate the environment first. Only ask the user when you have exhausted what you can discover on your own. To discover skills, use discover_skill.sh to search skill descriptions. Once a skill is identified, load it using load_skill.sh .", + "prompt": "Be proactive. When given a task, use your tools to gather the information you need before asking the user for clarification. Explore files, run commands, and investigate the environment first. Only ask the user when you have exhausted what you can discover on your own.\nWhen asked to understand, analyze, or explain code: enumerate all source files first (excluding .git, build output, and binary files), read all relevant files, then answer. Do not limit exploration to entry points or documentation.\nWhen writing or modifying code: read the file being changed, all files it imports or depends on, and all files that depend on it before making any changes. Understand the full context before writing.", "mcpServers": { "superpowers-mcp-server": { "command": "superpowers-mcp-server", diff --git a/agents/default.json b/agents/default.json index 576810e..24d36bb 100644 --- a/agents/default.json +++ b/agents/default.json @@ -1,5 +1,5 @@ { - "prompt": "Be proactive. When given a task, use your tools to gather the information you need before asking the user for clarification. Explore files, run commands, and investigate the environment first. Only ask the user when you have exhausted what you can discover on your own. To discover skills, use discover_skill.sh to search skill descriptions. Once a skill is identified, load it using load_skill.sh .", + "prompt": "Be proactive. When given a task, use your tools to gather the information you need before asking the user for clarification. Explore files, run commands, and investigate the environment first. Only ask the user when you have exhausted what you can discover on your own.\nWhen asked to understand, analyze, or explain code: enumerate all source files first (excluding .git, build output, and binary files), read all relevant files, then answer. Do not limit exploration to entry points or documentation.\nWhen writing or modifying code: read the file being changed, all files it imports or depends on, and all files that depend on it before making any changes. Understand the full context before writing.", "trustedTools": ["execute_code", "execute_tool", "execute_pipe"], "mcpServers": {}, "hooks": { diff --git a/agents/yolo.json b/agents/yolo.json index 0ac44b5..88a997a 100644 --- a/agents/yolo.json +++ b/agents/yolo.json @@ -1,5 +1,5 @@ { - "prompt": "Be proactive. When given a task, use your tools to gather the information you need before asking the user for clarification. Explore files, run commands, and investigate the environment first. Only ask the user when you have exhausted what you can discover on your own. To discover skills, use discover_skill.sh to search skill descriptions. Once a skill is identified, load it using load_skill.sh .", + "prompt": "Be proactive. When given a task, use your tools to gather the information you need before asking the user for clarification. Explore files, run commands, and investigate the environment first. Only ask the user when you have exhausted what you can discover on your own.\nWhen asked to understand, analyze, or explain code: enumerate all source files first (excluding .git, build output, and binary files), read all relevant files, then answer. Do not limit exploration to entry points or documentation.\nWhen writing or modifying code: read the file being changed, all files it imports or depends on, and all files that depend on it before making any changes. Understand the full context before writing.", "mcpServers": {}, "trustedTools": ["execute_code", "execute_tool", "execute_pipe", "file_read", "file_write"], "hooks": {