Skip to content

Commit 80288b2

Browse files
chore: Added code intelligence plugins (#5057)
* chore: Added code intelligence plugins See: https://code.claude.com/docs/en/discover-plugins#code-intelligence #skip-changelog * Coerce Claude into using LSP rather than grep * . * Apply suggestion from @jamescrosswell * Remove typescript code intelligence pugin
1 parent 715f350 commit 80288b2

File tree

2 files changed

+18
-0
lines changed

2 files changed

+18
-0
lines changed

.claude/settings.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,5 +30,11 @@
3030
"Bash(mv:*)"
3131
],
3232
"deny": []
33+
},
34+
"enabledPlugins": {
35+
"csharp-lsp@claude-plugins-official": true,
36+
"clangd-lsp@claude-plugins-official": true,
37+
"jdtls-lsp@claude-plugins-official": true,
38+
"swift-lsp@claude-plugins-official": true
3339
}
3440
}

AGENTS.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -159,3 +159,15 @@ AI commits MUST include:
159159
```
160160
Co-Authored-By: <Agent Name> <agent-email-or-noreply@example.com>
161161
```
162+
163+
### Code Intelligence
164+
165+
Prefer LSP over Grep/Read for code navigation — it's faster, precise, and avoids reading entire files:
166+
167+
- `workspaceSymbol` to find where something is defined
168+
- `findReferences` to see all usages across the codebase
169+
- `goToDefinition` / `goToImplementation` to jump to source
170+
171+
Use Grep only when LSP isn't available or for text/pattern searches (comments, strings, config).
172+
173+
After writing or editing code, check LSP diagnostics and fix errors before proceeding.

0 commit comments

Comments
 (0)