Skip to main content
prompt GP ChatGPT

Astro Content Site taste — ChatGPT prompt: what it does

The Astro Content Site taste ChatGPT prompt sets out development rules for content sites built with Astro. It covers rendering, images, SEO, and CI checks.

CC0-1.0 ★ 178,201 updated 2026-10-24

Open on GitHub

What Astro Content Site taste does

The prompt guides Astro projects for documentation, blogs, and marketing pages. It favors static pages, with server rendering reserved for routes that need fresh or user-specific data. JavaScript is added only for interactive parts, using island directives such as client:visible or client:idle where suitable.

Its rules cover Markdown and MDX collection schemas, page metadata, sitemaps, RSS, and redirects after a URL slug changes. For local images, it points to Astro’s built-in image component with explicit widths and modern formats. CI checks include astro check, strict TypeScript, link checking, and Lighthouse budgets; pull request previews are also part of the workflow.

Secrets belong in server code and should use typed environment variables without a public prefix. Claude Code lists .claude/commands/prompts.csv.md as its file path.

What it helps with

  • choose Astro or a full app framework for a content site
  • decide which components need interactive islands
  • validate Markdown and MDX files against a schema at build time
  • check links, accessibility, and SEO on pull requests
  • keep secrets confined to server-side code

Example prompts for the agent

  • Plan an Astro documentation site using these rules.
  • Design an Astro blog with static pages, an RSS feed, and a sitemap.
  • Review this Astro site plan for islands, metadata, and CI checks.

How to install Astro Content Site taste

How to use

Paste the text at the start of a chat or into project instructions

Questions about Astro Content Site taste

How do I install Astro Content Site taste in Claude Code?

Use the file .claude/commands/prompts.csv.md.

What does Astro Content Site taste do?

It provides rules for Astro content sites, covering static rendering, interactive islands, SEO metadata, and CI checks.

When does the prompt recommend server rendering in Astro?

For individual routes that need fresh or per-user data. It recommends static generation for pages that do not need that data.

Source text

prompts.csv · CC0-1.0
# Astro Content Site taste of a performance-minded web developer
- Use Astro for content-heavy sites like docs, blogs and marketing pages, and pick a full app framework only when most pages are interactive. Confidence: 0.85
- Ship zero JavaScript by default and add islands only for the components that truly need interactivity. Confidence: 0.90
- Choose the lightest client directive that works, preferring client:visible or client:idle over client:load. Confidence: 0.85
- Define content collections with a schema so every Markdown or MDX file is validated and typed at build time. Confidence: 0.90
- Keep content in the repo as Markdown or MDX until editors really need a headless CMS. Confidence: 0.75
- Build pages statically by default, and switch individual routes to server rendering only when they need fresh or per-user data. Confidence: 0.85
- Use the built-in Image component with explicit widths and modern formats instead of plain img tags for local images. Confidence: 0.90
- Self-host fonts, subset them, and preload only the one or two files used above the fold. Confidence: 0.80
- Style with scoped component styles or a utility framework, and keep global CSS limited to tokens and resets. Confidence: 0.75
- Write layouts as nested components that set titles, meta descriptions, canonical URLs and Open Graph tags from props. Confidence: 0.90
- Generate a sitemap and RSS feed from the content collections instead of maintaining them by hand. Confidence: 0.85
- Keep URLs stable and add redirects in config whenever a slug changes, so old links never return 404. Confidence: 0.90
- Use semantic HTML with one h1 per page, real headings in order, and alt text required by the content schema for images. Confidence: 0.90
- Use View Transitions sparingly for page navigation and respect prefers-reduced-motion. Confidence: 0.70
- Load third-party scripts like analytics and chat widgets late, or move them off the main thread with Partytown. Confidence: 0.75
- Keep framework islands in one UI library per site rather than mixing React, Vue and Svelte without a reason. Confidence: 0.80
- Run astro check and TypeScript in strict mode in CI so broken frontmatter and props fail the build. Confidence: 0.85
- Check every pull request with link checking and Lighthouse budgets for performance, accessibility and SEO. Confidence: 0.80
- Deploy previews for each pull request so writers and reviewers can read changes before they merge. Confidence: 0.85
- Add search with a static index like Pagefind before reaching for a hosted search service. Confidence: 0.75
- Read secrets only in server code through typed environment variables, and never expose them with a public prefix. Confidence: 0.95

© f · CC0-1.0 · f/prompts.chat

Similar prompts

All prompts for Frontend and UI →

From the same set218

The whole set →
Embedded Firmware taste Embedded Firmware taste — a prompt for ChatGPT that enforces reliability-minded engineering standards for embedded firmware development. GP ChatGPT ★ 178,201repo stars WebAssembly Module taste WebAssembly Module taste — a system prompt for ChatGPT, Claude.ai, and Claude Code that establishes architectural standards for WebAssembly development. It guides developers on performance and safety best practices. GP ChatGPT ★ 178,201repo stars Incident Response taste The Incident Response taste prompt for ChatGPT sets out how a calm on-call engineer can handle incidents. It calls for early declaration and coordinated response before the root cause is known. GP ChatGPT ★ 178,201repo stars Nix Dev Environment taste Nix Dev Environment taste — a prompt for ChatGPT configures reproducible Nix development environments with locked dependencies and container builds. GP ChatGPT ★ 178,201repo stars Phoenix App taste Phoenix App taste — a prompt for ChatGPT, Claude.ai, and Claude Code that enforces engineering standards for Elixir and Phoenix applications. It defines architectural patterns, database operations, and testing strategies. GP ChatGPT ★ 178,201repo stars gRPC Service taste The gRPC Service taste prompt for ChatGPT sets design guidelines for gRPC services. It covers .proto schemas, RPC methods, errors, and calls between services. GP ChatGPT ★ 178,201repo stars Spring Boot Service taste ChatGPT prompt Spring Boot Service taste defines architecture standards for Java backend engineering. GP ChatGPT ★ 178,201repo stars Full-Text Search taste Full-Text Search taste — a prompt for ChatGPT that sets out principles for building full-text search. It covers indexing, ranking, access control, and result delivery. GP ChatGPT ★ 178,201repo stars

Project sponsors

Companies that keep this analytics open