Claude Code Mastery Prompt Pack (24 Memo Prompts → From Basics to Production)

1) Pick ONE module per session (30–60 min).

2) Start in a repo (or a scratch repo). Add/adjust CLAUDE.md using the template below.

3) Paste the prompt into Claude Code.

4) Always request: (a) plan, (b) diffs, (c) tests, (d) rollback instructions.

5) End each session with a “Memo Card” (Claude generates it) and store it in /docs/memos/.

Recommended cadence:

Output convention (ask Claude to comply):

Create / update a file named CLAUDE.md at repo root.

# Project context

# Environment

# Architecture map

# Engineering standards

# Decision policy

# Safe operations

# Output format

Always respond with:

Assumptions → Plan → Diffs/Files → Commands → Tests → Risk/Rollback → Memo card.

Optional: add a “Definition of Done” block for your team:

Below are 24 prompts mapped to the 24 topics. Paste one at a time.

1) Opening keynote → Your personal mastery roadmap

Prompt:

"You are my Claude Code coach. Given my background: <1–2 lines>, my goal: <goal>, and my constraints: <time/tools>, design a 10-session learning plan using Claude Code in a real repo. For each session, give: objective, exact tasks, success criteria, and a ‘memo card’ summary template. Ask me up to 5 questions only if essential."

2) Beyond basics (CLAUDE.md, MCP, skills, subagents)

Prompt:

"Audit this repo and propose an ‘AI-native’ setup: improve CLAUDE.md, define 3–5 reusable skills (named procedures), and propose 2 subagents (roles, boundaries, handoff format). If you mention MCPs, describe what capability they would provide and how we’d test it safely. Output concrete file changes."

3) Build an AI engineering team (roles & workflow)

Prompt:

"Design a lightweight ‘AI engineering team’ operating model for a <team size> team building <product>. Define roles (PM, eng, QA, SRE, security), how Claude Code fits each role, the review gates, and a weekly cadence. Provide Slack/Linear/Jira-ready checklists and an escalation policy when the model is wrong."

4) Get more from the platform (search, comparison, batching)

Prompt:

"Teach me how to use: (a) search-like behavior, (b) model comparison, (c) batching work. Provide 5 example tasks from THIS repo and show how to batch them safely. Add a ‘when not to batch’ section."

5) The prompting playbook (battle-tested patterns)

Prompt:

"Create a prompting playbook for Claude Code in this repo: 10 patterns (e.g., spec-first, diff-first, tests-first, refactor boundaries, bug triage, log-to-fix, PR review, performance audit, security pass, documentation). For each pattern: when to use, exact prompt, expected output, common failure modes."

6) Capability curve (what to delegate vs keep)

Prompt:

"Build a ‘capability curve’ rubric for my use of Claude Code: categorize tasks into L1–L5 (safe → risky). For each level, list examples in THIS codebase, required guardrails, and approval gates. Output a one-page policy I can share with my team."

7) Design with Claude: from prompt to production

Prompt:

"Take this feature idea: <idea>. Produce a production-ready spec: user story, acceptance criteria, API/DB changes, UX notes, edge cases, observability, rollout plan. Then generate an implementation plan that minimizes risk (small diffs). End with a PR checklist."

8) Create with Claude on Google Cloud (cloud deployment template)

Prompt:

"Assume we deploy on Google Cloud (Cloud Run/GKE/Functions—choose best fit). For this repo, propose an end-to-end deployment blueprint: CI/CD, secrets, IAM, logging/metrics, cost controls. Provide terraform-like pseudocode or step-by-step CLI commands; include rollback and environment separation (dev/stage/prod)."

9) Agents that trade by themselves (agent autonomy constraints)

Prompt:

"Using the ‘autonomous trading agent’ as inspiration, define a general autonomy framework for agents in high-stakes domains. Give: allowed actions, forbidden actions, simulation/backtesting requirement, human-in-the-loop checkpoints, and an incident playbook. Make it domain-agnostic so I can adapt it to <my domain>."

10) Choose the right model (selection matrix)

Prompt:

"Create a model selection matrix for our workflows. Dimensions: cost, latency, context needs, reasoning depth, tool use, determinism, safety. Map 8 common tasks (coding, refactor, test gen, triage, docs, data analysis, planning, review) to recommended model profiles. Output as a table plus decision rules."

11) Memory & ‘dreaming’ for self-learning agents (practical memory design)

Prompt:

"Design a practical memory system for an agent working on this repo. Include: short-term scratchpad, long-term facts, project knowledge base, retrieval strategy, and ‘reflection’ jobs. Provide concrete file structure (/docs, embeddings optional), update rules, and tests to prevent stale memory."

12) What legal agents inherit from code agents (governance)

Prompt:

"Compare code agents vs legal/compliance agents. Identify shared primitives (tool use, retrieval, audit logs, citations, refusal, escalation). Then propose governance controls we should implement in code today that will satisfy future compliance needs (auditability, traceability, approvals)."

