# AI Coding Guild Prompt Library

Public copy-paste prompt library for non-software developers who want to supervise AI coding agents with smaller, safer, reviewable requests.

Prompt library URL: https://aicodingguild.com/prompts
Plain-text export: https://aicodingguild.com/prompts/txt
Prompt count: 58

## 1. What You're Actually Doing When You Build With AI
Category: Start Here — Build Safely With AI
Path: Start Here — Build Safely With AI
Lesson: https://aicodingguild.com/learn/start-here/what-you-are-actually-doing
Prompt page: https://aicodingguild.com/prompts/what-you-are-actually-doing
Estimated minutes: 9
Tags: vibe-coding, beginners, mindset, AI
Summary: A plain-English explanation of the job: AI writes fast, you still choose scope, inspect output, and own the result.

Prompt:
"I am completely new to vibe coding and I want to build one very small thing safely.
The problem is: [describe the problem]
The user is: [describe the user]
The smallest useful version would do only: [describe the tiny outcome]

Before writing any code:
1. tell me if this is a realistic first project
2. reduce the scope if it is still too big
3. explain the main risks and assumptions
4. tell me what I must review myself
5. stop before auth, payments, production data, or destructive changes unless I explicitly approve them"

## 2. Safe Beginner Loop
Category: Safety
Path: Start Here — Build Safely With AI
Lesson: https://aicodingguild.com/learn/start-here/the-safe-vibe-coding-loop
Prompt page: https://aicodingguild.com/prompts/the-safe-vibe-coding-loop
Estimated minutes: 10
Tags: vibe-coding, workflow, beginners, safety
Summary: Use this before any implementation work when you want the agent to stay scoped, explain itself, and stop after one reviewable change.

Prompt:
"I want to work in a safe beginner loop.
Please do only this one task: [describe one tiny change].

Before making changes:
1. explain your plan in plain English
2. list the files you expect to change
3. do not add packages or change config unless absolutely necessary

After making changes:
4. tell me exactly what changed
5. tell me how to test it in one minute
6. stop so I can review before the next step"

## 3. Choose a Tiny First Win
Category: Start Here — Build Safely With AI
Path: Start Here — Build Safely With AI
Lesson: https://aicodingguild.com/learn/start-here/choose-a-tiny-first-win
Prompt page: https://aicodingguild.com/prompts/choose-a-tiny-first-win
Estimated minutes: 9
Tags: beginners, scope, mvp, first-project
Summary: How to pick a first project that teaches the workflow without dragging you into complex product and engineering problems.

Prompt:
"I need help shrinking this idea into a safe first vibe-coded project.
The big idea is: [describe idea]

Reduce it to the smallest useful version by:
1. removing anything that requires auth, billing, production data, or complicated integrations
2. keeping only one user and one core job to be done
3. telling me what the first screen or flow should be
4. telling me what to deliberately postpone until later

I want a first win, not a platform."

## 4. Don't Lose Your Work — Folders, Git, and Checkpoints
Category: Start Here — Build Safely With AI
Path: Start Here — Build Safely With AI
Lesson: https://aicodingguild.com/learn/start-here/dont-lose-your-work
Prompt page: https://aicodingguild.com/prompts/dont-lose-your-work
Estimated minutes: 10
Tags: git, beginners, safety, workflow
Summary: The minimum safe setup for total beginners: a real project folder, a Git repo, a remote backup, and repeatable checkpoints.

Prompt:
"I am a beginner and I want the safest possible project setup before I keep building.
Help me:
1. confirm this project has the minimum Git safety setup
2. check that `.env`-style secret files are ignored
3. tell me what files should and should not be committed right now
4. suggest the next safe checkpoint

Do not rewrite history, force push, or delete files unless I explicitly approve it."

## 5. Your First Agent Session
Category: Start Here — Build Safely With AI
Path: Start Here — Build Safely With AI
Lesson: https://aicodingguild.com/learn/start-here/your-first-agent-session
Prompt page: https://aicodingguild.com/prompts/your-first-agent-session
Estimated minutes: 11
Tags: AI-tools, beginners, agent-workflow, hands-on
Summary: How to run a first real AI-assisted build session without letting it spiral into a mystery code dump.

Prompt:
"I am on my first real vibe-coding session.
Project: [describe project]
Current goal: [describe one small feature]

Before changing code:
1. explain the safest approach in plain English
2. list the files you expect to change
3. tell me if this request is still too big

Then implement only that one small feature.

Afterward:
4. tell me exactly what changed
5. tell me how to test it in under two minutes
6. stop so I can review before the next step

Do not add auth, deployment, payments, or unrelated cleanup."

## 6. Pre-Flight Secrets Check
Category: Secrets Hygiene
Path: Start Here — Build Safely With AI
Lesson: https://aicodingguild.com/learn/start-here/before-you-share-anything
Prompt page: https://aicodingguild.com/prompts/before-you-share-anything
Estimated minutes: 10
Tags: beginners, safety, sharing, shipping
Summary: 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.

Prompt:
"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]
- main flow: [describe flow]

Review it for:
1. obvious safety problems
2. anything sensitive I should not expose yet
3. the most likely embarrassing failure points
4. the smallest fixes that would make it safer to share

Do not suggest major rewrites. I want a practical pre-share checklist."

## 7. What AI-Assisted Building Changed — And Why It Matters
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/what-is-vibe-coding
Prompt page: https://aicodingguild.com/prompts/what-is-vibe-coding
Estimated minutes: 8
Tags: vibe-coding, AI, beginners, overview
Summary: Zoom out from the beginner workflow and understand why AI changed who gets to build software, what that unlocks, and what it does not.

