Prompt pack
Start safely
Prompts for scoping work, protecting secrets, and making the agent stop after one reviewable step.
Open Start safelyThis page is not the whole prompt library. It is the smaller, safer starter set for non-software developers who want a prompt they can copy right now without asking the agent to run wild.
Need the exact safest first move? Open Safe Agent Loop or copy it directly above.
Want every starter prompt in one paste? Use Copy Starter Bundle or open the starter prompt export. The export includes all 4 starter prompts with lesson links and prompt pages.
Scope one change
These starter prompts bias the agent toward one reviewable step instead of a sprawling build request.
Copy, then adapt
Replace the task, files, and constraints with your real context. Keep the guardrails that force the agent to explain itself.
Stop and inspect
The point is not speed. The point is keeping the diff small enough that you can read it, test it, and decide what happens next.
Prompt pack
Prompts for scoping work, protecting secrets, and making the agent stop after one reviewable step.
Open Start safelyPrompt pack
Prompts for a first Claude Code, Codex, or Cursor session so the agent sets a goal, explains scope, justifies tools or loops, verifies the result, and stops after one safe first move.
Open Run your first Claude or agent sessionPrompt pack
Prompts for tightening requests, reviewing diffs, verifying fixes, and debugging without letting the agent thrash or loop blindly.
Open Review and debugIf you are not a software developer, this is the fastest useful on-ramp: copy one safe sample prompt, scope the job, protect secrets, review the diff, and make the agent stop after one clear change you can inspect.
Use this before implementation work when you want the agent to set one goal, explain the plan, verify the result, and stop after one reviewable change.
"I want to work in a safe beginner loop.
Please do only this one task: [describe one tiny change].
Goal:
- outcome: [what should be true]
- scope: [files, pages, or systems in scope]Use this when your current request feels vague and you want the agent to help shape a safer, sharper implementation prompt before files change.
**Use this with Cursor or Claude Code before you ask for implementation work:**
"Help me tighten this coding prompt before any files are changed.
Project context: [stack, app purpose, relevant data model]
Goal: [the feature or fix I want]
Rough prompt: [paste your current prompt]Use this after an AI-generated change lands so the reviewer focuses on correctness, security, edge cases, and misleading tests.
"Review the diff between my branch and `main`.
For every finding:
1. label it as must-fix, should-fix, consider, or optional
2. explain why it matters
3. point to the relevant file or code sectionRun this before you paste configs, screenshots, or terminal output into an AI tool so you do not leak API keys, connection strings, or internal URLs.
"I am about to share this small app with another person for the first time.
Please give me a beginner-safe pre-share review.
Context:
- project: [describe project]
- who will see it: [friend/coworker/client/internal team]Curated prompt packs
If you do not want to browse prompt-by-prompt, open a pack built around one concrete job: getting through your first agent session, tightening prompts, protecting your work, reviewing a diff, getting a demo ready for production, or thinking in systems before the agent writes itself into a corner.
Prompts for a first Claude Code, Codex, or Cursor session so the agent sets a goal, explains scope, justifies tools or loops, verifies the result, and stops after one safe first move.
Featured prompt
Safe Agent Loop
Use this before implementation work when you want the agent to set one goal, explain the plan, verify the result, and stop after one reviewable change.
Prompts for scoping work, protecting secrets, and making the agent stop after one reviewable step.
Featured prompt
Pre-Flight Secrets Check
Run this before you paste configs, screenshots, or terminal output into an AI tool so you do not leak API keys, connection strings, or internal URLs.
Prompts for turning a promising AI-built demo into something you can share, test, deploy, sell, and improve without pretending it is production-ready too early.
Featured prompt
The First Production Stack — Domains, Auth, Data, Logs, and Payments
The practical baseline for turning an AI-built demo into a real software product: DNS, hosting, database, auth, observability, GitHub, durable notes, subscriptions, and security sweeps.
Prompts for tightening requests, reviewing diffs, verifying fixes, and debugging without letting the agent thrash or loop blindly.
Featured prompt
Review The Diff
Use this after an AI-generated change lands so the reviewer focuses on correctness, security, edge cases, and misleading tests.
Prompts for tightening vague requests, decomposing big ideas, using reasoning plans, teaching patterns with examples, and avoiding prompting anti-patterns.
Featured prompt
The Anti-Patterns — Prompts That Produce Bad Code
Recognize and avoid the most common prompting mistakes that lead to buggy, bloated, or wrong code.
Prompts that push the agent toward architecture, tradeoffs, and production-safe structure instead of surface fixes.
Featured prompt
Choosing Your Tech Stack — A Decision Framework
A practical framework for choosing the right tools and technologies for your project — with sensible defaults for AI-assisted builders.
Prompts for Git, checkpoints, backups, and version-control habits before you let the agent touch more files.
Featured prompt
Don't Lose Your Work — Folders, Git, and Checkpoints
The minimum safe setup for total beginners: a real project folder, a Git repo, a remote backup, and repeatable checkpoints.
Need more than the starter pack?
Need the full library instead of the safest first moves? Open the complete prompt archive or step into the beginner-safe start guide that tells you which prompt to run first.