Can an Astro site use React or Vue components?
Yes, through official integrations. The rule only asks the agent to use them where interactivity is needed and to hydrate them as late as possible.
An Astro site that ships HTML first and JavaScript only where an island needs it. The rules protect that default, because agents tend to add client directives and frameworks the page never needed.
# AGENTS.md
Project: astro-site. A content-focused Astro site with Markdown content collections and static output.
This file is the single source of truth for every coding agent working in this repository. The tool-specific files (CLAUDE.md, GEMINI.md, .github/copilot-instructions.md and .cursor/rules/project.mdc) point here. Edit this file, not those.
## Stack
- Languages: TypeScript, HTML and CSS
- Framework: Astro
- Hosting: Netlify
- Tests: Playwright
- Package manager: npm
## Commands
Run these from the repository root.
- Install dependencies: `npm install`
- Run locally: `npm run dev`
- Build: `npm run build`
- Run all tests: `npx playwright test`
- Run one test file: `npx playwright test tests/path.spec.ts`
- Lint: `npx eslint .`
- Type-check: `npx astro check`
- Format: `npx prettier --write .`
## Project layout
- `src/pages/`: File-based routes (.astro, .md, endpoints)
- `src/content/`: Content collection entries (Markdown, MDX)
- `src/content.config.ts`: Collection schemas
- `src/components/`: Astro components and framework islands
- `src/layouts/`: Page layouts
- `public/`: Static files served as-is
## Code style
- Indent with 2 spaces. Never tabs.
- TypeScript runs in strict mode. Do not use `any`; use `unknown` and narrow it, or write the real type.
- Match the style and patterns of the surrounding code, even where you would personally choose differently.
- Delete code you make unused, including imports, flags and files. Do not leave commented-out code behind.
- Every new UI control works with a keyboard, has a visible focus state and an accessible name.
## Working rules
- Before you say a task is done, run the test, lint and type-check commands above and make sure they pass. If you could not run them, say so.
- Never write secrets, API keys, tokens or passwords into code, tests, fixtures, logs or commits. Read them from environment variables, and never commit `.env` files.
- Do not add a new dependency without asking first. Prefer the standard library and what is already installed.
- Change only what the task needs. Do not refactor, rename or reformat unrelated code.
## Product constraints
- Watch the performance budget: no new blocking requests on page load, and justify any bundle-size increase in the change description.
- Public pages must render their main content as HTML on the server, with a unique title, meta description and one h1.
## Project-specific notes
- Default to `.astro` components, which ship zero JavaScript. Use a UI framework component only when it needs interactivity.
- Add the smallest client directive that works: prefer `client:visible` or `client:idle` over `client:load`.
- Content lives in content collections with a schema in `src/content.config.ts`; query it with `getCollection`, not file globs.
- Every page sets a unique `<title>`, meta description and canonical URL through the shared layout.
- Use the `<Image />` component from `astro:assets` for local images so they are optimized and sized.
- Run `npx astro check` after changing components or collection schemas.
## Project phase
This project is in active development. Follow the patterns that already exist; consistency beats novelty.
# CLAUDE.md
@AGENTS.md
## Claude Code
- The shared project instructions are imported from AGENTS.md on the line above. Edit AGENTS.md, not this file, so every agent stays in sync.
- Put Claude-only preferences below this line. Personal, uncommitted notes belong in CLAUDE.local.md.
# GEMINI.md
@./AGENTS.md
## Gemini CLI
- The shared project instructions are imported from AGENTS.md on the line above. Edit AGENTS.md, not this file.
- Alternative: delete this file and set "context": { "fileName": ["AGENTS.md"] } in .gemini/settings.json so Gemini CLI reads AGENTS.md directly.
# Copilot instructions
Project: astro-site. A content-focused Astro site with Markdown content collections and static output.
The full instructions are in AGENTS.md at the repository root. Read it before you change code; if anything here disagrees with it, AGENTS.md wins. The essentials are repeated below for Copilot surfaces that only read this file.
## Stack
- Languages: TypeScript, HTML and CSS
- Framework: Astro
- Hosting: Netlify
- Tests: Playwright
- Package manager: npm
## Commands
- Install dependencies: `npm install`
- Run locally: `npm run dev`
- Build: `npm run build`
- Run all tests: `npx playwright test`
- Run one test file: `npx playwright test tests/path.spec.ts`
- Lint: `npx eslint .`
- Type-check: `npx astro check`
- Format: `npx prettier --write .`
## Working rules
- Before you say a task is done, run the test, lint and type-check commands above and make sure they pass. If you could not run them, say so.
- Never write secrets, API keys, tokens or passwords into code, tests, fixtures, logs or commits. Read them from environment variables, and never commit `.env` files.
- Do not add a new dependency without asking first. Prefer the standard library and what is already installed.
- Change only what the task needs. Do not refactor, rename or reformat unrelated code.
---
description: Project instructions for every task (mirrors AGENTS.md)
globs:
alwaysApply: true
---
# Project rules
The project instructions live in @AGENTS.md at the repository root, which Cursor loads automatically. They are not repeated here, so they cost context only once. Edit AGENTS.md, not this rule.
Before you change code, check the Commands and Working rules sections of AGENTS.md, and run its test and lint commands before you say a task is done.
Put Cursor-only rules below, or add scoped rules as more .mdc files with `globs` (for example `src/components/**/*.tsx`).
These are the exact files the generator writes for this preset. Change any command or rule in the generator and download your own set.
The preset describes a a content-focused Astro site with Markdown content collections and static output. Its AGENTS.md is 49 non-empty lines with 8 exact commands, 6 key directories, and 6 stack-specific rules on top of the shared working rules.
npm install, npm run dev, npm run build, npx playwright test, npx playwright test tests/path.spec.ts, npx eslint ., npx astro check, npx prettier --write ..src/pages/, src/content/, src/content.config.ts, src/components/, src/layouts/, public/.Astro pages are fast because they ship no JavaScript by default. An agent that wraps a static list in a React component with client:load adds a framework runtime for nothing. The rule makes interactivity a deliberate choice.
A schema validates every Markdown frontmatter field at build time, so a missing date or misspelled tag fails loudly instead of rendering a broken page. Agents prefer quick globs, which skip validation.
Raw <img> tags skip resizing and dimension hints, causing layout shift and heavy pages. The Image component handles both.
Duplicate titles and missing descriptions are the most common defects on generated pages; routing them through one layout keeps them consistent.
.astro components, which ship zero JavaScript. Use a UI framework component only when it needs interactivity.client:visible or client:idle over client:load.src/content.config.ts; query it with getCollection, not file globs.<title>, meta description and canonical URL through the shared layout.<Image /> component from astro:assets for local images so they are optimized and sized.npx astro check after changing components or collection schemas.Want different commands or rules? Load this preset into the generator, change anything, and download your own set.
AGENTS.md is read directly by Codex, Cursor, Windsurf, Cline, Zed and Jules, and by GitHub Copilot's cloud agent, code review and CLI. Claude Code reads it through the generated CLAUDE.md, and Gemini CLI through GEMINI.md. See the compatibility table for details, last verified 2026-11-13.
All presets are on the stacks page.
Yes, through official integrations. The rule only asks the agent to use them where interactivity is needed and to hydrate them as late as possible.
It assumes static output. If you use an adapter for on-demand rendering, note which routes are server-rendered in the generator so the agent knows.
A content site has little logic and a lot of pages. A few end-to-end checks that pages render, link and pass accessibility checks catch more real problems.
Yes. Copy them into any project, commercial or not, without attribution. They are a starting point: adjust the commands and rules to match your repository.
You do not have to take our word for it. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing you type is sent. The check takes under a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Only the feedback form can add a line to that log, and it sends only the vote and comment you type into it. 2prompt has no server code at all: no API, no model and no database of your files. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site, the fonts and the anonymous analytics endpoint.