Prompt:
"I want to use vibe coding to build a small product.
I already understand the beginner safety loop.
Help me think about the bigger picture.

The problem space I care about is: [describe it]
The user is: [describe the person]
The kind of product I imagine is: [describe it]

Before writing code:
1. explain why vibe coding changes who can build in this space
2. tell me what human judgment is still required
3. tell me where AI will create false confidence
4. suggest the next foundational topic I should understand before going bigger"

## 8. Pick The Right Tool
Category: Tool Choice
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/the-vibe-coders-toolkit
Prompt page: https://aicodingguild.com/prompts/the-vibe-coders-toolkit
Estimated minutes: 10
Tags: tools, cursor, bolt, replit, v0, lovable
Summary: Use this when you are about to start a project and need a recommendation on which AI coding tool matches your experience and constraints.

Prompt:
"I need help choosing the right vibe-coding tool for this stage.
My project is: [describe it]
My experience level is: [describe it]
I care most about: [speed, control, design, collaboration, privacy]

Recommend the best starting tool, one backup tool for later, and the main tradeoffs I should know before I begin."

## 9. What You Can Build Next — And What Should Wait
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/what-you-can-build-today
Prompt page: https://aicodingguild.com/prompts/what-you-can-build-today
Estimated minutes: 8
Tags: inspiration, projects, examples, beginners
Summary: A realistic map of what AI-assisted builders can build now, what makes sense after your first tiny win, and what should still wait.

Prompt:
"Help me choose the right next project category.
I have already completed a tiny first win.
Now I want to map what kind of project makes sense next.

My idea is: [describe it]

Place this idea in one of three buckets:
1. realistic now
2. realistic next after more practice
3. not realistic yet

Then explain the safest product shape for the current stage and the main reason not to jump ahead."

## 10. The Honest Truth — What AI Can and Cannot Do For You
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/the-honest-truth
Prompt page: https://aicodingguild.com/prompts/the-honest-truth
Estimated minutes: 10
Tags: expectations, limitations, AI, reality-check
Summary: A stage-two reality check: where AI genuinely accelerates you, where it creates false confidence, and what breaks as scope grows.

Prompt:
"Critique this project plan honestly.
This is no longer my first tiny experiment.
I want to understand where the current workflow will break as the project grows.

I want you to identify:
1. where AI will probably help
2. where AI is likely to create false confidence
3. the biggest risks around testing, security, maintainability, and feature creep
4. what I need to review manually before I trust the output

Do not reassure me. Be specific."

## 11. Your Next 24 Hours — Turn One Tiny Win Into a Repeatable Practice
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/your-first-24-hours
Prompt page: https://aicodingguild.com/prompts/your-first-24-hours
Estimated minutes: 12
Tags: workflow, hands-on, practice, iteration
Summary: A plan for the day after your first tiny build: stabilize it, understand it, improve it, and turn a lucky win into a reliable workflow.

Prompt:
"Help me turn my first tiny vibe-coded project into a repeatable practice project.
The app currently does: [describe it]
The current weak point is: [describe it]
My available time is: [time]

Give me a concrete plan for:
1. auditing what I already have
2. choosing one improvement that increases quality without exploding scope
3. testing that improvement
4. checkpointing safely
5. identifying the next concept I should learn on purpose

Do not suggest auth, billing, or major new features."

## 12. Frontend vs Backend — What's the Difference and Why Does It Matter?
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/frontend-vs-backend
Prompt page: https://aicodingguild.com/prompts/frontend-vs-backend
Estimated minutes: 8
Tags: frontend, backend, architecture, fundamentals
Summary: Understand the two halves of every web application using a restaurant analogy that makes it click.

Prompt:
"Before implementing this feature, split the work into frontend and backend responsibilities.
1. Explain what the user sees and interacts with
2. Explain what the server must handle behind the scenes
3. List the files or systems likely to change on each side
4. Call out any data that must never live in the frontend
5. Stop before changing auth, permissions, or the data model without my approval

I want a clean boundary, not a blurry full-stack mess."

## 13. What Happens When You Type a URL — The Journey of a Web Request
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/what-happens-when-you-type-a-url
Prompt page: https://aicodingguild.com/prompts/what-happens-when-you-type-a-url
Estimated minutes: 9
Tags: web-requests, DNS, HTTP, networking, fundamentals
Summary: Follow a web request from your browser to a server and back — the complete journey explained simply.

Prompt:
"Help me trace this page load like a web request investigator.
1. Explain the request path from URL to rendered page
2. Tell me which stages are DNS, network, server processing, and browser rendering
3. Based on this symptom, identify the most likely failing stage
4. Tell me what I should inspect in DevTools or logs to confirm it
5. Do not jump to code changes before explaining the likely bottleneck

Symptom: [describe the bug or slowdown]."

## 14. What is a Server? Cloud, Hosting, and Where Your Code Lives
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/what-is-a-server
Prompt page: https://aicodingguild.com/prompts/what-is-a-server
Estimated minutes: 8
Tags: servers, cloud, hosting, infrastructure, fundamentals
Summary: Demystifying servers, cloud hosting, and serverless — understand where your app actually runs.

