vagejs with Cursor
The AI editor, ready to go.

Set up

1. Create a site in a terminal: npm create vagejs@latest my-site, then cd my-site && npm install.
2. Open the my-site folder in Cursor.
3. Open the agent panel and ask it to run npm run dev. Cursor shows the local address so you can watch changes as they happen.

How Cursor finds the instructions

Cursor reads AGENTS.md from the project root (and from subfolders, merged together) plus any project rules in .cursor/rules/. Project rules must be .mdc files; plain .md files in that folder are ignored. See Cursor's rules docs.

You don't need a Cursor rule to use vagejs. Add one only for your own preferences, for example .cursor/rules/voice.mdc with your house style.

Set how commands run

Cursor's agent can run terminal commands under different run modes. Choose Allowlist and add the commands that only read your project or build it:

• npm run check
• npm run build
• npx vage info --json

Leave deploy commands off the list so Cursor asks you each time. Cursor's run modes docs explain the options.

Prompts to try

@AGENTS.md Add a FAQ section to the home page using the questions in faq.txt. Keep the answers short and in plain English, then run npm run check.

Make every page's description unique and under 160 characters. Show me the list before you change anything.

Find pages with no internal links pointing to them and suggest where to link them from.

Typing @AGENTS.md makes sure the file is in the conversation. The prompt library has more.

Good to know

• Cursor also has a command-line agent; see Cursor's CLI docs.
• If a change looks wrong in the browser, tell the agent what you see. It can run npm run check and npm run audit to confirm the fix.