Files

Kieran Klaassen 35b39ddc10 [2.10.1] Fix command collisions and bugs

Fixes:
- #40: Add missing `name:` field to heal-skill.md and create-agent-skill.md
- #41: Rewrite corrupted prime.md (was containing CLAUDE.md text)
- #42: Namespace workflow commands as `compound:*` to avoid collision with built-in `/plan`
- #36: Shorten Playwright MCP alias from `playwright` to `pw` (64 char limit)

Command renames:
- /plan → /compound:plan
- /review → /compound:review
- /work → /compound:work
- /compound → /compound:codify

Removed:
- Deprecated /codify command (use /compound:codify)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2025-12-10 18:38:31 -08:00

2.3 KiB

Raw Blame History

name, description, argument-hint

name

description

argument-hint

prime

Prime Claude with project context by reading key files and understanding the codebase structure

optional
specific area to focus on

Prime Command

Prime yourself with essential project context to work effectively in this codebase.

Workflow

1. Discover Project Structure

First, understand the project layout:

# Find project root indicators
ls -la | head -20

# Check for common config files
ls -la *.json *.yml *.yaml *.toml 2>/dev/null | head -10

# Find source directories
ls -d */ 2>/dev/null | head -10

2. Read Key Documentation

Read project documentation in this order:

CLAUDE.md (if exists) - Project-specific Claude instructions
README.md - Project overview and setup
CONTRIBUTING.md (if exists) - Development guidelines
.claude/ directory (if exists) - Custom commands and config

3. Understand Tech Stack

Identify the technology stack:

Ruby/Rails: Look for Gemfile, config/routes.rb
JavaScript/Node: Look for package.json, tsconfig.json
Python: Look for requirements.txt, pyproject.toml, setup.py
Go: Look for go.mod
Rust: Look for Cargo.toml

4. Map Key Directories

For the identified stack, explore the structure:

Rails projects:

app/models/ - Domain models
app/controllers/ - Request handlers
app/views/ or app/components/ - UI layer
config/ - Configuration
db/schema.rb - Database structure

Node/JS projects:

src/ or lib/ - Source code
components/ - UI components
api/ or routes/ - API endpoints
tests/ or __tests__/ - Test files

5. Summarize Context

After priming, provide a brief summary:

Project Context

Name: [project name] Stack: [technologies identified] Key directories: [important paths] Special instructions: [from CLAUDE.md if present]

Ready to help with: [list 3-5 things you can now assist with]

Focus Areas

If the user specified a focus area ($ARGUMENTS), prioritize:

"models" - Focus on data layer and business logic
"api" - Focus on endpoints and request handling
"frontend" - Focus on UI components and views
"tests" - Focus on test structure and patterns
"config" - Focus on configuration and environment

2.3 KiB Raw Blame History