100 Codex Prompts for Beginners

Codex Prompt Library

100 Codex prompts for beginners

A copyable beginner prompt library for using Codex safely. These prompts are designed to slow the work down in a good way: inspect first, explain simply, make one change at a time, verify before publishing, and avoid secrets or private data.

Start with the first 10 Browse all 100 prompts

How beginners should use Codex prompts

Do not ask Codex to change everything at once. Give it a clear goal, ask it to inspect first, and make sure you understand the plan before edits happen.

Inspect firstAsk Codex to look before editing.

One changeKeep the first version small.

Plain EnglishAsk for simple explanations.

VerifyCheck links, mobile, buttons, and errors.

No secretsDo not paste passwords, keys, or private data.

The first 10 prompts to try

If you are brand new, start with these 10. They teach Codex to orient, explain, plan, fix carefully, verify, and recommend one safe next step.

#001 Explain this project Getting oriented #002 Find the most important files Getting oriented #003 Summarize the app in plain English Getting oriented #021 Turn my request into a plan Planning changes #023 Choose the safest first change Planning changes #013 Explain this error message Understanding code #039 Fix one bug safely Fixing bugs #062 Check all links Testing and QA #070 Tell me what I should manually review Testing and QA #100 Recommend the next safe step Shipping safely

Search all 100 beginner prompts

Search prompts

Explain this project

When to use this: when you open a repo or folder for the first time

Help me with: Explain this project.

Use this when: when you open a repo or folder for the first time.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#002 Getting oriented

Find the most important files

When to use this: when you do not know where to start

Help me with: Find the most important files.

Use this when: when you do not know where to start.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#003 Getting oriented

Summarize the app in plain English

When to use this: when the project feels overwhelming

Help me with: Summarize the app in plain English.

Use this when: when the project feels overwhelming.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#004 Getting oriented

Explain how this page works

When to use this: when you are looking at one page or screen

Help me with: Explain how this page works.

Use this when: when you are looking at one page or screen.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#005 Getting oriented

Find the entry point

When to use this: when you need to know what runs first

Help me with: Find the entry point.

Use this when: when you need to know what runs first.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#006 Getting oriented

Map the folder structure

When to use this: when file names feel confusing

Help me with: Map the folder structure.

Use this when: when file names feel confusing.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#007 Getting oriented

Tell me what is safe to edit

When to use this: before touching an unfamiliar file

Help me with: Tell me what is safe to edit.

Use this when: before touching an unfamiliar file.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#008 Getting oriented

Find the build or start command

When to use this: when you need to run the project

Help me with: Find the build or start command.

Use this when: when you need to run the project.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#009 Getting oriented

Explain the tech stack

When to use this: when you see unfamiliar tools or frameworks

Help me with: Explain the tech stack.

Use this when: when you see unfamiliar tools or frameworks.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#010 Getting oriented

Create a beginner onboarding note

When to use this: when you want a simple project summary

Help me with: Create a beginner onboarding note.

Use this when: when you want a simple project summary.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#011 Understanding code

Explain this file line by line

When to use this: when a file looks intimidating

Help me with: Explain this file line by line.

Use this when: when a file looks intimidating.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#012 Understanding code

Explain this function

When to use this: when you need one block of code translated

Help me with: Explain this function.

Use this when: when you need one block of code translated.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#013 Understanding code

Explain this error message

When to use this: when an error appears in the terminal or browser

Help me with: Explain this error message.

Use this when: when an error appears in the terminal or browser.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#014 Understanding code

Explain this CSS

When to use this: when styling is confusing

Help me with: Explain this CSS.

Use this when: when styling is confusing.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#015 Understanding code

Explain this HTML structure

When to use this: when page markup is hard to read

Help me with: Explain this HTML structure.

Use this when: when page markup is hard to read.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#016 Understanding code

Explain this JavaScript behavior

When to use this: when a button, form, or interaction is unclear

Help me with: Explain this JavaScript behavior.

Use this when: when a button, form, or interaction is unclear.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#017 Understanding code

Explain this dependency

When to use this: when you see a package or plugin name

Help me with: Explain this dependency.

Use this when: when you see a package or plugin name.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#018 Understanding code

Explain this config file

When to use this: when settings are blocking progress

Help me with: Explain this config file.

Use this when: when settings are blocking progress.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#019 Understanding code

Explain what data flows where

When to use this: when you need to understand inputs and outputs

Help me with: Explain what data flows where.

Use this when: when you need to understand inputs and outputs.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#020 Understanding code

Teach me the concept behind this code

When to use this: when you want to learn, not just fix

Help me with: Teach me the concept behind this code.

