Launch price: $49 one-time for all 38 specialists. Get it →
Free tool

Subagent Generator

Describe a role and get a ready-to-use Claude Code subagent file.

1. Describe your subagent

Start from a preset (optional)
File name: .claude/agents/code-reviewer.md
Claude reads this to decide when to hand work to the subagent, so be specific.
Tool access
Where will you save it?

2. System prompt (optional parts)

Your subagent file

code-reviewer.md

    

Checks

    How to use it

    1. Pick a starter preset, or type a role name and describe what the subagent does.
    2. Say when it should be used. This text is what Claude reads to decide when to call it.
    3. Choose which tools it can use and which model it runs on.
    4. Copy or download the file and save it in the folder shown under the preview.
    5. In Claude Code, ask for it by name, for example: "use the code-reviewer subagent to check my last change".

    What a subagent file looks like

    A subagent is a single Markdown file. The top part, between the two --- lines, is settings. Everything below it is the system prompt: the instructions the subagent follows each time it runs. Project subagents live in .claude/agents/ and are shared with your team through your repo. Personal ones live in ~/.claude/agents/ and work in every project.

    ---
    name: code-reviewer
    description: Reviews code changes for bugs and unclear code. Use PROACTIVELY after code is written or changed.
    tools: Read, Grep, Glob
    model: sonnet
    ---
    You are a careful code reviewer.
    
    ## Process
    1. Run git diff to see what changed.
    2. Read the changed files in full.
    3. Report problems, most serious first.
    • name: lowercase letters, numbers and hyphens.
    • description: what it does and when to use it. Claude uses this to choose the subagent.
    • tools: a comma-separated list. Leave the line out and the subagent can use every tool.
    • model: sonnet, opus, haiku or inherit. Leave it out for the default.

    FAQ

    Where do I save the file?

    Save it as .claude/agents/<name>.md inside your project to share it with your team, or ~/.claude/agents/<name>.md to use it everywhere. If both exist with the same name, the project one wins.

    Which tools should I give a subagent?

    Give the fewest it needs. A reviewer or auditor only has to read, so Read, Grep and Glob are enough. Add Edit and Write only for roles that change files, and add Bash only when the role has to run commands such as tests.

    How do I make Claude use it without being asked?

    Write a clear description of when it applies and tick "Let Claude call it automatically". That adds the words "Use PROACTIVELY" to the description, which nudges Claude to hand matching work over on its own. You can always call it by name too.

    Does this tool send my text anywhere?

    No. Everything runs in your browser and nothing is uploaded or stored.

    How long should the description be?

    One or two sentences. Too short and Claude will not know when to use it. Too long and it wastes space in every conversation.

    Want a full team instead of one role? Agentsforce ships 38 ready-made specialists you can drop into your project.

    More free tools

    Give Claude Code a whole team. 38 specialists, one payment of $49.

    Get Agentsforce