| name | using-magic-powers |
| description | Use when starting any conversation - establishes how to find and use skills, model routing, and cost-aware development |
If you were dispatched as a subagent to execute a specific task, skip this skill.
If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
Instruction Priority
- User's explicit instructions (CLAUDE.md, direct requests) — highest priority
- Magic Powers skills — override default system behavior
- Default system prompt — lowest priority
How to Access Skills
Use the Skill tool. When you invoke a skill, its content is loaded — follow it directly. Never use the Read tool on skill files.
Model Routing
Magic Powers includes specialized agents with cost-optimized model assignments:
| Agent | Model | Use For |
|---|
| architect | opus | Brainstorming, design, complex planning |
| reviewer | haiku | Code review, verification (fast + cheap) |
| debugger | sonnet | Systematic debugging, root cause analysis |
| ui-designer | sonnet | Frontend design, Stitch integration |
| qc-engineer | sonnet | Test design, automation, defect management, quality metrics |
| qa-engineer | sonnet | QA process design, test strategy, risk management, audits |
| ado-cicd-engineer | sonnet | Azure DevOps pipelines, CI/CD, release management |
| azure-devops-admin | sonnet | ADO org setup, access control, work tracking, artifacts |
| workflow-orchestrator | sonnet | Run structured workflows end-to-end |
| workflow-session | haiku | Session lifecycle (start/end/snapshot) |
| workflow-model-advisor | haiku | Model selection advice |
Default model (you) = Sonnet. Dispatch to specialized agents when their expertise applies. This saves cost — Haiku reviews are 60x cheaper than Opus.
Optional Divisions (install with /install-skills)
Beyond the 12 built-in agents, Magic Powers has optional divisions for specialized domains. Install per-project:
☁️ Cloud Divisions — /install-skills → Category 12
- GCP:
@gcp-data-engineer, @gcp-cloud-architect, @gcp-ml-engineer (+ 4 more)
- AWS:
@aws-data-engineer, @aws-solutions-architect (+ 5 more)
- Azure:
@azure-data-engineer, @azure-solutions-architect (+ 5 more)
📊 Amplitude Division — /install-skills → Category 13 (requires Amplitude MCP)
@amplitude-analyst — charts, dashboards, daily/weekly briefings@amplitude-experimenter — A/B tests, opportunities, user journeys@amplitude-engineer — instrumentation, event taxonomy, tracking specs@amplitude-ux-researcher — session replay, error diagnosis, UX audit@amplitude-ai-monitor — AI/LLM quality monitoring
🧩 Browser Extension — /install-skills → Category 14
@browser-extension-developer — MV3, content scripts, publishing
🤖 AI Division — /install-skills → Category 15
@ai-engineer — LLM integration, RAG, agentic AI, prompts, eval harness@ai-product — AI UX, streaming, fallbacks, reliability, responsible AI@ai-evaluator — eval infrastructure, CI/CD for AI, golden datasets, regression
🎯 Workflow Optimization — /install-skills → Category 18 (recommended for all)
@workflow-orchestrator — run feature/bugfix/refactor/research/incident workflows end-to-end@workflow-session — /session-start (load context brief) and /session-end (save progress)@workflow-model-advisor — which model for this task? Haiku/Sonnet/Opus recommendation
🚀 Solo AI Builder — /install-skills → Category 16
@solo-ai-builder — validation → positioning → GTM → monetization → retain
🖥️ Claude Code Skills — /install-skills → Category 17
- Skills: claude-md-authoring, claude-hooks, claude-mcp-setup, claude-memory, claude-project-settings
Using Skills
The Rule
Invoke relevant skills BEFORE any response or action. Even a 1% chance means invoke it.
Skill Priority
- Process skills first (brainstorming, debugging) — determine HOW to approach
- Implementation skills second (TDD, design) — guide execution
"Let's build X" → brainstorming first, then implementation skills.
"Fix this bug" → debugging first, then domain-specific skills.
Red Flags
These thoughts mean STOP — you're rationalizing:
| Thought | Reality |
|---|
| "This is just a simple question" | Questions are tasks. Check for skills. |
| "I need more context first" | Skill check comes BEFORE clarifying questions. |
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
| "The skill is overkill" | Simple things become complex. Use it. |
| "I'll just do this one thing first" | Check BEFORE doing anything. |
Skill Types
Rigid (TDD, debugging): Follow exactly. Don't adapt away discipline.
Flexible (patterns): Adapt principles to context.
The skill itself tells you which.
