Claude Code prompts

37 prompts

Prompts for Claude Code, Anthropic's coding agent that runs in your terminal and works across a repository. They describe the task, the files and checks involved, and what done looks like, so the agent can plan, edit and verify.

7 results

  • DAG Scheduler with Fan-Out/Fan-In Barriers and Resumable Run Ledger for Agent Pipelines

    Guides Claude Code to build or refactor a dependency-aware DAG scheduler for agent phases, with cycle validation, bounded parallelism, join policies, retries, and an append-only run ledger so interrupted runs resume without redoing finished nodes.

  • Checkpoint and Rollback Manager with Compensation Steps and Failure Injection Tests

    Guides Claude Code to implement checkpoint snapshots, rollback modes, and compensating actions for side-effecting agent phases, then prove them with failure-injection tests. Helps you decide the rollback strategy per phase.

  • Typed Phase Handoff Contracts and Validator for Multi-Agent Pipelines

    Has Claude Code define schema-based handoff contracts between agent phases, generate a validator, and add contract tests. Supports the decision of which phase boundaries need strict contracts versus lightweight checks.

  • Subagent Fan-Out Plan for a Large Codebase Migration

    Plans a big migration so an orchestrating agent can split it into independent chunks for parallel subagents, each with a clear brief, a verification command and merge rules.

  • Agent Run Post-Mortem: Trace Root Cause and Prompt or Tool Fixes

    Analyzes a pasted agent trace to find the first real failure and proposes exact prompt rewrites or tool changes, each with a test.

  • Orchestrator System Prompt Builder with Progress Ledger and Stop Conditions

    Writes a ready-to-deploy orchestrator system prompt that delegates to your workers, tracks progress in a ledger, merges results and stops on defined conditions.

  • Parallel Git Worktree Task Split with Interface Contracts and Merge Order

    Turns a pasted feature spec into independent coding-agent tasks with file ownership, interface contracts, a merge order and a done command for each task.

About Claude Code prompts

How do I give Claude Code one of these prompts?

Start claude in the repository's root folder and paste the prompt as your first message. Fill in the blanks with real paths, commands and limits first; the agent can't guess them.

Should a prompt go into CLAUDE.md?

Only rules that apply to every task, such as build commands and code style, belong in CLAUDE.md. Keep one-off task prompts in the chat so they don't steer later work.

Do these prompts work in other coding agents?

Most do. Codex, Cursor and Copilot's agent mode follow the same kind of task brief; swap any mention of CLAUDE.md for that tool's instruction file, such as AGENTS.md.