claude-dev-env 2.28.0 → 2.29.0

package/rules/conservative-action.md

@@ -1,17 +0,0 @@
-# Conservative Action
-
-Source: [Anthropic - Tool Usage](https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/claude-prompting-best-practices#tool-usage)
-
-<do_not_act_before_instructions>
-When the user's intent is ambiguous, default to research and recommendations rather than taking action. Provide information, explain options, and surface tradeoffs — then let the user decide before making changes.
-
-Proceed with edits, file modifications, or implementations only when the user explicitly requests them.
-</do_not_act_before_instructions>
-
-## Deciding whether to act
-
-- If the user asks a question, answer the question. Do not also fix the thing they asked about.
-- If the user describes a problem, investigate and recommend. Do not jump to implementation.
-- If the user says "do it", "go ahead", "make the change", or similarly explicit language, proceed with action.
-- Once the user has explicitly asked and you have what you need, act — do not re-open settled facts or decisions, and do not re-survey options you will not pursue. This rule governs the ambiguous case; the clear case belongs to `long-horizon-autonomy`.
-- When in doubt, put the decision to the user through `AskUserQuestion` with two options: show the approach first, or make the change now.

package/rules/context7.md

@@ -1,8 +0,0 @@
-When working with libraries, frameworks, or APIs — use Context7 MCP to fetch current documentation instead of relying on training data. This includes setup questions, code generation, API references, and anything involving specific packages.
-
-## Steps
-
-1. Call `resolve-library-id` with the library name and the user's question
-2. Pick the best match — prefer exact names and version-specific IDs when a version is mentioned
-3. Call `query-docs` with the selected library ID and the user's question
-4. Answer using the fetched docs — include code examples and cite the version

package/rules/few-words.md

@@ -1,3 +0,0 @@
-# Few Words
-
-small words. few words. always. forever.

package/rules/parallel-tools.md

@@ -1,23 +0,0 @@
-# Parallel Tool Calls
-
-Source: [Anthropic - Parallel Tool Calling](https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/claude-prompting-best-practices#optimize-parallel-tool-calling)
-
-<use_parallel_tool_calls>
-When multiple tool calls have no dependencies between them, make all independent calls in a single response. Only sequence calls when a later call needs an earlier call's result.
-</use_parallel_tool_calls>
-
-## Examples
-
-- Reading 3 files: call all 3 Read operations at once.
-- Running independent searches: launch all Grep/Glob calls simultaneously.
-- Checking git status + reading a config file: both in one response.
-- Reading a file, then editing based on its content: sequential (edit depends on read result).
-
-## Guard rails
-
-- Use real parameter values only. Do not guess or use placeholders to force parallelism.
-- If you are unsure whether calls are independent, run them sequentially.
-
-## The one surface that serializes
-
-Harness tool calls — Read, Grep, Glob, and the rest — carry no shared cost and parallelize freely. A large shell filesystem walk does not: parallel full-tree searches contend for the shell and can lock the host, so issue those one at a time. See [`filesystem-search.md`](filesystem-search.md).