Prompt:
"Help me choose the safest hosting model for this project.
1. Explain whether this app should use static hosting, managed platform hosting, or serverless functions
2. Tell me what parts of the app run where
3. List the operational tradeoffs: logs, scaling, cold starts, cost, and simplicity
4. Tell me which environment variables or secrets must be configured
5. Stop before making infra, billing, or region changes without my approval

Optimize for low operational burden and easy rollback."

## 15. What is an API? The Bridges Between Software Systems
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/what-is-an-api
Prompt page: https://aicodingguild.com/prompts/what-is-an-api
Estimated minutes: 9
Tags: APIs, REST, integrations, fundamentals
Summary: Understand APIs through a simple analogy — the waiter between your app and the data it needs.

Prompt:
"Help me integrate this API like a cautious engineer.
1. Explain the API contract in plain English
2. List the request shape, response shape, auth method, and rate-limit risks
3. Tell me where the secret should live and how to keep it out of the frontend
4. Include failure handling for bad responses, timeouts, and retries
5. Stop before adding credentials or billing-connected integrations without my approval

Optimize for a stable integration, not just a demo that works once."

## 16. What is a Database? Where Your Data Lives and Why It Matters
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/what-is-a-database
Prompt page: https://aicodingguild.com/prompts/what-is-a-database
Estimated minutes: 9
Tags: databases, SQL, NoSQL, data, fundamentals
Summary: Understand databases through the spreadsheet analogy — SQL vs NoSQL, when you need one, and which to choose.

Prompt:
"Help me design the smallest safe database model for this feature.
1. List the tables or collections I actually need
2. Show the key fields and relationships
3. Explain whether SQL or NoSQL makes more sense here and why
4. Call out ownership, validation, and deletion risks
5. Stop before running migrations, destructive schema changes, or data backfills without my approval

Optimize for clear data modeling and easy future maintenance."

## 17. Programming Languages — Which Ones Exist and Why There Are So Many
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/programming-languages-overview
Prompt page: https://aicodingguild.com/prompts/programming-languages-overview
Estimated minutes: 8
Tags: programming-languages, overview, fundamentals
Summary: A friendly tour of the programming language landscape — why so many exist and which ones matter for AI-assisted builders.

Prompt:
"Help me understand the language choices in this project before we change anything.
1. List the languages involved and what role each one plays
2. Tell me which languages I actually need to recognize as the human reviewer
3. Explain whether the current choices are conventional or unusual
4. Warn me if switching languages would create more churn than value
5. Do not recommend a rewrite unless there is a concrete business reason

Optimize for clarity and maintainability, not language hype."

## 18. JavaScript and TypeScript — The Language of the Web
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/javascript-and-typescript
Prompt page: https://aicodingguild.com/prompts/javascript-and-typescript
Estimated minutes: 9
Tags: javascript, typescript, web-development, fundamentals
Summary: What JavaScript does, why TypeScript exists, and where you'll see them in every web project you build.

Prompt:
"Explain this JavaScript or TypeScript file to me before changing it.
1. Tell me what runs in the browser and what runs on the server
2. Explain any important types, props, or return values
3. Tell me what TypeScript is protecting me from in this file
4. Point out the highest-risk area for silent bugs
5. Stop before converting between JavaScript and TypeScript unless there is a strong reason

I want clarity about behavior and data shape, not just a summary."

## 19. HTML and CSS — The Building Blocks Every Builder Should Recognize
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/html-and-css
Prompt page: https://aicodingguild.com/prompts/html-and-css
Estimated minutes: 8
Tags: HTML, CSS, web-development, styling, fundamentals
Summary: Understand how HTML provides structure and CSS provides style — the visual foundation of every web page.

Prompt:
"Help me make this UI change without breaking structure or accessibility.
1. Explain the current HTML structure in plain English
2. Tell me which styles are controlling layout, spacing, and typography
3. Suggest the smallest set of markup or class changes needed
4. Preserve semantics, accessibility, and mobile responsiveness
5. Stop before a style request turns into a wholesale component rewrite

I want a precise UI edit, not generic beautification."

## 20. Python — The Swiss Army Knife (and When to Reach for It)
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/python
Prompt page: https://aicodingguild.com/prompts/python
Estimated minutes: 8
Tags: python, AI, data-science, scripting, fundamentals
Summary: Understand Python's strengths in AI, data, and scripting — and know when to use it versus JavaScript.

Prompt:
"Help me decide whether this task should use Python or stay in my existing stack.
1. Explain why Python would or would not be a better fit
2. Show the smallest Python example that solves the task
3. Explain the script line by line in plain English
4. Tell me what dependencies and runtime setup it requires
5. Stop before introducing a separate Python service unless the use case truly justifies it

Optimize for the simplest maintainable solution."

## 21. Reading Code You Didn't Write — The Skill AI Can't Replace
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/reading-code-you-didnt-write
Prompt page: https://aicodingguild.com/prompts/reading-code-you-didnt-write
Estimated minutes: 10
Tags: code-reading, debugging, skills, fundamentals
Summary: Learn how to read and understand AI-generated code — patterns to recognize, questions to ask, and how to use AI to explain itself.

Prompt:
"Explain this code so I can review it like an owner, not a spectator.
1. Tell me what this file is responsible for
2. Point out the key names, branches, and data flow
3. Identify the highest-risk logic, permission check, or side effect
4. Tell me what could go wrong in production
5. Keep the explanation anchored to the actual code, not a generic summary

Here is the file or diff: [paste code or change]."

