NEW: Claude Code Security — research preview

Claude Code Prompt Collection

Independently authored prompt templates for AI coding agents — system prompts, tool prompts, agent delegation, memory management, and multi-agent coordination.

Read time: 3 min

title: "Claude Code Prompt Collection" description: "Independently authored prompt templates for AI coding agents — system prompts, tool prompts, agent delegation, memory management, and multi-agent coordination." section: "Claude" readTime: "3 min"

Claude Code Prompt Collection

An independently authored collection of prompt templates for building AI coding agents. Every prompt in this collection was written from scratch by studying how production coding agents structure safety rules, route tools, delegate to subagents, and manage memory — then implementing the same patterns in original language.

Attribution: Source: repowise-dev/claude-code-prompts — MIT License. Independently authored by the RepoWise team. Not affiliated with Anthropic.


What's Inside

CategoryCountCovers
System Prompts2Agent identity, safety rules, code style, tool routing, output format; multi-agent coordinator
Tool Prompts11Shell, file read/edit/write, grep, glob, web search/fetch, agent launcher, ask user, plan mode
Agent Prompts5General purpose, code explorer, solution architect, verification specialist, documentation guide
Memory Prompts4Conversation summarization, session notes, memory extraction, memory consolidation
Utility Prompts4Session titles, tool summaries, away recaps, next-action suggestions
Patterns9Commentary on each pattern with reusable templates

Quick Start

  1. Browse the Patterns page to understand how production coding agents structure their prompts.
  2. Copy any complete prompt from System Prompts or Tool Prompts into your own agent configuration.
  3. Replace {{PLACEHOLDER}} values with your stack, tool names, and risk policy.
  4. For Cursor or VS Code users, the Agent Prompts section covers specialized subagent configurations you can drop into your setup.

How the Prompts Fit Together

┌─────────────────────────────────────────────┐
│           SYSTEM PROMPT                     │
│  Identity · Safety · Code Style · Tools     │
└───────────────────┬─────────────────────────┘
                    │ governs
        ┌───────────┼───────────┐
        ▼           ▼           ▼
  TOOL PROMPTS  AGENT PROMPTS  MEMORY PROMPTS
  Shell · File  Explorer ·     Summary ·
  Grep · Glob   Architect ·    Session Notes ·
  Web · Agent   Verifier ·     Extraction ·
  Ask · Plan    Docs Guide     Consolidation
        │
        ▼
  UTILITY PROMPTS
  Title · Summary · Recap · Next Action

The system prompt is the behavioral contract that governs all other activity. Tool prompts define how each individual tool should be used. Agent prompts configure specialized subagents. Memory prompts manage context across long sessions. Utility prompts handle small UX details like session titles and away recaps.


Prompt Engineering Methodology

These prompts follow patterns observed in how production coding agents behave:

  • Layered priority — system instructions override developer instructions override user instructions override tool feedback
  • Intent-based tool routing — each tool has clear rules for when to use it and what NOT to use it for
  • Risk-tiered caution — low/medium/high risk tiers with different safeguard requirements
  • Adversarial verification — verification means running commands and checking output, not reading code and deciding it "looks correct"
  • Minimal context memory — compact memory objects with explicit expiry for stale assumptions

See the Patterns page for deep analysis of each pattern with reusable templates.


Not affiliated with or endorsed by Anthropic. "Claude Code" is used here to describe the subject matter under nominative fair use.