A Claude Code agent, or subagent, is a Markdown file that gives Claude a specialist role: its own instructions, a limited set of tools and a model. The main session hands it a task, it works in its own context, and only the result comes back. These pages explain ten of the specialists in the Agentsforce kit: what each one does, what is in its file, and when to use a different one.
Resources
Claude Code Agents
Ten specialist subagents for Claude Code: what each one does, and when to use it.
Code Reviewer Subagent for Claude Code
A code reviewer subagent checks what a change did, not whether a file looks fine.
See the agent →
Debugging Subagent for Claude Code
A debugging subagent finds why a bug happens before changing code.
See the agent →
Test-Driven Development Subagent for Claude Code
A TDD subagent writes a failing test, watches it fail for the expected reason, writes the smallest code that passes, then refactors, one small slice at a time.
See the agent →
Tech Lead Agent for Claude Code
A tech lead agent plans work instead of writing it.
See the agent →
Frontend Design Subagent for Claude Code
A frontend design subagent builds interfaces that fit what already exists.
See the agent →
API Engineer Subagent for Claude Code
An API subagent designs and changes endpoints that clients depend on.
See the agent →
Database Engineer Subagent for Claude Code
A database subagent changes schemas and queries without risking your data.
See the agent →
WordPress Plugin Subagent for Claude Code
A WordPress plugin subagent builds plugins that are safe on a shared, global codebase.
See the agent →
WordPress SEO Audit Subagent for Claude Code
A WordPress SEO subagent finds the search problems WordPress itself creates.
See the agent →
Shopify Theme and Liquid Subagent for Claude Code
A Shopify theme subagent builds Online Store 2.0 sections, blocks and templates.
See the agent →
Which agent for which job
| Job | Agent | Tools |
|---|---|---|
| Before you merge a branch or open a pull request | Code Reviewer | Read-only |
| A test fails and the reason is not obvious | Debugging Specialist | Reads and edits |
| Business rules such as pricing, discounts, tax or permissions | TDD Engineer | Reads and edits |
| A feature that touches several parts of the codebase | Tech Lead | Read-only |
| A new page, dashboard or landing page | Frontend Design | Reads and edits |
| Adding new REST or GraphQL endpoints | API Engineer | Reads and edits |
| Schema changes on tables that already hold real data | Database Engineer | Reads and edits |
| Building a custom plugin for a client site | WordPress Plugin Engineer | Reads and edits |
| Search Console shows many crawled-but-not-indexed or duplicate pages | WordPress SEO Auditor | Read-only |
| New sections or blocks for an Online Store 2.0 theme | Shopify Theme and Liquid Engineer | Reads and edits |
How agent files work
Each agent is one .md file. The top, between two --- lines, holds settings: name, a description that tells Claude when to delegate, the tools it may use and the model. Everything below is the agent's instructions. Project agents live in .claude/agents/ and are shared through your repository; personal ones live in ~/.claude/agents/. Run /agents in Claude Code to see which are loaded.
To write your own, start with the free Subagent Generator, or read how to create a Claude Code subagent. For other people's collections, see the best Claude Code subagent collections.
Get all 55 specialists
These ten are part of a set of 55 specialists and 89 playbooks for engineering, marketing, WordPress and Shopify work. Get Agentsforce for a one-time $49 and one command installs them into your project.
Give Claude Code a whole team. 55 specialists, one payment of $49.
Get Agentsforce