## 22. What is Git? Source Control Explained for Non-Developers
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/what-is-git
Prompt page: https://aicodingguild.com/prompts/what-is-git
Estimated minutes: 9
Tags: git, version-control, source-control, fundamentals
Summary: Go deeper than 'don't lose your work' and understand commits, branches, merges, and recovery without developer jargon.

Prompt:
"Help me use Git safely on this project.
1. Explain the safest workflow for the change I want to make
2. Tell me whether this should happen on a new branch or not
3. List the Git commands I should expect to run and what each one does
4. Tell me what a good commit message would look like
5. Stop before any destructive Git command or history rewrite

Assume I am new to Git and optimize for recoverability, not cleverness."

## 23. What is GitHub? Your Code's Home on the Internet
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/what-is-github
Prompt page: https://aicodingguild.com/prompts/what-is-github
Estimated minutes: 8
Tags: github, repositories, collaboration, fundamentals
Summary: Understand GitHub, repositories, and collaboration — and why every builder using AI needs it.

Prompt:
"Help me set up and use GitHub safely for this project.
1. Explain the role GitHub should play in my workflow
2. Tell me whether this repo should be public or private and why
3. List the integrations I should expect with deployment, CI, and AI tools
4. Recommend the safest first workflow for branches and pull requests
5. Stop before changing repo visibility, secrets, or deployment permissions

Optimize for a solo builder who still wants a professional workflow."

## 24. What is a Terminal? The Command Line Isn't Scary
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/what-is-a-terminal
Prompt page: https://aicodingguild.com/prompts/what-is-a-terminal
Estimated minutes: 9
Tags: terminal, command-line, CLI, fundamentals
Summary: Demystify the terminal — what it is, why developers love it, and five commands to get you started.

Prompt:
"Explain the terminal commands I need for this task before I run anything.
1. Tell me which directory I should be in first
2. Show the exact command
3. Explain each part of the command in plain English
4. Tell me what output I should expect if it succeeds
5. Warn me if the command is destructive or changes files

Assume I am comfortable running safe commands but I do not want surprise side effects."

## 25. What is VS Code? The Editor Behind Cursor (and Why It Matters)
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/what-is-vs-code
Prompt page: https://aicodingguild.com/prompts/what-is-vs-code
Estimated minutes: 8
Tags: vs-code, cursor, code-editor, tools
Summary: Understand VS Code — the world's most popular code editor, the foundation of Cursor, and your future daily tool.

Prompt:
"Help me set up a practical Cursor or VS Code workflow for this project.
1. Recommend the minimum editor features and extensions I should rely on
2. Tell me which shortcuts matter most for daily work
3. Explain how file navigation, terminal use, and source control fit together
4. Tell me what should stay simple instead of over-customized
5. Stop before installing a long list of extensions or changing project tooling

Optimize for a beginner who wants a calm, maintainable setup."

## 26. What is npm? Package Managers and Why They Exist
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/what-is-npm
Prompt page: https://aicodingguild.com/prompts/what-is-npm
Estimated minutes: 9
Tags: npm, packages, dependencies, node-modules, fundamentals
Summary: Understand packages, dependencies, package.json, and node_modules — the supply chain of modern software.

Prompt:
"Help me make a safe package-manager decision for this project.
1. Tell me which package manager this repo is already using and how you know
2. Explain whether I need a new dependency or can use what is already installed
3. If a new package is justified, tell me the tradeoffs and maintenance risk
4. List the exact install and verification steps
5. Stop before switching package managers or adding a dependency just for convenience

Optimize for fewer dependencies, predictable installs, and easy rollback."

## 27. The MVP Mindset — Build Less, Learn More
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/the-mvp-mindset
Prompt page: https://aicodingguild.com/prompts/the-mvp-mindset
Estimated minutes: 9
Tags: MVP, product, strategy, mindset
Summary: Understand what an MVP really is, why it matters, and the common mistakes that trap first-time builders.

Prompt:
"Help me reduce this idea to an MVP.
The user is: [describe person]
The problem is: [describe one problem]
My current feature list is: [list features]

Cut this down to the smallest version that delivers real value.
Tell me which three features stay in the MVP, which features move to later, and why."

## 28. Validating Your Idea Before Writing Code
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/validating-your-idea
Prompt page: https://aicodingguild.com/prompts/validating-your-idea
Estimated minutes: 10
Tags: validation, product, strategy, user-research
Summary: Learn proven techniques to test whether people actually want what you're building — before you invest time building it.

Prompt:
"Help me validate this idea before I build it.
Idea: [describe it]
Target user: [describe them]
What I think the problem is: [describe it]

Give me:
1. the fastest validation tests I can run
2. the questions I should ask users
3. what evidence would be weak, medium, or strong validation
4. what would convince me to stop or narrow the idea"

## 29. Choosing Your Tech Stack — A Decision Framework
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/choosing-your-tech-stack
Prompt page: https://aicodingguild.com/prompts/choosing-your-tech-stack
Estimated minutes: 9
Tags: tech-stack, architecture, decisions, tools
Summary: A practical framework for choosing the right tools and technologies for your project — with sensible defaults for AI-assisted builders.

Prompt:
"Recommend a tech stack for this project.
Project type: [describe it]
Constraints: [budget, hosting, mobile, data, auth, payments, privacy]
My experience level: [describe it]

Give me:
1. the default stack you recommend
2. why each tool is a good fit
3. which choices are boring and proven
4. which parts I should avoid over-optimizing right now"