Use this when: when you want to learn, not just fix.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#021 Planning changes

Turn my request into a plan

When to use this: before starting any change

Help me with: Turn my request into a plan.

Use this when: before starting any change.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#022 Planning changes

Break this task into small steps

When to use this: when the task feels too big

Help me with: Break this task into small steps.

Use this when: when the task feels too big.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#023 Planning changes

Choose the safest first change

When to use this: when there are multiple possible approaches

Help me with: Choose the safest first change.

Use this when: when there are multiple possible approaches.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#024 Planning changes

List files likely to change

When to use this: before asking Codex to edit

Help me with: List files likely to change.

Use this when: before asking Codex to edit.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#025 Planning changes

Define done-when checks

When to use this: so you know when the task is finished

Help me with: Define done-when checks.

Use this when: so you know when the task is finished.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#026 Planning changes

Write acceptance criteria

When to use this: when you want clear success conditions

Help me with: Write acceptance criteria.

Use this when: when you want clear success conditions.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#027 Planning changes

Plan a one-page feature

When to use this: for a small UI or content change

Help me with: Plan a one-page feature.

Use this when: for a small UI or content change.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#028 Planning changes

Plan a bug fix

When to use this: before debugging or editing

Help me with: Plan a bug fix.

Use this when: before debugging or editing.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#029 Planning changes

Plan a WordPress content update

When to use this: before touching a live page

Help me with: Plan a WordPress content update.

Use this when: before touching a live page.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#030 Planning changes

Explain risks before editing

When to use this: when you are worried about breaking something

Help me with: Explain risks before editing.

Use this when: when you are worried about breaking something.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#031 Fixing bugs

Reproduce this bug first

When to use this: when something is broken but unclear

Help me with: Reproduce this bug first.

Use this when: when something is broken but unclear.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#032 Fixing bugs

Find why this page looks wrong

When to use this: when layout or spacing is off

Help me with: Find why this page looks wrong.

Use this when: when layout or spacing is off.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#033 Fixing bugs

Find why this button does not work

When to use this: when a click does nothing

Help me with: Find why this button does not work.

Use this when: when a click does nothing.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#034 Fixing bugs

Find why text is hard to read

When to use this: when colors or contrast are bad

Help me with: Find why text is hard to read.

Use this when: when colors or contrast are bad.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#035 Fixing bugs

Find why a link is broken

When to use this: when a link leads nowhere

Help me with: Find why a link is broken.

Use this when: when a link leads nowhere.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#036 Fixing bugs

Find why a form fails

When to use this: when a form does not submit or save

Help me with: Find why a form fails.

Use this when: when a form does not submit or save.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#037 Fixing bugs

Find why mobile layout breaks

When to use this: when the page looks bad on a phone

Help me with: Find why mobile layout breaks.

Use this when: when the page looks bad on a phone.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#038 Fixing bugs

Find why content repeats

When to use this: when titles or sections duplicate

Help me with: Find why content repeats.

Use this when: when titles or sections duplicate.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#039 Fixing bugs

Fix one bug safely

When to use this: when you want a small focused fix

Help me with: Fix one bug safely.

Use this when: when you want a small focused fix.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#040 Fixing bugs

Explain the bug fix after editing

When to use this: when you need to understand what changed

Help me with: Explain the bug fix after editing.

Use this when: when you need to understand what changed.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#041 Building simple pages

Build a simple landing page

When to use this: when you need one clear offer page

Help me with: Build a simple landing page.

Use this when: when you need one clear offer page.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#042 Building simple pages

Build a checklist page

When to use this: when you want a useful downloadable-style resource

Help me with: Build a checklist page.

Use this when: when you want a useful downloadable-style resource.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#043 Building simple pages

Build a prompt library page

When to use this: when you want copyable prompts

Help me with: Build a prompt library page.

Use this when: when you want copyable prompts.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#044 Building simple pages

Build a simple calculator

When to use this: when you have a formula or score

Help me with: Build a simple calculator.

Use this when: when you have a formula or score.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#045 Building simple pages

Build a comparison table

When to use this: when readers need to choose between options

Help me with: Build a comparison table.

Use this when: when readers need to choose between options.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#046 Building simple pages

Build a resource directory

When to use this: when you have a list of tools or links

Help me with: Build a resource directory.

Use this when: when you have a list of tools or links.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#047 Building simple pages

Build a FAQ section

When to use this: when visitors have common questions

Help me with: Build a FAQ section.

Use this when: when visitors have common questions.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#048 Building simple pages

Build a mobile-friendly layout

When to use this: when the page must work on phones

Help me with: Build a mobile-friendly layout.

Use this when: when the page must work on phones.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#049 Building simple pages

