- name
SKILL.md
Tệp skill vẫn nằm trong kho mã của nhà phát hành.
Dán lệnh đã sao chép vào terminal. Lệnh sẽ cài đặt tệp SKILL.md này vào agent đó.
npx skills add ericrisco/rsc-harness --skill astro -a cursor -yDán lệnh đã sao chép vào terminal. Lệnh sẽ cài đặt tệp SKILL.md này vào agent đó.
npx skills add ericrisco/rsc-harness --skill astro -a claude-code -yDán lệnh đã sao chép vào terminal. Lệnh sẽ cài đặt tệp SKILL.md này vào agent đó.
npx skills add ericrisco/rsc-harness --skill astro -a codex -yDán lệnh đã sao chép vào terminal. Lệnh sẽ cài đặt tệp SKILL.md này vào agent đó.
npx skills add ericrisco/rsc-harness --skill astro -a grok -yGửi tin nhắn đã sao chép trong cuộc trò chuyện Grok Bot. Bot sẽ lấy tệp SKILL.md này từ GitHub và thêm vào bộ skill mà mọi Bot của bạn dùng chung.
Install this skill: https://github.com/ericrisco/rsc-harness/tree/HEAD/skills/astroTừ nhà phát hành
Ship zero client JavaScript by default. Hydrate the smallest possible surface, as late as you can
get away with. An .astro component renders to HTML at build time and ships no runtime; every
island is a bundle the visitor downloads, parses, and executes. Content and marketing sites win on
TTFB/LCP and Lighthouse, not on React-everywhere. If you find yourself adding client:load to make
a page "work," stop — the page already works; you are adding interactivity, and interactivity is the
expensive exception, not the default.
Astro 6.0 is stable (released 2026-03-10); the Astro 5 line is
still production-ready. Do not mix advice across majors — read package.json → the astro version
before advising. What v6 changes, per the
upgrade-to-v6 guide:
22.12.0 or higher is required (18 and 20 are dropped) — check the actual runtime.src/content.config.ts. The legacy src/content/config.ts path is
removed, not merely discouraged, and the old auto-detection (legacy.collections) is gone.
The legacy.collectionsBackwardsCompat escape hatch is a migration crutch, not a supported layout.z is imported from astro/zod, not
astro:content (see Content collections below).Pick the cheapest row that satisfies the requirement. Read top-down; stop at the first match.
Default: every page is prerendered to static HTML at build time. You opt into dynamism per route — never the other way around.
---
// src/pages/dashboard.astro — opt this ONE route into on-demand (SSR) rendering.
// Requires a configured adapter (Vercel/Netlify/Cloudflare/Node). Everything else stays static.
export const prerender = false;
const user = await getUser(Astro.request); // runs per request
---
<h1>Hello {user.name}</h1>
---
// src/pages/blog/[slug].astro — many STATIC routes generated from data at build time.
import { getCollection } from "astro:content";
export async function getStaticPaths() {
const posts = await getCollection("blog");
return posts.map((post) => ({ params: { slug: post.id }, props: { post } }));
}
const { post } = Astro.props;
---
<h1>{post.data.title}</h1>
In Astro 6 the dev server runs the production runtime (Vite 7 Environment API), so dev no longer
diverges from prod on Cloudflare/Bun/Deno — fewer "works in dev, breaks on deploy" surprises. Adapter
choice per platform → references/deploy-and-integrations.md.
A client:* directive turns a framework component into a hydrated island. Choose the latest
directive that still feels instant to the user — never default to client:load.
---
import Carousel from "../components/Carousel.tsx";
---
<Carousel client:load />
<Carousel client:visible />
client:only gotcha: it skips SSR entirely, so the component produces no server HTML (expect a
flash/layout shift) and you must name the framework (client:only="react") — Astro can't infer
it without the server render. Reach for it only when SSR genuinely breaks; otherwise prefer
client:visible.
Type-safe content lives in a single config file. The path is load-bearing:
// src/content.config.ts ← v6 path. NOT src/content/config.ts (legacy path removed in v6)
import { defineCollection } from "astro:content";
import { z } from "astro/zod"; // v6: z moved OUT of astro:content into astro/zod (Zod 4)
import { glob } from "astro/loaders";
const blog = defineCollection({
// glob() sources files from anywhere; `id` comes from the filename minus extension
loader: glob({ pattern: "**/*.{md,mdx}", base: "./src/data/blog" }),
schema: z.object({
title: z.string(),
pubDate: z.coerce.date(),
draft: z.boolean().default(false),
tags: z.array(z.string()).default([]),
}),
});
export const collections = { blog };
Query and render in a page. render() is now a standalone call (not entry.render()):
---
// src/pages/blog/[slug].astro
import { getCollection, getEntry, render } from "astro:content";
export async function getStaticPaths() {
const posts = await getCollection("blog", ({ data }) => !data.draft);
return posts.map((post) => ({ params: { slug: post.id }, props: { post } }));
}
const { post } = Astro.props;
const { Content } = await render(post);
---
<article><h1>{post.data.title}</h1><Content /></article>
Built-in loaders are glob() (many files) and file() (one JSON/YAML array). Custom and CMS
loaders, Zod 4 schema patterns, collection references, Live Content Collections (real-time data with
no rebuild, stable in v6), querying and MDX details → references/content-layer.md.
When most of a page is static and CDN-cacheable but one fragment is per-visitor, use a server island instead of turning the whole route into SSR. The page ships static; the island is fetched and rendered after first paint.
---
// src/components/UserGreeting.astro — rendered on demand, deferred after the static shell
const user = await getUserFromCookie(Astro.request);
---
<span>Welcome back, {user.name}</span>
---
import UserGreeting from "../components/UserGreeting.astro";
---
<header>
<UserGreeting server:defer>
<span slot="fallback">Welcome</span>
</UserGreeting>
</header>
This beats full SSR when: the page is otherwise cacheable on a CDN, and only a small slice depends on the request. You keep static LCP and personalize without making every request hit the origin.
Use astro add so it patches astro.config.mjs and installs peers in one step:
npx astro add react mdx sitemap
@tailwindcss/vite), not the legacy
@astrojs/tailwind integration (that path was for Tailwind 3).astro.config.mjs — no manual
@font-face.Adapter recipes per platform, hybrid rendering, env handling, SSR endpoints (src/pages/api/*.ts)
and the Fonts/CSP config → references/deploy-and-integrations.md.
<Image>/<Picture> from astro:assets — automatic width/height, format, and
lazy-loading kill CLS and over-sized payloads. Never a raw <img> for local assets.<ClientRouter /> from astro:transitions to the <head> for SPA-like
navigation without an SPA. Prefetch links with the prefetch config/attribute.Run the codemod first, then verify each item:
npx @astrojs/upgrade
22.12.0+ (CI image, local, deploy target).z import moved: import { z } from "astro/zod" — z and astro:schema are gone
from astro:content. Then review for Zod 4 breaking changes.src/content.config.ts (delete src/content/config.ts; the
legacy path is removed, not just deprecated).docs.astro.build/en/guides/upgrade-to/v6.bash scripts/verify.sh from the Astro project root — grep-based, needs no install. It FAILS if
a v6 project still has src/content/config.ts instead of src/content.config.ts, WARNS on
over-hydration smells (many client:load, or client:only with no framework string), CHECKS
that content schemas import from astro:content, and — only if the astro binary resolves —
optionally runs npx astro check. On an empty or clean tree it prints OK and exits 0; warnings are
advisory and never fail the run.
../nextjs/SKILL.md — when the project is really an app-router React app with server actions and
heavy client interactivity, not a content/marketing site.../landing-copy/SKILL.md and ../seo-geo/SKILL.md — this skill builds the site; those write the
copy and decide the SEO/structured-data strategy that fills it.../vercel/SKILL.md, ../netlify/SKILL.md, ../cloudflare/SKILL.md — platform mechanics (DNS,
env, build settings) once the code and adapter are ready.Use when building a content-driven or marketing site with Astro 6: static-first pages, islands and partial hydration, content collections, server islands, per-route on-demand rendering, deploy adapter
---name: astrodescription: Use when building a content-driven or marketing site with Astro 6: static-first pages, islands and partial…---# skills/astro/SKILL.mdTổng quan
Use when building a content-driven or marketing site with Astro 6: static-first pages, islands and partial hydration, content collections, server islands, per-route on-demand rendering, deploy adapters, and Astro 5→6 migration. NOT app-router React with server actions and heavy client interactivity (that is `nextjs`).
Câu hỏi thường gặp
Tải skills/astro/SKILL.md từ nhà phát hành, hoặc sao chép đường dẫn và mở kho mã. PlugMCP chỉ liệt kê skill và không lưu trữ tệp này.
Nhà phát hành duy trì nó tại https://github.com/ericrisco/rsc-harness.
Claude, Cursor, Codex và Grok Build có thể đọc tệp SKILL.md mà bạn thêm từ kho mã của nhà phát hành. Grok Bot cài đặt skill khi bạn gửi liên kết thư mục GitHub của skill trong cuộc trò chuyện.