## 30. The 1-Week MVP Sprint — A Realistic Plan
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/one-week-mvp-sprint
Prompt page: https://aicodingguild.com/prompts/one-week-mvp-sprint
Estimated minutes: 12
Tags: MVP, sprint, shipping, project-planning, hands-on
Summary: A day-by-day plan for building and shipping your first product in one week — practical, focused, and achievable.

Prompt:
"Turn this product idea into a one-week MVP sprint.
Project: [describe it]
Available time per day: [time]
Must-have features: [list them]

Give me a realistic day-by-day plan for:
1. setup
2. first feature
3. second feature
4. polish and fixes
5. deployment and feedback

Also tell me what to cut first if the schedule slips."

## 31. Java — The Enterprise Workhorse
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/java-enterprise
Prompt page: https://aicodingguild.com/prompts/java-enterprise
Estimated minutes: 13
Tags: java, spring-boot, jvm, enterprise, programming-languages
Summary: Understand where Java lives in the modern tech landscape — Spring Boot, the JVM ecosystem, and why enterprises run on it.

Prompt:
"Explain this Java or Spring Boot example in terms I can use as a JavaScript or TypeScript developer.
1. Tell me what the code is doing conceptually
2. Map the Java concepts to familiar web concepts in my stack
3. Point out the route, validation, service, and persistence layers
4. Tell me what assumptions an enterprise team is optimizing for here
5. Do not focus on syntax trivia until the architecture is clear

Here is the Java example: [paste code or docs]."

## 32. C# and .NET — Microsoft's Full Stack
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/csharp-dotnet
Prompt page: https://aicodingguild.com/prompts/csharp-dotnet
Estimated minutes: 13
Tags: csharp, dotnet, aspnet, blazor, microsoft, enterprise
Summary: Explore the .NET ecosystem — ASP.NET, Blazor, Azure integration, and why C# powers so many enterprise applications.

Prompt:
"Translate this .NET example into the web concepts I already know.
1. Explain what part is the language, what part is the framework, and what part is the cloud platform
2. Map the route, data access, auth, and deployment concepts to a JavaScript stack
3. Tell me whether this is modern .NET or old .NET Framework
4. Highlight any Microsoft-specific assumptions, especially Azure or enterprise identity
5. Stop before recommending a stack switch unless there is a compelling business reason

Here is the code or documentation: [paste it]."

## 33. Python Beyond AI — Django, Flask, and FastAPI
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/python-beyond-ai
Prompt page: https://aicodingguild.com/prompts/python-beyond-ai
Estimated minutes: 13
Tags: python, django, flask, fastapi, web-development, scripting
Summary: Discover Python's world beyond machine learning — web frameworks, data engineering, scripting, and why Python is the Swiss Army knife of programming.

Prompt:
"Help me evaluate this Python approach beyond the AI hype.
1. Explain whether this task is better suited to Django, Flask, FastAPI, or no Python web framework at all
2. Show me the smallest maintainable implementation
3. Translate the important parts into concepts I already know from JavaScript
4. Tell me what environment and dependency management it requires
5. Stop before introducing a separate Python service if the same job fits cleanly in my current stack

Optimize for fit, not for adding technology for its own sake."

## 34. Go — The Cloud Native Language
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/go-cloud-native
Prompt page: https://aicodingguild.com/prompts/go-cloud-native
Estimated minutes: 12
Tags: go, golang, cloud-native, kubernetes, docker, concurrency
Summary: Understand Go's role in modern infrastructure — simplicity, concurrency, its connection to Docker and Kubernetes, and why it's the language of cloud tooling.

Prompt:
"Help me decide whether Go is the right tool for this service or utility.
1. Explain why Go is or is not a better fit than Node.js for this job
2. Map goroutines, packages, binaries, and error handling to concepts I already know
3. Show me the smallest realistic Go example
4. Tell me what deployment and operational advantages I actually gain
5. Stop before recommending Go just because it is fashionable in infrastructure circles

Optimize for operational simplicity and distribution, not novelty."

## 35. PHP — Still Running the Internet
Category: Foundations for AI-Assisted Builders
Path: Foundations for AI-Assisted Builders
Lesson: https://aicodingguild.com/learn/foundations/php-still-running
Prompt page: https://aicodingguild.com/prompts/php-still-running
Estimated minutes: 12
Tags: php, wordpress, laravel, legacy, web-development
Summary: Learn why PHP powers 40% of the web — WordPress, Laravel, and the legacy codebase reality that every developer should understand.

Prompt:
"Help me understand this PHP or WordPress system pragmatically.
1. Tell me whether I am looking at Laravel, WordPress, or custom legacy PHP
2. Explain the overall architecture and where I should start reading
3. Map the main concepts to frameworks and tools I already know
4. Call out version, plugin, security, and maintenance risks
5. Stop before recommending a rewrite unless the current system is truly unsafe or unmaintainable

Optimize for realistic maintenance and integration decisions."

## 36. The AI Coding Tool Landscape
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/ai-coding-tool-landscape
Prompt page: https://aicodingguild.com/prompts/ai-coding-tool-landscape
Estimated minutes: 12
Tags: ai-tools, cursor, bolt, replit, v0, lovable, comparison
Summary: Cursor, Bolt, Replit, v0, Lovable compared — which tool fits your workflow?

Prompt:
"Help me choose the right AI coding tool for this project.
Project type: [describe it]
Current stage: [prototype, feature build, maintenance, refactor]
My skill level: [describe honestly]
Constraints: [privacy, deployment target, code ownership, budget]

