From elixir-phoenix
Recommends the right /phx: command for planning, review, debug, deploy, or test tasks by classifying user intent from query, git status, and existing plans.
How this skill is triggered — by the user, by Claude, or both
Slash command
/elixir-phoenix:helpThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Helps users find the right command, skill, or agent for their situation.
Helps users find the right command, skill, or agent for their situation.
/phx:help # Analyze context, suggest commands
/phx:help how do I debug this? # Route to /phx:investigate
/phx:help add a new feature # Route to /phx:plan -> /phx:work
$ARGUMENTS — optional description of what the user wants to doIf $ARGUMENTS is non-empty, use it as primary signal.
Always gather ambient context (run in parallel):
.claude/plans/*/plan.md — active work in progress?.claude/solutions/**/*.md — prior knowledge?Read references/tool-catalog.md for the full routing table.
Map the user's situation to one of these categories:
| Category | Signals | Primary Commands |
|---|---|---|
| Starting out | No plans, new to plugin | /phx:intro |
| Ideation | "explore", "brainstorm", "not sure", "how to approach", "vague idea" | /phx:brainstorm |
| New feature | "add", "build", "implement", multi-file | /phx:plan → /phx:work |
| Quick change | Single file, <50 lines, "fix typo" | /phx:quick |
| Bug | Error, stack trace, "broken", "failing" | /phx:investigate |
| Review | "check", "review", PR ready | /phx:review |
| Performance | "slow", "N+1", "memory" | /phx:perf, /ecto:n1-check, /lv:assigns |
| Research | "how to", "best practice", "evaluate lib" | /phx:research |
| Resume work | Existing plan with unchecked tasks | /phx:work --continue |
| Post-fix | "that worked", solved a hard bug | /phx:compound |
| Full cycle | Large feature, new domain area | /phx:full |
| Project health | "audit", "tech debt", "overall quality" | /phx:audit, /phx:techdebt |
| Deployment | "deploy", "release", "production" | /phx:verify then deploy skill |
| Permissions | "too many prompts", "allow", "permission fatigue" | /phx:permissions |
If high confidence (clear match to one category): Present the recommendation with:
If medium confidence (2-3 possible matches):
Use AskUserQuestion with the top options, each with a one-line explanation.
If low confidence (vague or no signal): Ask ONE focused clarifying question. Examples:
Then recommend based on the answer.
After recommending, always add:
/phx:help anytime to get routing advice"/phx:intro for a full plugin walkthrough"/phx:plan Add user notifications not just "use the plan command"intent-detection (auto-trigger) with explicit invocation/phx:intro for onboardingnpx claudepluginhub oliver-kriska/claude-elixir-phoenix --plugin elixir-phoenixRoutes ambiguous work requests to matching /phx: workflows like /phx:investigate for bugs, /phx:plan for features, or /phx:brainstorm for ideation based on keyword signals.
Guides developers on creating, structuring, and organizing slash commands for Claude Code. Covers YAML frontmatter, dynamic arguments, bash execution, user interactions, and best practices for reusable command workflows.
Guides creation of Claude Code slash commands using YAML frontmatter, XML tags like <objective> and <process>, dynamic context, and argument handling.