Improve a page headline and intro

When to use this: when the page feels vague

Help me with: Improve a page headline and intro.

Use this when: when the page feels vague.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#050 Building simple pages

Make this page easier to scan

When to use this: when the content feels dense or messy

Help me with: Make this page easier to scan.

Use this when: when the content feels dense or messy.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#051 WordPress help

Inspect this WordPress page

When to use this: before editing a live page

Help me with: Inspect this WordPress page.

Use this when: before editing a live page.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#052 WordPress help

Fix visible shortcode text

When to use this: when shortcode output appears as plain text

Help me with: Fix visible shortcode text.

Use this when: when shortcode output appears as plain text.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#053 WordPress help

Add page-scoped CSS

When to use this: when one page needs a style fix

Help me with: Add page-scoped CSS.

Use this when: when one page needs a style fix.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#054 WordPress help

Find a theme CSS conflict

When to use this: when the theme overrides your colors

Help me with: Find a theme CSS conflict.

Use this when: when the theme overrides your colors.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#055 WordPress help

Make CTA buttons readable

When to use this: when button text has poor contrast

Help me with: Make CTA buttons readable.

Use this when: when button text has poor contrast.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#056 WordPress help

Check WordPress links

When to use this: after publishing or editing content

Help me with: Check WordPress links.

Use this when: after publishing or editing content.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#057 WordPress help

Create a WordPress custom HTML block

When to use this: when you need a self-contained section

Help me with: Create a WordPress custom HTML block.

Use this when: when you need a self-contained section.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#058 WordPress help

Update a page without publishing surprises

When to use this: when editing production content

Help me with: Update a page without publishing surprises.

Use this when: when editing production content.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#059 WordPress help

Explain what WordPress changed

When to use this: after an update or REST edit

Help me with: Explain what WordPress changed.

Use this when: after an update or REST edit.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#060 WordPress help

Make a rollback note

When to use this: before or after a risky WordPress change

Help me with: Make a rollback note.

Use this when: before or after a risky WordPress change.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#061 Testing and QA

Check the page loads

When to use this: after changing a page

Help me with: Check the page loads.

Use this when: after changing a page.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#062 Testing and QA

Check all links

When to use this: before publishing or sharing

Help me with: Check all links.

Use this when: before publishing or sharing.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#063 Testing and QA

Check buttons and forms

When to use this: after adding interactions

Help me with: Check buttons and forms.

Use this when: after adding interactions.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#064 Testing and QA

Check mobile layout

When to use this: before saying a page is finished

Help me with: Check mobile layout.

Use this when: before saying a page is finished.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#065 Testing and QA

Check text contrast

When to use this: when colors were changed

Help me with: Check text contrast.

Use this when: when colors were changed.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#066 Testing and QA

Check for raw code or shortcodes

When to use this: after replacing content

Help me with: Check for raw code or shortcodes.

Use this when: after replacing content.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#067 Testing and QA

Check browser console errors

When to use this: when JavaScript may be involved

Help me with: Check browser console errors.

Use this when: when JavaScript may be involved.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#068 Testing and QA

Create a simple QA checklist

When to use this: for a nontechnical review

Help me with: Create a simple QA checklist.

Use this when: for a nontechnical review.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#069 Testing and QA

Summarize what was verified

When to use this: when you need proof of work

Help me with: Summarize what was verified.

Use this when: when you need proof of work.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#070 Testing and QA

Tell me what I should manually review

When to use this: before final approval

Help me with: Tell me what I should manually review.

Use this when: before final approval.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#071 Git/GitHub basics

Explain what Git changed

When to use this: when you see a list of modified files

Help me with: Explain what Git changed.

Use this when: when you see a list of modified files.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#072 Git/GitHub basics

Summarize this diff

When to use this: before reviewing code changes

Help me with: Summarize this diff.

Use this when: before reviewing code changes.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#073 Git/GitHub basics

Tell me which files are safe to commit

When to use this: when there are unrelated edits

Help me with: Tell me which files are safe to commit.

Use this when: when there are unrelated edits.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#074 Git/GitHub basics

Write a simple commit message

When to use this: after a focused change

Help me with: Write a simple commit message.

Use this when: after a focused change.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#075 Git/GitHub basics

Explain this Git error

When to use this: when a Git command fails

Help me with: Explain this Git error.

Use this when: when a Git command fails.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#076 Git/GitHub basics

Check the current branch

When to use this: before starting work

Help me with: Check the current branch.

Use this when: before starting work.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#077 Git/GitHub basics

Explain what a pull request should say

When to use this: before opening a PR

Help me with: Explain what a pull request should say.