Recommend:
1. the best primary tool
2. one secondary tool if the project grows
3. the tradeoffs of each
4. the handoff point where I should switch tools instead of forcing one tool to do everything"

## 37. Cursor — The Power User's Choice (Setup and First Steps)
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/cursor-setup
Prompt page: https://aicodingguild.com/prompts/cursor-setup
Estimated minutes: 15
Tags: ai-tools, cursor, setup, editor
Summary: Install Cursor, configure it for vibe coding, and build your first project with AI assistance.

Prompt:
Help me set up Cursor for this project in a safe way.
First, explain whether this task should use chat, inline edit, or Composer.
Then propose a short `.cursorrules` file based on this stack and these constraints:
- [stack]
- [current files or feature area]
- no new dependencies without asking
- stop before auth, schema, billing, or infra changes
After that, help me make one small reviewable change and tell me exactly what I must inspect before I accept it.

## 38. Bolt.new and Lovable — Instant Full-Stack Apps
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/bolt-and-lovable
Prompt page: https://aicodingguild.com/prompts/bolt-and-lovable
Estimated minutes: 12
Tags: ai-tools, bolt, lovable, prototyping, full-stack
Summary: Build complete web applications from a text prompt with Bolt.new and Lovable.

Prompt:
"I want to prototype this app in Bolt or Lovable.
App idea: [describe it]
Must-have flow: [describe it]
Data fields: [list them]
Visual direction: [describe it]
Constraints: [auth, payments, storage, deployment, handoff plan]

Recommend whether Bolt or Lovable is the better starting point and give me a prompt that is specific enough to produce a usable first prototype."

## 39. Replit — Code, Deploy, and Collaborate in Your Browser
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/replit
Prompt page: https://aicodingguild.com/prompts/replit
Estimated minutes: 12
Tags: ai-tools, replit, browser-ide, deployment, collaboration
Summary: Use Replit for browser-based development, instant deployment, and real-time collaboration.

Prompt:
"I want to use Replit for this project.
Goal: [learning, prototype, collaboration]
App idea: [describe it]
Constraints: [no local setup, shareable URL, collaboration, budget]

Tell me:
1. whether Replit is the right tool
2. which template I should start from
3. what I should keep simple to stay inside Replit's strengths
4. when I should export the code and move to a different environment"

## 40. v0 by Vercel — UI Components From a Text Prompt
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/v0-by-vercel
Prompt page: https://aicodingguild.com/prompts/v0-by-vercel
Estimated minutes: 10
Tags: ai-tools, v0, vercel, ui-components, design
Summary: Generate production-ready UI components with v0 and integrate them into your projects.

Prompt:
"I want v0 to generate a React component for this screen:
[describe the UI, data fields, visual style, empty state, loading state, and mobile behavior]

The component must:
1. work in a Next.js + Tailwind project
2. be easy to wire to real data later
3. avoid making up backend logic
4. call out any shadcn/ui dependencies it expects"

## 41. Claude Code — When You Want AI in Your Terminal
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/claude-code
Prompt page: https://aicodingguild.com/prompts/claude-code
Estimated minutes: 12
Tags: ai-tools, claude-code, terminal, anthropic, advanced
Summary: Use Claude Code for terminal-based AI development with deep codebase understanding.

Prompt:
"I'm using Claude Code on this project.
First, read the codebase and summarize:
1. what the app does
2. how the architecture is organized
3. the risky areas to avoid touching casually

Then propose a `CLAUDE.md` file and a safe plan for this change: [describe change].
Do not modify [list protected areas] without asking first."

## 42. GitHub Copilot — The AI That Lives in Your Editor
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/github-copilot
Prompt page: https://aicodingguild.com/prompts/github-copilot
Estimated minutes: 10
Tags: ai-tools, github-copilot, vs-code, code-completion
Summary: Set up GitHub Copilot for inline code completions and AI-assisted development in VS Code.

Prompt:
"I'm using GitHub Copilot in VS Code.
Help me get better suggestions for this task: [describe task].
Tell me:
1. what comments or function names I should write first
2. which related files I should open for context
3. when Copilot is likely enough and when I should switch to a stronger multi-file tool
4. what I must review manually before I accept a suggestion"

## 43. Tighten My Coding Prompt
Category: Prompt Design
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/anatomy-of-good-coding-prompt
Prompt page: https://aicodingguild.com/prompts/anatomy-of-good-coding-prompt
Estimated minutes: 12
Tags: ai-tools, prompt-engineering, best-practices
Summary: Use this when your current request feels vague and you want the agent to help shape a safer, sharper implementation prompt before files change.

Prompt:
**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]

Rewrite it using these sections:
1. Context
2. Task
3. Specifics
4. Constraints
5. Output

Keep the scope limited to one reviewable change.
Tell me which assumptions are still missing.
Tell me what I must verify manually before I let an agent write code."

## 44. System Prompts — .cursorrules and CLAUDE.md Explained
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/system-prompts
Prompt page: https://aicodingguild.com/prompts/system-prompts
Estimated minutes: 12
Tags: ai-tools, system-prompts, cursorrules, claude-md, configuration
Summary: Write system prompts that give AI persistent context about your project and preferences.

Prompt:
**Use this when you want the agent to draft your persistent project instructions:**
"Help me write a system prompt file for this project.
Tool target: [Cursor / Claude Code / both]
Project summary: [what the app does]
Stack: [frameworks, languages, key services]
Repo conventions: [folders, naming, testing, styling, data access]
Constraints: [things the agent must never do]
Current phase: [what is already built and what is in progress]

