Verify plugin elements against current best practices and optimize for consistency
Validates plugin elements against Claude Code best practices and optimizes for consistency.
/plugin marketplace add lenneTech/claude-code/plugin install lt-dev@lenne-techplugin/Analyze and optimize plugin elements against current Claude Code best practices. Use this command after /clear, context summarization, or when you want to ensure elements are up-to-date and consistent.
/clear to restore best practice awareness| Command | Purpose |
|---|---|
/lt-dev:plugin:element | Create new plugin elements with best practices |
/lt-dev:skill-optimize | Optimize skill files specifically |
MANDATORY: Fetch the latest official documentation from GitHub:
WebFetch: https://github.com/anthropics/claude-code/blob/main/plugins/README.md
WebFetch: https://github.com/anthropics/skills/blob/main/README.md
For specific topics: Use WebSearch: "Claude Code [topic] documentation site:claude.com"
Use AskUserQuestion to determine the check scope:
Question (German): "Was soll geprüft werden?"
Options:
If "Einzelnes Element" is selected, ask for the element path.
Based on scope, inventory all elements to check:
# Skills
find plugins/lt-dev/skills -name "SKILL.md" -type f
# Commands
find plugins/lt-dev/commands -name "*.md" -type f
# Agents
find plugins/lt-dev/agents -name "*.md" -type f
# Hooks
cat plugins/lt-dev/hooks/hooks.json 2>/dev/null || echo "No hooks.json"
For each element, perform the following checks:
Compare against fetched documentation:
permissions.json:
usedBy arrays include all skills/agents using each patternBash(command:*)Check against skills:
# Find all Bash commands used in skills
grep -r "npm \|npx \|lt " plugins/lt-dev/skills/ --include="*.md"
# Compare with permissions.json patterns
cat plugins/lt-dev/permissions.json
.mcp.json:
Check MCP usage:
# Find MCP references in commands
grep -r "Linear\|Chrome\|chrome-devtools\|linear" plugins/lt-dev/commands/ --include="*.md"
grep -r "Chrome MCP\|Linear MCP" plugins/lt-dev/commands/ --include="*.md"
plugin.json:
CLAUDE.md:
Check structure:
# Compare documented structure with actual
ls -la plugins/lt-dev/
ls -la plugins/lt-dev/.claude-plugin/
Create a comprehensive report of findings:
## Plugin Best Practice Check Report
### Summary
- **Elements Checked:** X
- **Passed:** Y
- **Issues Found:** Z
- **Suggestions:** N
### Detailed Findings
#### Skills (X checked)
| Skill | Status | Issues |
|-------|--------|--------|
| skill-name | ✅/⚠️/❌ | [issues if any] |
[Detailed issues per skill]
#### Commands (X checked)
| Command | Status | Issues |
|---------|--------|--------|
| /command-name | ✅/⚠️/❌ | [issues if any] |
[Detailed issues per command]
#### Agents (X checked)
| Agent | Status | Issues |
|-------|--------|--------|
| agent-name | ✅/⚠️/❌ | [issues if any] |
[Detailed issues per agent]
#### Configuration Files
| File | Status | Issues |
|------|--------|--------|
| permissions.json | ✅/⚠️/❌ | [issues if any] |
| .mcp.json | ✅/⚠️/❌ | [issues if any] |
| plugin.json | ✅/⚠️/❌ | [issues if any] |
[Detailed issues per config file]
#### Documentation
| File | Status | Issues |
|------|--------|--------|
| CLAUDE.md | ✅/⚠️/❌ | [issues if any] |
### Recommended Actions
**Critical (fix immediately):**
1. [Critical issue 1]
2. [Critical issue 2]
**Improvements (recommended):**
1. [Improvement 1]
2. [Improvement 2]
**Suggestions (optional):**
1. [Suggestion 1]
2. [Suggestion 2]
After presenting the report, ask (in German):
"Ich habe [N] Probleme und [M] Verbesserungsvorschläge gefunden.
Möchtest du:
For each fix:
After all fixes:
## Fix Summary
- **Applied:** X fixes
- **Skipped:** Y items
- **Manual action required:** Z items
### Changes Made
1. [Change 1]
2. [Change 2]
### Manual Actions Required
1. [Action 1] - [Reason]
usedBy arraysFor a fast check without full documentation fetch, use this condensed checklist:
Skills: name + description (max 280 chars, WHEN focus)
Commands: description (WHAT focus)
Agents: name + description + model + tools
- File name is kebab-case
- # Title exists
- ## Sections use level 2
- Language is English
- Purpose stated in first paragraph
- "When to Use" section exists
- Related elements mentioned
permissions.json:
- All npm/npx/lt commands have patterns
- usedBy arrays reference existing skills
.mcp.json:
- All used MCP servers are configured
- Server types are valid (stdio/http)
plugin.json:
- Version is semver format
- Required fields present (name, version, description)
CLAUDE.md:
- Repository structure matches actual layout
- Configuration docs are current