The prompt library

You are a senior developer helping a beginner plan a small project.
My idea: [describe your idea in 2-3 sentences].
Limits: I know basic HTML, CSS and a little JavaScript. It must be free to host. It must work on a phone.
Give me: (1) the 3-5 core features for a first version, (2) the features to leave for later, (3) the files I will need, (4) the order to build things in. Use short numbered lists. Do not write any code yet.

You are a product mentor who keeps beginners from overbuilding.
Here is my project idea: [paste idea].
It is too big for me to finish in one weekend. Cut it down to the smallest version that is still useful to one real person.
Shape: one paragraph describing the small version, then a list of what I am cutting and why.

You are a patient teacher. I want to build [what you want to build].
Which tools and languages should a beginner use for this, and why? Limits: prefer free tools, no paid hosting, and the fewest moving parts possible.
Shape: a short table with columns Tool, What it does, Why it is the simple choice. Then one sentence on what I should NOT use yet.

You are a senior developer. Break this feature into small slices I can build and test one at a time: [describe the feature].
Limits: each slice must take under 30 minutes and must be something I can see working in the browser.
Shape: a numbered list. For each slice, write what I will see on screen when it works.

You are an experienced developer reviewing a beginner's project plan.
Here is my plan: [paste plan].
Tell me the three parts most likely to go wrong for a beginner, and how I should prepare for each.
Limits: under 200 words. Do not write code.
Shape: a numbered list of three items. For each: the risk in one sentence, then how to prepare in one or two sentences.

You are a web developer building for a beginner.
Task: create a [type of page, e.g. personal portfolio] for [name], who is a [who they are].
Limits: ONE single HTML file. All CSS inside a <style> tag in the same file. No external libraries, no frameworks, no images from the internet. It must look good on a phone first.
Shape: the complete file in one code block, starting with <!DOCTYPE html> and ending with </html>. No explanation.

You are a careful web developer helping a beginner.
Here is my current file:
[paste the complete file]

Add this one feature: [describe it].
Limits: keep everything else exactly the same. Do not rename anything. Do not add libraries.
Shape: give me the complete updated file in one code block, then two sentences on what you changed.

You are a JavaScript teacher. In my page below, make [the button / the form / the list] do this: [describe what should happen].
Limits: plain JavaScript only, no frameworks. Put the script just before </body>. Add a short comment above each function explaining it in plain English.
Shape: the complete updated file.

[paste the complete file]

You are a patient JavaScript teacher. My app is below. Make it save [what to save, e.g. the list of expenses] using localStorage, so the data is still there after I refresh the page.
Limits: plain JavaScript. Use JSON.stringify to save and JSON.parse to load. Handle the case where nothing is saved yet, and the case where the saved data is broken, without crashing. Explain in 3 sentences what localStorage is and where the data actually lives.
Shape: the explanation first, then the complete updated file.

[paste the complete file]

You are a front-end developer. Create a form with these fields: [list fields].
Limits: show a friendly error message under any field that is empty or wrong. Do not use alert(). Plain HTML, CSS and JavaScript in one file. Must work on a phone.
Shape: the complete file in one code block.

You are a web designer who keeps things simple.
Here is my page: [paste file].
Improve only the design: spacing, font sizes, colours and alignment. Use a calm, professional colour scheme with good contrast.
Limits: do not change any text, any HTML structure, or any JavaScript. It must still work on a 360px-wide phone.
Shape: the complete updated file, then a short list of what you changed.

You are a patient senior developer helping a beginner debug.
What I did: [the steps].
What I expected: [what should have happened].
What actually happened: [paste the exact error message or describe exactly what you see].
Here is the relevant code: [paste code].
Tell me the most likely cause first, then the fix. Explain the cause in plain English in 2-3 sentences. Then give me the corrected code.

You are a patient senior developer. I got this error and I do not understand it:
[paste the exact error, including the line number]

Explain in plain words what it means, as if I have never coded.
Limits: no jargon without a short definition. Do not guess at code you have not seen.
Shape: two or three sentences on the meaning, then a numbered list of the three most common causes, each with how to check it.

You are a patient senior developer helping a beginner.
My page shows [a blank white screen / nothing happens when I click the button]. There is no visible error.
Here is my complete file: [paste file].
Walk me through how to open the browser's developer console and what to look for. Then check my file for the most likely problem.
Limits: fix only that one problem. Change nothing else.
Shape: numbered steps for the console first, then the cause in two sentences, then the complete fixed file.