Return:
1. A concise `.cursorrules` or `CLAUDE.md`
2. A short list of rules I should not include because they are too vague, too stale, or too noisy
3. A maintenance checklist for keeping this file current as the project changes."

## 45. Breaking Big Ideas into Small Tasks — The Decomposition Pattern
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/decomposition-pattern
Prompt page: https://aicodingguild.com/prompts/decomposition-pattern
Estimated minutes: 12
Tags: ai-tools, prompt-engineering, decomposition, workflow
Summary: Learn why small, focused prompts produce better code than trying to build everything at once.

Prompt:
**Use this before you start building a multi-part feature:**
"I want to build [feature or app idea]. Break it into 8-12 implementation steps.

Requirements for each step:
- It must build on the previous step
- It must produce something testable
- It must avoid mixing auth, billing, schema, and UI redesign into one step
- It must name the files or systems likely to change
- It must include a short verification check before the next step

Start with foundations first.
Tell me which steps need my approval before an agent should continue."

## 46. Few-Shot Prompting — Teaching AI by Showing Examples
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/few-shot-prompting
Prompt page: https://aicodingguild.com/prompts/few-shot-prompting
Estimated minutes: 10
Tags: ai-tools, prompt-engineering, few-shot, examples
Summary: Use examples to teach AI your patterns, styles, and conventions before it writes new code.

Prompt:
**Use this when you want the agent to follow an existing pattern instead of inventing one:**
"I need a new [component / route / hook / migration].
Use these files as examples:
- [file 1]
- [file 2]

Replicate these aspects:
- [imports and file structure]
- [error handling pattern]
- [response shape or UI composition]

Adapt these aspects for the new task:
- [field names]
- [queries]
- [business logic]

Before coding, summarize the pattern you see.
Call out any inconsistencies between the examples.
Stop if the examples appear outdated or conflict with the rest of the repo."

## 47. Chain-of-Thought — Making AI Think Step by Step
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/chain-of-thought
Prompt page: https://aicodingguild.com/prompts/chain-of-thought
Estimated minutes: 10
Tags: ai-tools, prompt-engineering, chain-of-thought, reasoning
Summary: Use chain-of-thought prompting to get AI to reason through complex coding problems.

Prompt:
**Use this for tasks with real logic, architecture, or debugging complexity:**
"I need help with [problem].
Before writing code, work in three phases.

Phase 1: Think
- Explain the problem in plain English
- Identify the main rules, dependencies, and edge cases
- Point out anything ambiguous or risky

Phase 2: Plan
- Propose the implementation approach
- List files or systems likely to change
- Explain how you will verify correctness

Phase 3: Code
- Do not start this phase until I approve phases 1 and 2

Keep these constraints in mind: [constraints].
Tell me what I must test manually after implementation."

## 48. The Anti-Patterns — Prompts That Produce Bad Code
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/anti-patterns
Prompt page: https://aicodingguild.com/prompts/anti-patterns
Estimated minutes: 12
Tags: ai-tools, prompt-engineering, anti-patterns, mistakes
Summary: Recognize and avoid the most common prompting mistakes that lead to buggy, bloated, or wrong code.

Prompt:
**Use this when a conversation with the agent keeps going sideways:**
"I am going to paste three prompts that produced bad results.
For each prompt:
1. Classify the anti-pattern causing the failure
2. Explain why the prompt created bad code or bad direction
3. Rewrite it into a safer, more specific prompt
4. Add the right constraints, review gates, and stop conditions

Use these anti-pattern labels when relevant:
mega prompt, vague request, implicit standards, error dump,
moving target, trust fall, kitchen sink, outdated assumption.

After the rewrites, give me one reusable rule I should add to my workflow so I stop making the same mistake."

## 49. The Build-Review-Iterate Loop
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/build-review-iterate
Prompt page: https://aicodingguild.com/prompts/build-review-iterate
Estimated minutes: 12
Tags: ai-tools, workflows, vibe-coding, iteration
Summary: Master the core vibe coding workflow — generate code, review it critically, and iterate toward your goal.

Prompt:
"I want to work in a build-review-iterate loop for this feature.
Start with the smallest reviewable slice that proves the approach.
After you propose or implement that slice, stop and show me:
1. what you changed
2. what assumptions you made
3. what could still go wrong
4. what the next iteration should focus on

Keep each iteration scoped to one to three concrete changes.
If we pass five iterations on one feature, tell me to step back and reassess instead of patching blindly."

## 50. Review The Diff
Category: Review
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/code-review-with-ai
Prompt page: https://aicodingguild.com/prompts/code-review-with-ai
Estimated minutes: 12
Tags: ai-tools, workflows, code-review, quality
Summary: Use this after an AI-generated change lands so the reviewer focuses on correctness, security, edge cases, and misleading tests.

Prompt:
"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 section
4. suggest a concrete fix

Prioritize bugs, security issues, missing edge cases, and misleading tests.
Do not waste time on style commentary unless it affects correctness or maintainability."

## 51. Debug This Without Thrashing
Category: Debugging
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/debugging-with-ai
Prompt page: https://aicodingguild.com/prompts/debugging-with-ai
Estimated minutes: 12
Tags: ai-tools, workflows, debugging, troubleshooting
Summary: Use this when the app is already broken and you need the agent to isolate one likely cause, propose a narrow fix, and define how to verify it.

