claude-dev-env 1.64.1 → 1.64.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/CLAUDE.md +46 -0
  2. package/package.json +1 -1
package/CLAUDE.md CHANGED
@@ -86,3 +86,49 @@ When changing how skills, rules, or hooks install or sync in this repo (for exam
86
86
  - **task_scope:** Match every action to what was explicitly requested. When intent is ambiguous, research official docs and present options via AskUserQuestion before making any changes. Proceed with edits only on explicit instruction.
87
87
  - **confirm_implementation_forks:** When two or more viable paths would satisfy the goal and the choice changes the deliverable — its scope, completeness, deferred work, dependencies, or a hard-to-reverse contract — stop and ask which path via AskUserQuestion before implementing. A path that defers work or leaves a placeholder creating a follow-up task is itself a fork to surface, not a default to take silently. Phrase the question in plain language with only the detail needed to decide. See [`confirm-implementation-forks`](rules/confirm-implementation-forks.md).
88
88
  - **disambiguate_overloaded_terms:** When a word in the request has two different technical meanings — "conflict" (git-merge versus functional/behavioral), "sync" (fast-forward versus commit), and the like — confirm which one is meant via AskUserQuestion before analyzing or acting.
89
+
90
+ ## Serena (Code Intelligence MCP)
91
+
92
+ The `mcp__serena__*` tools expose LSP-level code intelligence for any activated project.
93
+
94
+ ### CRITICAL: Call `initial_instructions` first
95
+ Before any coding task, call the `initial_instructions` tool to load the Serena Instructions Manual.
96
+
97
+ ### When to use Serena
98
+ - **Symbol declaration** → `mcp__serena__find_declaration`
99
+ - **All references to a symbol** → `mcp__serena__find_referencing_symbols`
100
+ - **Implementations of an interface/class** → `mcp__serena__find_implementations`
101
+ - **Rename across codebase** → `mcp__serena__rename_symbol`
102
+ - **Targeted body replacement / insertion** → `replace_symbol_body`, `insert_after_symbol`, `insert_before_symbol`
103
+ - **Safe symbol removal (no references)** → `mcp__serena__safe_delete_symbol`
104
+ - **File diagnostics** → `mcp__serena__get_diagnostics_for_file`
105
+
106
+ ### Tool hierarchy for code navigation
107
+ 1. **Serena** — symbol-level navigation (declarations, references, implementations, rename)
108
+ 2. **Everything** (`everything_search`) — file-system search by name/path/extension
109
+ 3. **Grep/Glob** — content and pattern matching
110
+
111
+ ## Everything Search (MCP Tool)
112
+
113
+ This machine has **Everything (voidtools)** running with an HTTP server on port 54321.
114
+ The `everything_search` MCP tool is available in every session.
115
+
116
+ ### Use Everything for file-system searches
117
+ Use `everything_search` for finding files by name, path, extension, size, or date. For content searches, use Grep — Everything's `content:` search is a fallback when Grep returns nothing.
118
+
119
+ ### Fallback order
120
+ 1. **Everything** (`everything_search`) — file-system search by name/path/extension/size/date, and content search
121
+ 2. **Grep** — complex regex content searches if Everything's `content:` returns nothing
122
+ 3. **Glob** — precise relative-path pattern matching within the current project
123
+
124
+ ### Search syntax quick reference
125
+ - `ext:py` — find by extension (multiple: `ext:ts;js`)
126
+ - `path:src\components` — match against full path
127
+ - `count:10` — limit number of results to 10
128
+ - `*.config.*` — wildcards
129
+ - `size:>10mb` — size filter
130
+ - `dm:today` / `dm:thisweek` — date modified filter
131
+ - `content:keyword` — search inside file contents
132
+ - `parent:node_modules package.json` — match parent folder
133
+ - `foo bar` — AND, `foo | bar` — OR, `!foo` — NOT
134
+ - `"exact phrase"` — literal match
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-dev-env",
3
- "version": "1.64.1",
3
+ "version": "1.64.3",
4
4
  "description": "Claude Code development standards — rules, hooks, agents, commands, and skills",
5
5
  "type": "module",
6
6
  "bin": {