Home · Resources · Prompt Patterns Cheat Sheet

The Prompt Patterns Cheat Sheet for Student Builders

Updated July 2026Free printable · works with Claude Code, Cursor, and any AI coding tool

The difference between students who ship and students who flail isn’t typing speed — it’s prompt discipline. These are the eight patterns we drill in every Atlantic Coders course, distilled onto one printable page. They work in Claude Code, Cursor, or any AI coding tool, because they’re really just good engineering communication: context, small steps, constraints, and verification. Tape it next to your screen until they’re habits.

Prompt Patterns for Student Buildersredwoodacademy.ai

1 · Set the scene first

The AI can't see your project unless you tell it. Start sessions with what you're building, what it's built with, and where you are.

I'm building a study-timer web app (HTML/CSS/JS, no framework). The timer works. Now I want to add streak tracking.

2 · One job per prompt

“Build my whole app” produces a mess you can't check. Ask for one small thing, verify it works, then ask for the next.

Add a "reset streak" button next to the counter. Don't change anything else.

3 · Ask for the plan before the code

Making the AI explain its approach first catches bad ideas while they're still cheap — and teaches you how it thinks.

Before writing code: what's your plan for storing streaks, and what could go wrong with it?

4 · Show, don't describe

An example of the input and the output you want beats three sentences of description.

Format dates like this: "Mon, Jul 20". Example: 2026-07-20 → "Mon, Jul 20".

5 · Constrain it

Tell it what NOT to touch. Unconstrained AI 'helpfully' rewrites things that already worked.

Only edit timer.js. Don't add libraries. Don't change the HTML.

6 · The debug formula

“It's broken” gets guesses. Exact error + what you expected + what happened instead gets fixes.

I clicked Start and expected the timer to count down. Instead it shows NaN. Here's the exact error from the console: [paste]. What's the cause?

7 · Explain it back

The pattern that makes you a real builder. If you can't explain a line, you don't own it yet.

Explain what this function does line by line, like I'm seeing it for the first time.

8 · Attack your own app

Before you ship, make the AI play the villain. It will find the weird inputs you never tried.

Here's my app. What are 5 ways a user could break it? Rank them by how likely they are.

The golden rule

Never ship a line you can’t explain. The AI is your intern, not your ghostwriter — you’re the one whose name is on the app.

Put these to work: plan your build with the first-app project planner, then follow the 5-day roadmap.