You are a careful code reviewer.
This code was working. I changed [describe the change] and now [describe what broke].
Old version: [paste old code]
New version: [paste new code]
Compare them and tell me exactly which change broke it and why.
Limits: do not suggest other improvements.
Shape: the cause in two or three sentences, then only the lines I need to fix, with the line they replace.

You are a debugging coach. I cannot tell where my JavaScript goes wrong. Add console.log lines to the code below so I can see what is happening step by step. Each log message should say where it is and what value it is printing.
Limits: do not change any logic.
Shape: the complete file, then a sentence on where to look for the output.

[paste code]

You are a patient teacher. Explain what the code below does, line by line, to someone who has never coded.
Limits: plain English and no jargon. If you must use a technical word, define it in brackets.
Shape: a numbered list, one item per line or small group of lines, quoting the code before each explanation.

[paste code]

You are a teacher. Explain what [word, e.g. "API"] means to someone who has never coded, in four sentences, no jargon. Then give one everyday example from life in India.

You are a teacher who explains with simple steps.
Explain how [concept, e.g. "a browser loads a website"] works, from start to finish.
Limits: no more than 8 steps, one sentence each, no jargon.
Shape: a numbered list of steps, then one simple analogy.

You are a strict but kind teacher. I just learned about [topic].
Ask me 5 questions, one at a time, to check I really understand it. Wait for my answer before asking the next one. If I get one wrong, explain the right answer simply before moving on.

You are a patient teacher. What is the difference between [thing A] and [thing B]?
Limits: explain for a beginner, no jargon.
Shape: a small comparison table, then one sentence on when to use each.

You are a senior developer doing a friendly code review for a beginner.
Review the code below for: bugs, things that will break on a phone, security problems, and confusing names.
Shape: a numbered list, most serious problem first. For each, say why it matters and show the fix. Do not rewrite the whole file.

[paste code]

You are a security reviewer. Check this code for common beginner security mistakes: secret keys in the code, user input placed straight into the page, data sent without HTTPS, and anything else risky.
Explain each problem in plain words and show the safer version.

[paste code]

You are an accessibility tester. Check my page for accessibility problems: missing alt text, low colour contrast, buttons without labels, links with no visible focus outline, text that is too small on phones, and anything a screen reader would struggle with.
Limits: only report real problems in this file. Do not rewrite the whole page.
Shape: a checklist of problems, most serious first, with the fix for each.

[paste file]

You are a careful code reviewer. Another AI wrote the code below for me. Before I use it, review it. Do not rewrite it yet.
1. Explain in 5 bullet points what it does.
2. List anything that looks wrong, risky, or unnecessary.
3. List anything that depends on a library or service I would need to set up.

[paste code]

You are a senior developer. Refactor the code below to make it easier to read: better names, smaller functions, removed repetition.
Limits: the behaviour must stay exactly the same. Do not add features. Do not add libraries.
Shape: the complete refactored code, then a short list of what you changed and why.

[paste code]

You are a senior developer helping a beginner. My project is one big file and it is getting hard to manage. Split it into index.html, style.css and app.js.
Limits: everything must work exactly as before. Show me how the HTML links to the other two files.
Shape: the three complete files, each in its own code block, with the file name above each.

[paste file]

You are a senior developer. I have repeated the same kind of code several times in the file below. Find the repetition and replace it with one reusable function.
Limits: the behaviour must stay exactly the same.
Shape: the change explained in 3 sentences, then the complete updated file.

[paste code]

You are a patient teacher. Rewrite this code so a beginner can read it. Use descriptive variable names, add a short comment above each block, and avoid clever one-line tricks.
Limits: same behaviour. No new features or libraries.
Shape: the complete rewritten code.

[paste code]

You are a QA tester. Here is what my app does: [describe it].
List the 10 most important things I should test by hand, including the strange cases (empty input, very long text, refreshing the page, using a phone, no internet).
Shape: a numbered checklist I can tick off.

You are a QA tester. Here is a JavaScript function: [paste function].
List the inputs that could break it (empty, zero, negative numbers, text instead of a number, very large values).
Limits: do not change the code yet.
Shape: a table with the columns Input, What happens now, What should happen.