Prompt:
"Help me debug this issue systematically.
Feature: [what is broken]
Error or symptom: [full message or precise symptom]
Expected behavior: [what should happen]
Actual behavior: [what happens instead]
Steps to reproduce: [exact steps]
Relevant code: [paste code]
What I've already tried: [list]

First tell me the likely root causes in order.
Then give me the smallest fix to test first.
After that, tell me how I should verify the fix and what related areas I should retest."

## 52. Refactoring With AI — Making Code Better Without Breaking It
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/refactoring-with-ai
Prompt page: https://aicodingguild.com/prompts/refactoring-with-ai
Estimated minutes: 12
Tags: ai-tools, workflows, refactoring, code-quality
Summary: Use AI to safely improve, reorganize, and simplify existing code without changing what it does.

Prompt:
"Help me refactor this code without changing behavior.
First explain what the current code does and what parts are risky to change.
Then propose the smallest valuable refactoring step.
For that step, show me:
1. the files involved
2. what behavior must stay the same
3. what tests or manual checks should prove we did not break anything

Do not mix new features into this refactor.
If the refactor is too large, split it into reviewable phases."

## 53. When to Stop Prompting and Start Reading
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/when-to-stop-prompting
Prompt page: https://aicodingguild.com/prompts/when-to-stop-prompting
Estimated minutes: 10
Tags: ai-tools, workflows, learning, understanding
Summary: Recognize when AI stops helping and learn when reading code yourself is the faster path forward.

Prompt:
"Do not suggest code changes yet.
Help me understand this flow first.
Walk me through what happens from [user action] to [visible result].
Reference the key files, functions, and state changes in order.
Then tell me:
1. which part I seem not to understand yet
2. what questions I should answer before prompting for a fix
3. whether the better next move is explanation, debugging, refactoring, or a new implementation prompt"

## 54. How LLMs Actually Work — For Non-ML People
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/how-llms-work
Prompt page: https://aicodingguild.com/prompts/how-llms-work
Estimated minutes: 14
Tags: llm, tokens, context-window, attention, temperature, ai-fundamentals
Summary: Understand tokens, context windows, attention, and temperature without a single equation.

Prompt:
"Explain this model behavior in practical coding terms:
- why the output changed between runs
- why context seems to fade in a long conversation
- how I should structure prompts for better focus

Use tokens, context windows, attention, and temperature in the explanation, but keep it tied to real development workflows."

## 55. OpenAI vs Anthropic vs Open Source — An Honest Comparison
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/openai-vs-anthropic-vs-open-source
Prompt page: https://aicodingguild.com/prompts/openai-vs-anthropic-vs-open-source
Estimated minutes: 15
Tags: openai, anthropic, open-source, llama, comparison, ai-models
Summary: Compare the major AI model providers — strengths, weaknesses, pricing, and when to use which.

Prompt:
"Help me choose an AI provider strategy for my work.
Stack: [describe stack]
Task mix: [quick edits, debugging, architecture, code review, private code]
Constraints: [budget, privacy, offline needs, existing subscriptions]

Recommend:
1. the best default provider
2. when to switch to another provider or model family
3. where open source is worth considering
4. the biggest tradeoffs I should test myself instead of trusting benchmarks"

## 56. API Keys, Rate Limits, and Cost Management
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/api-keys-rate-limits-costs
Prompt page: https://aicodingguild.com/prompts/api-keys-rate-limits-costs
Estimated minutes: 13
Tags: api-keys, rate-limits, costs, pricing, budget, ai-operations
Summary: Understand AI API pricing, rate limits, budgets, and how to monitor and control your AI spending.

Prompt:
"Help me operationalize AI API usage for this app.
I need:
1. a secure API key handling plan for local, CI, and production
2. a rate-limit and retry strategy for 429s
3. a budget recommendation
4. guidance on which model tier to use for which task
5. a monitoring checklist so costs do not surprise me"

## 57. Fine-Tuning vs RAG vs Prompt Engineering
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/fine-tuning-vs-rag-vs-prompting
Prompt page: https://aicodingguild.com/prompts/fine-tuning-vs-rag-vs-prompting
Estimated minutes: 14
Tags: fine-tuning, rag, prompt-engineering, customization, ai-strategy
Summary: Three approaches to customizing AI — when each works, the cost and complexity tradeoffs, and which to try first.

Prompt:
"Help me choose between prompt engineering, RAG, and fine-tuning for this use case.
Problem: [describe it]
Knowledge base size: [small, medium, large]
How often it changes: [frequency]
Query volume: [approximate]
Budget and complexity tolerance: [describe]

Recommend the simplest approach that is likely to work, explain why, and tell me what evidence would justify moving to the next level."

## 58. Running Local Models — Ollama and LM Studio
Category: Working With AI Tools
Path: Working With AI Tools
Lesson: https://aicodingguild.com/learn/ai-tools/running-local-models
Prompt page: https://aicodingguild.com/prompts/running-local-models
Estimated minutes: 14
Tags: ollama, lm-studio, local-models, privacy, self-hosted, llama
Summary: Run AI models on your own machine — privacy benefits, performance tradeoffs, setup guides, and when local makes sense.

Prompt:
"Design a local AI coding setup for me.
Hardware: [CPU/GPU/RAM]
Operating system: [OS]
Constraints: [privacy, offline use, budget]
Typical tasks: [simple coding help, reviews, refactors, chat]

Recommend:
1. the best local model size I can realistically run
2. whether Ollama or LM Studio is the better starting point
3. what tool integration I should use
4. which tasks should still go to cloud models if policy allows"