13) Speed to production with managed agents (operationalization checklist)

Prompt:

"Pretend we have access to managed agent infrastructure. What operational requirements must our agent meet to be ‘managed’? Provide a checklist: auth, rate limits, retries, idempotency, state, logging, metrics, alerting, sandboxing, policy enforcement. Apply it to our current repo and list gaps."

14) Build a production-ready agent (reference architecture)

Prompt:

"Design a production-ready agent architecture for <use case>. Include: orchestrator, tools, policy engine, memory, human review UI, evaluation harness, and deployment topology. Provide sequence diagrams in text and a folder/file layout for implementation."

15) The thinking lever (quality controls that improve reasoning)

Prompt:

"Give me 12 ‘thinking levers’ to increase Claude Code output quality WITHOUT making it slow. Examples: clarify constraints, request invariants, force counterexamples, require tests, ask for rollback, ask for 2 options, isolate risky steps. For each lever: exact one-liner I can paste, and when to use it."

16) Sidecoding at scale (turn prototypes into systems)

Prompt:

"We have many small ‘sidecoded’ features. Create a process to industrialize them: intake criteria, architecture review, refactor budget, test minimums, documentation, ownership, SLAs, observability. Provide a scorecard (0–100) and thresholds for promote/hold/kill."

17) Building an AI-native company at scale (org patterns)

Prompt:

"Synthesize operating patterns for scaling AI-native product development (like large org case studies). Produce: org structure options, platform vs product split, internal tooling, evaluation culture, data governance, enablement. Then tailor it to my org: <context>. Output a 90-day plan."

18) From 1 person to 80 (systems for leverage)

Prompt:

"Assume I’m a small team aiming to scale impact fast. Create ‘leverage systems’: reusable prompts, code generators, internal templates, onboarding playbooks, self-serve docs. Provide a concrete backlog of 20 leverage items with ROI estimates and dependencies."

19) Proactive agent workflow (signals → actions)

Prompt:

"Design a proactive agent workflow for this repo: what signals to monitor (CI failures, error logs, dependency CVEs, performance regression), how to triage, and what actions are safe to auto-take (open PR, draft issue, suggest patch). Provide a policy matrix: signal × action × required approval."

20) Build agents with Microsoft Foundry (portable abstraction)

Prompt:

"I might use Microsoft Foundry (or similar). Design a provider-agnostic abstraction layer so our agent logic is portable. Define interfaces for: model calls, tools, memory, evals, logging, auth. Provide example pseudocode and a migration plan from a monolithic script to this architecture."

21) Coding isn’t the constraint anymore (bottleneck analysis)

Prompt:

"Help me identify the real bottleneck in my delivery pipeline. Ask me 10 diagnostic questions. Then output: top 3 bottlenecks (e.g., unclear specs, review latency, testing, deployment friction, stakeholder alignment), and for each, an AI-assisted intervention with measurable metrics and a 2-week experiment plan."

22) Claude on AWS: code to orchestration (AWS blueprint)

Prompt:

"Assume AWS deployment. For this repo, propose an architecture using AWS primitives (choose appropriate services). Include: CI/CD, secrets, IAM, logging/metrics, queues, scaling, cost controls. Provide a phased rollout plan and rollback strategy."

23) Stop babysitting your agents (autonomy without chaos)

Prompt:

"Create a ‘no-babysitting’ operating model: define which tasks can be autonomous, how to set guardrails, how to review outputs efficiently, and how to run evaluations continuously. Provide templates: Agent Charter, Tool Policy, Review Checklist, Incident Report."

24) What’s new in Claude Code (update routine)

Prompt:

"Create a monthly update routine for staying current with Claude Code. Output: a checklist, a 60-minute monthly agenda, what to test in a sandbox repo, and a changelog template. Also propose how to communicate changes to the team and update CLAUDE.md + skills."

Bonus: universal ‘memo card’ generator prompt

"Summarize today’s work into a memo card with: Goal, Key decisions, Commands used, Files changed, Tests, Known risks, Next action. Keep under 1200 characters."

Bonus: safe ‘diff-first’ implementation prompt

"Implement the plan via minimal diffs. Show proposed changes file-by-file before writing. Do not delete code unless necessary. Add/adjust tests. Provide exact commands to run locally."

A) Session score (0–5 each, total /25)

1. Clarity: requirements & acceptance criteria explicit

2. Safety: rollback path + no secrets

3. Testability: tests added/updated, deterministic repro

4. Maintainability: small diffs, naming, docs

5. Observability: logs/metrics/alerts considered

B) Agent readiness score (0–100)

Thresholds:

1) Agent Charter (1 page)

2) Tool Policy (table)

Columns: Tool | Risk | Allowed scopes | Rate limits | Approval needed? | Logging

3) PR Review checklist (AI-assisted)

4) Incident report

5) Continuous eval harness (starter)