Claude
Chat assistant that is strong at writing and explaining code. You can paste files and ask for full pages.
Free: Free plan, check limits
Visit53 colourful cards: AI tools to build with, copy-ready prompts for starting, designing, fixing, improving and shipping, plus habits that make prompts work. Replace the [brackets] with your own details.
Pick one chat tool, one editor or builder, and keep a project in GitHub. Free plans change often, so check limits before you start.
Chat assistant that is strong at writing and explaining code. You can paste files and ask for full pages.
Free: Free plan, check limits
VisitGeneral chat assistant that can write, explain and fix code.
Free: Free plan, check limits
VisitTry Gemini models in the browser and build quick app prototypes.
Free: Free to use, check limits
VisitCommand-line coding agent that works inside your project folder.
Free: Needs a paid plan or API credits
VisitAI code editor based on VS Code, with chat and inline edits.
Free: Free plan, check limits
VisitAI code editor with an agent that edits several files.
Free: Free plan, check limits
VisitAI completion and chat inside VS Code and other editors.
Free: Free tier, check limits
VisitDescribe an app and get a full-stack project you can edit and deploy.
Free: Free plan, check limits
VisitBuild and run full-stack web apps in the browser from a prompt.
Free: Free tier, check limits
VisitGenerate React and Tailwind interfaces from a prompt or screenshot.
Free: Free tier, check limits
VisitBrowser IDE with an AI agent that can build and host small apps.
Free: Free starter plan, check limits
VisitGive the goal, the stack, the pages and the style in the first message. Replace the [brackets] with your own details.
Use to get a first working page in one file.
Prompt: Build a single-file landing page (HTML, CSS and a little vanilla JS) for [product name]: [one-sentence description]. Sections: hero with a call-to-action, 3 feature cards, pricing, FAQ and footer. Make it responsive with a mobile menu, use a [colour] accent, and keep the code readable with comments. Do not use any build tools.
Use for a personal site that you will host on GitHub Pages.
Prompt: Create a portfolio website for a [role] named [name]. Pages: Home, Projects, About, Contact. Plain HTML, CSS and JS only so it works on GitHub Pages. Include a dark mode toggle, a project grid with filters, and a contact form that posts to [form service]. Keep each page under 300 lines and explain the folder structure at the end.
Use when you need to save and edit data.
Prompt: Build a [type of app, e.g. expense tracker] using [framework, e.g. Next.js] and [database, e.g. Supabase]. Features: add, edit, delete and list [items]; sign in with email; each user only sees their own data. First show me the database schema and the list of files you will create, wait for my OK, then write the code.
Use for admin screens and reports.
Prompt: Build a responsive dashboard for [topic] using [React or plain JS] and [chart library]. Show 4 summary cards, a line chart for [metric] over time, a bar chart for [metric] by category, and a sortable table. Use sample data in a separate file so I can replace it later.
Use for small browser tools.
Prompt: Make a Chrome extension (Manifest V3) that [what it does]. List the files and permissions needed, explain why each permission is required, and give me steps to load it unpacked for testing.
Use for a simple server.
Prompt: Write a small REST API in [Node.js with Express or Python with FastAPI] for [resource]. Include routes to create, read, update and delete, input validation, error handling, a .env.example file, and a README with curl examples. Do not add features I did not ask for.
Be concrete about layout, colours and feel. Screenshots and a reference site help a lot.
Use to keep design consistent.
Prompt: Restyle this page to feel [calm, bold, playful or minimal]. Use this palette: [hex colours], this font: [font], 8px spacing, rounded corners of [size], and soft shadows. Keep all the existing content and behaviour, and only change styling.
Attach a screenshot first.
Prompt: Recreate the attached screenshot as a responsive page with HTML and CSS. Match spacing, font sizes and colours as closely as you can, then list anything you had to guess.
Use on an existing site.
Prompt: Add a light and dark theme to this site using CSS variables. Respect the system setting by default, add a toggle button in the header, and remember the choice in localStorage with a safe fallback if storage is blocked.
Use when it looks wrong on phones.
Prompt: Review this page for small screens (360px wide). Fix horizontal scrolling, tap targets smaller than 44px, text that is too small and images that overflow. Show me the changes as a list before the code.
Use for polish.
Prompt: Add gentle animations: fade-in on scroll for sections, hover lift on cards and a smooth button press. Use CSS only where possible, keep each animation under 300ms and respect prefers-reduced-motion.
Paste the exact error text and the code around it. Say what you expected and what happened.
Use when you have an error message.
Prompt: I get this error: [paste full error message]. Here is the relevant code: [paste code]. Explain in plain words what causes it, then give the smallest fix. Show only the lines that change.
Use when something behaves wrongly.
Prompt: Expected: [what should happen]. Actual: [what happens]. Steps to reproduce: [steps]. Before changing anything, list 3 likely causes, tell me how to check each one, and then suggest a fix for the most likely.
Use for front-end problems.
Prompt: Here are the browser console errors and the failed network requests: [paste]. Tell me which one is the root cause and which are side effects, and what to change.
Use when fixes keep causing new bugs.
Prompt: Fix only [specific problem] in [file]. Do not rename functions, change other files or reformat code. If you think something else must change, tell me first and wait.
Use when a library or API changed.
Prompt: This code was written for [library version]. I am using [new version]. List what changed between them that affects this code and update it. Link to the migration notes you used if you can.
Ask for a review before a rewrite, so you can pick what to change.
Use before you ship.
Prompt: Review this code like a senior developer. Group findings as bugs, security risks, performance and readability. For each, say how serious it is and show a fix. Do not rewrite the whole file.
Use to clean up long files.
Prompt: Refactor this code into smaller functions with clear names without changing behaviour. Keep the public API the same, and list every function you moved or renamed.
Use for apps with logins or forms.
Prompt: Audit this app for common security problems: exposed secrets, missing input validation, injection, weak authentication and unsafe CORS. List each problem with the file and line, and how to fix it.
Use when pages feel slow.
Prompt: Suggest ways to make this page load faster: image sizes and formats, render-blocking scripts, fonts, caching and unused code. Rank them by impact and show the code for the top three.
Use for public sites.
Prompt: Check this page against WCAG 2.1 AA basics: colour contrast, headings order, alt text, form labels, keyboard focus and ARIA. List problems and fixes.
Use for content sites.
Prompt: Review this HTML for SEO basics: title and meta description, heading structure, canonical link, Open Graph tags, structured data and image alt text. Suggest exact changes.
Use these when the code works and you want to publish it.
Paste the diff.
Prompt: Write a clear git commit message for this diff. Use a short summary line under 60 characters in the imperative mood, then a short body explaining why. Diff: [paste]
Use for any repo.
Prompt: Write a README for this project with: what it does, a screenshot placeholder, how to install and run it, environment variables (names only, never real values), folder structure and how to deploy. Here are the files: [paste file list].
Use before you push to GitHub.
Prompt: Read this code and list every environment variable it uses. Create a .env.example with placeholder values and a comment for each, and a .gitignore line so the real .env is never committed.
Use before Cloudflare Pages, Netlify or Vercel.
Prompt: I want to deploy this project on [Cloudflare Pages, Netlify or Vercel]. Tell me the build command, output directory, environment variables to add, and anything in my code that will break in production. Then give me a short checklist.
Use when you are stuck.
Prompt: Here is what my project does today: [summary]. I want to add [feature]. Suggest a plan in small steps that each leave the app working, and tell me which step to do first.
These matter more than any single prompt.
Name the goal, the user and the technologies. "Build a booking page in plain HTML and CSS" beats "make a website".
Add: "Show me the plan and wait for my OK before writing code." It catches wrong assumptions cheaply.
Small requests are easier to test and to undo. Commit after every change that works.
Copy the full message and the code around it. Paraphrased errors lead to guesses.
Show a sample input and the output you want. Attach a screenshot for visual work.
Say what not to touch: other files, the design, the database. Ask it to list assumptions.
Do not put real API keys, passwords or private data into a prompt. Use placeholders and keep secrets in environment variables.