Astro4

A set of development rules for Astro 4 and newer, where Astro is a framework for building fast websites and web applications. It covers components, page structure, interactive browser features, content collections, and server-side or static rendering.

In plain words
What is it for?
Use it when building or reviewing Astro pages, layouts, components, content collections, routes, and interactive features.
Why use it?
It helps an agent follow Astro's project structure and choose how much browser-side JavaScript a page needs.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/thesethrose/devrules/astro4
Clone the repo
git clone --depth 1 https://github.com/TheSethRose/DevRules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,018 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01018
Opus 5 $0.00000 $0.00509
Sonnet 5 $0.00000 $0.00204
Haiku 4.5 $0.00000 $0.00102

Measured 2d ago against content hash 0e1d93f7d264, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Astro4 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/technologies/Astro4.mdc · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Astro Development Best Practices (v4+)

You are an expert Astro developer, aware of its features up to version 4+. Reference: https://docs.astro.build/en/getting-started/

Core Concepts

  • Component-Based: Uses .astro files blending HTML, scoped CSS, and JS/TS frontmatter.
  • Islands Architecture: Zero-JS by default. Use client:* directives (load, idle, visible, media, only) to hydrate interactive UI components (Islands) client-side.
  • UI Framework Agnostic: Integrates with React, Vue, Svelte, Solid, Preact, Alpine.js, etc.
  • Content-Focused: Built-in Content Collections API for type-safe Markdown/MDX. Astro DB for integrated database solutions.
  • Server-First: Prioritizes Server-Side Rendering (SSR) via Adapters or Static Site Generation (SSG).
  • View Transitions: Built-in support for smooth page transitions and persistent elements using astro:transitions.

Project Structure (Typical)

  • src/pages/: File-based routing (.astro, .md, .mdx, .js, .ts for API routes).
  • src/layouts/: Reusable page layout components (.astro).
  • src/components/: Reusable UI components (.astro or framework components).
  • src/content/: Content Collections (config.ts, posts/, docs/, etc.).
  • src/styles/: Global CSS, fonts.
  • src/middleware.{ts,js}: For executing code before/after rendering (auth, redirects).
  • src/env.d.ts: TypeScript definitions for Astro environment.
  • public/: Static assets.
  • astro.config.mjs (or .ts): Main configuration.
  • db/config.ts, db/seed.ts: Astro DB configuration and seeding.

Configuration (astro.config.mjs)

  • Define site, base, output mode (static/server/hybrid).
  • Configure Integrations: UI Frameworks (@astrojs/react, etc.), Tailwind (@astrojs/tailwind), MDX (@astrojs/mdx), Sitemap (@astrojs/sitemap), Astro DB (@astrojs/db).
  • Setup Adapters for deployment (Vercel, Netlify, Cloudflare, Node).
  • Define Vite plugin options.
  • Manage TypeScript settings.
  • Configure Markdown/MDX options (syntax highlighting, remark/rehype plugins).
  • Set up Internationalization (i18n) routing.
  • Enable Experimental Features.

Read the full file on GitHub · 65 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 65 lines · 0 tokens per session scan A 0e1d93f7d264

Subscribe to this mod's changes

Astro4 is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,018 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.