-
Install the framework:
/installChoose: current directory, specific path, or global (
~/.claude/) -
Configure skills and settings:
/setup -
Start developing!
Use /install to inject the framework into any project.
| Option | Description |
|---|---|
| Current directory | Install to . |
| Specify path | Enter any project path |
| Global | Install to ~/.claude/ for all projects |
.claude/
├── agents/ (2 workflow agents)
├── commands/ (4 commands)
└── hooks/ (3 hook files)
dev/
├── active/ (your task docs)
└── templates/ (doc templates)
CLAUDE.md (project instructions)
Running /install on a directory with an existing installation will:
- Preserve your
skill-rules.jsonconfiguration - Preserve customized
CLAUDE.md - Update agents, commands, and hook scripts
Use /setup to configure skills and customize settings.
Setup offers several ways to integrate your skills:
- Scan a directory - Enter path to your skills folder
- Use home directory - Scan
~/.claude/skills/ - Skip - Configure manually later
| Location | When to Use |
|---|---|
~/.claude/skills/ |
Global skills for all projects |
.claude/skills/ |
Project-specific skills |
| Custom path | Your own organization |
After scanning, setup offers:
- Configure each - Set keywords for each skill manually
- Smart defaults - Auto-generate keywords from skill names
- No triggers - Just register skills without auto-detection
Smart defaults example:
apex-best-practices.md→ keywords: ["apex", "trigger", "class", "soql"]lwc-dev-guidelines.md→ keywords: ["lwc", "lightning", "component"]
Optionally configure project-specific settings:
- Project name
- Org type (Scratch/Sandbox/Production)
- Test coverage requirement
- Custom naming conventions
Skills are markdown files with domain knowledge.
# Skill Name
## Section 1
- Point 1
- Point 2
## Section 2
Content here...# Apex Best Practices
## Bulkification
- Always handle 200+ records
- Use collections (List, Set, Map)
- Never assume single record
## Governor Limits
- SOQL: 100 queries per transaction
- DML: 150 statements per transaction
- Never put SOQL/DML in loops
## Security
- Enforce CRUD/FLS with USER_MODE
- Use bind variables in dynamic SOQL
- Document "without sharing" usage| Location | Availability |
|---|---|
~/.claude/skills/ |
All projects |
[project]/.claude/skills/ |
This project only |
Edit .claude/hooks/skill-rules.json directly:
{
"skills": {
"my-skill": {
"type": "domain",
"enforcement": "suggest",
"priority": "high",
"promptTriggers": {
"keywords": ["keyword1", "keyword2"],
"intentPatterns": ["(create|build).*pattern"]
},
"fileTriggers": {
"pathPatterns": ["**/*.cls"],
"contentPatterns": ["ClassName"]
}
}
}
}| Field | Purpose |
|---|---|
promptTriggers.keywords |
Words in prompts that trigger skill |
promptTriggers.intentPatterns |
Regex patterns for intent matching |
fileTriggers.pathPatterns |
Glob patterns for file paths |
fileTriggers.contentPatterns |
Regex patterns for file content |
| Command | Purpose |
|---|---|
/install |
Install framework to a directory |
/setup |
Configure skills and settings |
/dev-docs |
Create task documentation |
/dev-docs-update |
Save progress before ending |
| Agent | Use Case |
|---|---|
strategic-plan-architect |
Plan large features |
test-class-generator |
Generate Apex test classes |
Framework not found in current directory.
Run /install first to install the framework.
Solution: Run /install and choose a target directory.
- Verify skill files exist in the scanned directory
- Files must have
.mdextension - Try running
/setupagain
- Check
.claude/hooks/exists - Verify JSON syntax in skill-rules.json:
python -c "import json; json.load(open('.claude/hooks/skill-rules.json'))"
- Verify
.claude/commands/exists - Check files have
.mdextension - Restart Claude Code session