Use this when: before opening a PR.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#078 Git/GitHub basics

Review changes before commit

When to use this: to catch accidental edits

Help me with: Review changes before commit.

Use this when: to catch accidental edits.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#079 Git/GitHub basics

Help me avoid overwriting someone else's work

When to use this: when the worktree is dirty

Help me with: Help me avoid overwriting someone else's work.

Use this when: when the worktree is dirty.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#080 Git/GitHub basics

Explain rollback options

When to use this: when you need to undo safely

Help me with: Explain rollback options.

Use this when: when you need to undo safely.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#081 Improving prompts

Rewrite my prompt clearly

When to use this: when your first request feels vague

Help me with: Rewrite my prompt clearly.

Use this when: when your first request feels vague.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#082 Improving prompts

Add context to my prompt

When to use this: when Codex needs more background

Help me with: Add context to my prompt.

Use this when: when Codex needs more background.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#083 Improving prompts

Add constraints to my prompt

When to use this: when you want safer behavior

Help me with: Add constraints to my prompt.

Use this when: when you want safer behavior.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#084 Improving prompts

Add done-when criteria

When to use this: when you need a clear finish line

Help me with: Add done-when criteria.

Use this when: when you need a clear finish line.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#085 Improving prompts

Turn a screenshot into a prompt

When to use this: when you want a visual issue fixed

Help me with: Turn a screenshot into a prompt.

Use this when: when you want a visual issue fixed.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#086 Improving prompts

Turn feedback into an edit request

When to use this: when you want Codex to revise a page

Help me with: Turn feedback into an edit request.

Use this when: when you want Codex to revise a page.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#087 Improving prompts

Make my prompt beginner-friendly

When to use this: when the wording is too technical

Help me with: Make my prompt beginner-friendly.

Use this when: when the wording is too technical.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#088 Improving prompts

Ask me clarifying questions first

When to use this: when the task is fuzzy

Help me with: Ask me clarifying questions first.

Use this when: when the task is fuzzy.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#089 Improving prompts

Create a reusable prompt template

When to use this: when you repeat the same kind of work

Help me with: Create a reusable prompt template.

Use this when: when you repeat the same kind of work.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#090 Improving prompts

Review my prompt for risk

When to use this: before asking Codex to touch production

Help me with: Review my prompt for risk.

Use this when: before asking Codex to touch production.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#091 Shipping safely

Explain what you will change before editing

When to use this: before any production change

Help me with: Explain what you will change before editing.

Use this when: before any production change.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#092 Shipping safely

Check for risks before publishing

When to use this: when a page or feature is going live

Help me with: Check for risks before publishing.

Use this when: when a page or feature is going live.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#093 Shipping safely

Verify this page on mobile

When to use this: before final approval

Help me with: Verify this page on mobile.

Use this when: before final approval.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#094 Shipping safely

Tell me what I should manually review

When to use this: before calling the work done

Help me with: Tell me what I should manually review.

Use this when: before calling the work done.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#095 Shipping safely

Create a publish checklist

When to use this: before updating a live page

Help me with: Create a publish checklist.

Use this when: before updating a live page.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#096 Shipping safely

Create a rollback plan

When to use this: before a risky update

Help me with: Create a rollback plan.

Use this when: before a risky update.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#097 Shipping safely

Check for secrets or private data

When to use this: before sharing code or content

Help me with: Check for secrets or private data.

Use this when: before sharing code or content.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#098 Shipping safely

Check accessibility basics

When to use this: before publishing UI changes

Help me with: Check accessibility basics.

Use this when: before publishing UI changes.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#099 Shipping safely

Write a plain-English completion report

When to use this: after work is finished

Help me with: Write a plain-English completion report.

Use this when: after work is finished.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

#100 Shipping safely

Recommend the next safe step

When to use this: when you are unsure what to do next

Help me with: Recommend the next safe step.

Use this when: when you are unsure what to do next.

Please work like a beginner-friendly Codex partner:
1. Inspect first before changing anything.
2. Explain what you found in plain English.
3. Suggest one small safe next step.
4. If editing is needed, tell me exactly what you will change before you change it.
5. Make only the smallest useful change.
6. Verify the result after the change.
7. Tell me what I should manually review.

Important: do not use or expose passwords, API keys, private customer data, or secrets. If you see risk, stop and explain the safer option.

Safety prompts to remember

These safety ideas are built into the library, but they are worth repeating before any live-site or production work.

Explain what you will change before editing.
Check for risks before publishing.
Verify this page on mobile.
Tell me what I should manually review.
Check for secrets or private data before sharing anything.

When in doubt, ask Codex to inspect, explain, and suggest one safe next step before making edits.