Prompt library
Copy, paste, review.
These prompts work with any coding agent that can read your project, whether that's Claude Code, Codex, Cursor, Copilot or Gemini CLI. Each one points the agent at AGENTS.md, keeps the facts in your hands, and ends with a check, so you get a working site instead of a confident guess. Replace the parts in capitals.
Start a new site
Read AGENTS.md. This site is for MY BUSINESS, which DOES WHAT for WHO. Write a home page with a clear one-sentence headline, three short sections and a contact link. Ask me for anything you'd otherwise have to invent. Then run npm run check until it reports 0 errors.Suggest the pages this site needs, based on the notes below. For each page give me a title, a description under 160 characters and the URL. Don't create anything until I approve the list.
NOTESAdd and edit content
Add a page at /PAGE-SLUG/ from the text below. Keep my wording, fix only spelling, and write a description under 160 characters. Run npm run check.
TEXTWrite a blog post called "TITLE" from these notes. Use type: article, and set author and datePublished only from what I give you here: AUTHOR, DATE. Run npm run check when you're done.Rename /OLD-SLUG/ to /NEW-SLUG/. Move the file, add a redirect in vage.config.ts, and update every link that pointed to the old address. Confirm with npm run check.Fix problems
Run npx vage check --json. Fix every error, one file at a time. Then list any warnings you couldn't fix and explain why.Run npm run audit and explain the results in plain English. Fix what you can without changing how the pages look, and tell me what needs my decision.The page /PAGE-SLUG/ looks wrong: DESCRIBE WHAT YOU SEE. Find the cause, fix it, and run npm run check.Search and AI visibility
Review every page's title and description. Flag titles over 60 characters, descriptions over 160, and any two pages that target the same topic. Suggest fixes, but don't change anything yet.Our business details are: NAME, WEBSITE, LOGO PATH. Add them as Organization structured data in vage.config.ts, using only these facts. Run npm run check.We want to allow AI search crawlers but not AI training crawlers. Update the robots settings in vage.config.ts, then show me the generated robots.txt.Analytics
Add Google Analytics 4 with measurement ID G-XXXXXXX. Read it from an environment variable rather than writing it in the code, and start with consent set to denied. Run npm run check.Track clicks on the "Book a call" button as an event called book_call. Declare the event in vage.config.ts and use data-vage-event on the link, with no custom JavaScript.Publish safely
Run npx vage deploy:github --dry-run and show me exactly which files would be committed. Don't push anything.Get the site ready to publish: run check, build and audit, and summarize anything I should fix first. Stop before deploying. I'll run the deploy myself.Tips for better results
- Give it the facts. Paste your notes, prices or opening hours. An agent that has to guess will guess.
- Ask for a plan first on bigger changes: "Show me the plan before you edit anything."
- One job per prompt. Small, checked steps are easier to review than one big change.
- Always end with a check.
npm run checkis how you know the site still works.