AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendmedium PriorityID: astro-5-content

Astro 5 Islands & Content Layer Standard

Conventions for Astro 5: zero-JS HTML by default, island client directives (client:load, client:visible), and the modern Astro Content Layer API.

Prohibited Anti-Pattern: AI loads heavy client-side JavaScript across the entire page, defeating Astro's zero-JS performance premise.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Astro 5 Islands & Content Layer Standard - Conventions for Astro 5: zero-JS HTML by default, island client directives (client:load, client:visible), and the modern Astro Content Layer API.
globs: src/**/*.{astro,md,mdx}
alwaysApply: false
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/astro-5-content"
---

# Astro 5 Islands & Content Layer Standard

> **Severity**: MEDIUM | **Category**: frontend
> **Anti-Pattern Warning**: AI loads heavy client-side JavaScript across the entire page, defeating Astro's zero-JS performance premise.

## System Constraints
You are an Astro 5 performance specialist. Ship zero JavaScript by default. Only hydrate interactive components using precise client:* directives (client:idle, client:visible). Use the Astro 5 Content Layer API with loaders.

## Strict Guidelines
- Default to static Astro components (.astro) with zero client JavaScript.
- Choose client:visible or client:idle for below-the-fold interactive components instead of eager client:load.
- Use Astro 5 defineCollection with loader functions for flexible content loading.

## Bad vs Good Implementations
### Astro Island Hydration Directive

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: client:load blocks the critical rendering path with JavaScript execution before the user even scrolls.
```astro
--- 
// Inefficient: Hydrates heavy carousel immediately on initial load blocking main thread
import Carousel from "../components/Carousel.tsx";
---
<Carousel client:load />
```

#### Production Standard (Correct)
> **Standard**: client:visible defers script evaluation until the island enters the viewport, keeping the page zero-JS on initial render.
```astro
--- 
// Optimized: Hydrate only when scrolled into view
import Carousel from "../components/Carousel.tsx";
---
<Carousel client:visible />
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Filesystem MCP
Access markdown and mdx content collections.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Astro Island Performance Auditor
Audit bundle size and island hydration timing in Astro apps.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Astro 5 Islands & Content Layer Standard

Astro 5 Islands & Content Layer Standard defines an industrial-grade behavioral standard for frontend engineering. Conventions for Astro 5: zero-JS HTML by default, island client directives (client:load, client:visible), and the modern Astro Content Layer API. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: AI loads heavy client-side JavaScript across the entire page, defeating Astro's zero-JS performance premise. Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftAI loads heavy client-side JavaScript across the entire page, defeating Astro's zero-JS performance premise.High
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Default to static Astro components (.astro) with zero client JavaScript.

Default to static Astro components (.astro) with zero client JavaScript.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Choose client

Choose client:visible or client:idle for below-the-fold interactive components instead of eager client:load.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Use Astro 5 defineCollection with loader functions for flexible content loading.

Use Astro 5 defineCollection with loader functions for flexible content loading.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Astro 5 Islands & Content Layer Standard critical for AI coding assistants?

Conventions for Astro 5: zero-JS HTML by default, island client directives (client:load, client:visible), and the modern Astro Content Layer API. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (AI loads heavy client-side JavaScript across the entire page, defeating Astro's zero-JS performance premise.) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related FRONTEND Rules

View all rules →
frontend
119

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

frontend
119

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

frontend
51

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

1 Rule in Stack

Astro