You are a patient teacher. Write simple tests for the function below using plain JavaScript and console.assert, so I can run them in the browser console without installing anything.
Limits: console.assert prints nothing when a test passes, so end with console.log("Tests finished") and tell me that only failed tests show a message.
Shape: the tests in one code block, then how to run them in 3 steps.

[paste function]

You are a QA tester for mobile websites. I want to check my website works on phones.
Limits: free tools only. Assume a budget Android phone with a 360px-wide screen.
Shape: a short checklist of what to look at on a real phone, then numbered steps for using Chrome's device toolbar on a laptop to preview different screen sizes.

You are a patient teacher. I have a website made of [list your files] and a GitHub account. Walk me through publishing it on GitHub Pages, step by step, using only the GitHub website (no terminal).
Shape: numbered steps. Tell me what I should see on screen after each step, and how long I might have to wait.

You are a deployment helper for beginners. My project has a front end and a small backend that calls an API with a secret key: [describe the setup and language].
Suggest a free or very cheap place to host it, and give me step-by-step instructions. Explain where the secret key should go so it never appears in my code or on GitHub.

You are a deployment helper for beginners. I tried to deploy my project to [hosting service] and got this error:
[paste the full error or build log]
Limits: if the log is not enough to be sure, say what else you need instead of guessing.
Shape: what went wrong in two or three plain-English sentences, then numbered steps to fix it.

You are a careful senior developer. I am about to share my project publicly. Here is what it does: [describe].
Give me a pre-launch checklist covering: broken links, phone layout, page title and description, favicon, no secrets in the code, no personal data I did not mean to share, and anything else important.
Limits: only things a beginner can check in under an hour.
Shape: a checklist with - [ ] boxes, most important first.

You are a coding mentor. I can study [hours] hours a week. I know [what you know]. I want to be able to [goal] in [weeks] weeks.
Give me a week-by-week plan with one small project each week.
Limits: free resources only, official documentation where possible.
Shape: one short section per week: what to learn, the project, and how I will know I am done.

You are a patient teacher. Here is a project I built with AI help: [paste code or describe it].
Pick the 5 most important concepts used in it that I should truly understand.
Limits: use examples from my own code.
Shape: a numbered list. For each concept, a 3-sentence explanation and one small exercise I can do without AI.

You are a friendly senior developer. Here is a section of official documentation I find hard: [paste the text].
Explain it: what it is for, when I would use it, and a tiny example.
Limits: use only what the text says. If something is not in it, tell me rather than guessing.
Shape: three short headed parts (What it is for, When to use it, Example), then the one line in the original that matters most.

You are a coding mentor. Give me a small coding exercise on [topic] that I should be able to solve on my own in 20 minutes.
Limits: do not give the answer. When I paste my attempt later, give hints before you give solutions.
Shape: the exercise in under 100 words, with one example of the expected result.

You are a developer who writes clear README files. Write a README.md for my project.
Project: [name]. What it does: [one sentence]. Built with: [tools]. Live link: [URL]. What I learned: [2-3 points].
Shape: Markdown with these sections: title, one-line description, live link, features, how to run it, what I learned. Keep it honest and short. Do not invent features.

You are a friend who writes plain, honest LinkedIn posts. Write a post about a project I built.
Project: [what it does]. Live link: [URL]. The hardest part was: [what]. What I learned: [what]. I used AI tools: [which] and I checked and understood the code myself.
Limits: under 150 words, honest, no hype words like "revolutionary" or "game-changer", no hashtag spam (maximum 3). Write in first person, in simple English.

You are a career coach for freshers. Turn this project into 2 resume bullet points: [describe the project, tools used, and any real result].
Limits: start each with an action verb, mention the tools, and do not invent numbers or results I did not give you.
Shape: two bullet points, each under 25 words.

You are a friendly interviewer for a junior web developer role. Ask me to explain how my project works: [describe project].
Ask one question at a time, wait for my answer, then tell me what was good and what was unclear. After 5 questions, give me a short summary of what to practise.

You are a career coach. Help me write a short, polite message to [a person / a startup / a local business] offering to [what you can do, e.g. build a simple website].
Limits: under 80 words. Friendly, not pushy. No exaggeration about my experience.
Shape: one message, ready to send, with one link to my work: [URL].

You are a mentor reviewing a beginner's GitHub profile. My projects are: [list with one line each].
Suggest: a short profile bio, which 3 projects to pin and why, and a better one-line description for each.