Skills
The 28 Wield skills, including a built-in assistant that helps you choose where to start.
Skills
Wield packages reusable engineering behavior as skills. Use /wield:<name> in
Claude Code or $wield:<name> in Codex. Wield includes 28 skills: 27 task
and workflow skills organized into seven groups by intent, plus the support
assistant.
Start with the assistant
Not sure which skill fits? Ask the built-in Support & orientation assistant. It maps your goal to the current relevant skill, gives you the command, and offers to run it:
/wield:support help me choose a review workflow # Claude Code
$wield:support help me choose a review workflow # CodexWithout a goal, it starts with broad areas and narrows the choices as you answer. Those conversational areas are designed for progressive discovery and do not need to match this site's seven catalog groups exactly.
Skills compose. A planning skill produces a plan a build skill executes; a review skill gates what a delivery skill ships. The Build & execute and Investigate & review groups are where most loops run.
Browse by intent
Plan & ideate
Brainstorm, plan, map scenarios, and reason through hard problems before writing code.
Build & execute
Implement features, fix errors, optimize against metrics, bootstrap projects, and run git workflows.
Investigate & review
Scout code, audit changes, look up documentation, and run security or whole-codebase reviews.
Docs & knowledge
Initialize and maintain docs, and look up library and framework APIs.
Design & visuals
Build polished UI, apply design intelligence, and automate live browser or desktop work.
Extend Wield
Author reusable skills and automate browsers or desktop apps.
Deliver & present
Deploy to any platform, run tests, and manage progress against a plan.
Skill routing
Wield ships routing rules that help Claude pick the right skill for a task. Two are worth knowing about:
- Domain routing maps a domain (frontend, security, git, docs) to the skill that fits the user's intent.
- Workflow routing sequences skills for multi-step tasks — for example, the core development loop:
/wield:implementation-planning → /wield:feature-building → /wield:test-generation
→ /wield:code-audit → /wield:release-pipelineSee Rules for how routing is defined and loaded.
A note on scope
These docs describe what each skill does, when to use it, and what to expect. They intentionally don't reproduce private prompt internals or embedded operating rules — just the behavior you interact with.