Skill

astro-content

Expert Astro Content Layer API — content.config.ts, glob/file loaders, custom loaders, getCollection, getEntry, render(), Zod schemas, MDX, Remark/Rehype plugins. Use when managing structured content, blog posts, or any typed data collections.

From fuse-astro

Install

Run in your terminal

npx claudepluginhub fusengine/agents --plugin fuse-astro

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

references/config.md

references/loaders.md

references/mdx.md

references/overview.md

references/querying.md

references/rendering.md

references/templates/blog-collection.md

references/templates/custom-loader.md

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Parent Repo Stars4

Parent Repo Forks0

Last CommitMar 17, 2026

Actions

View Source View Plugin View on GitHub View README

Astro Content Layer Expert

Type-safe content management with loaders, Zod schemas, and the unified Content Layer API.

Agent Workflow (MANDATORY)

Before ANY implementation, use TeamCreate to spawn 3 agents:

fuse-ai-pilot:explore-codebase - Check existing collections, loaders, and content structure
fuse-ai-pilot:research-expert - Verify latest Content Layer docs via Context7/Exa
mcp__context7__query-docs - Get loader and schema examples

After implementation, run fuse-ai-pilot:sniper for validation.

Overview

When to Use

Managing blog posts, docs, or product descriptions in Markdown/MDX
Fetching content from a CMS, API, or database with type safety
Needing TypeScript autocomplete for frontmatter fields
Migrating from Astro 4 legacy content collections

Why Content Layer API

Feature	Benefit
`src/content.config.ts`	Single config file at project root
Built-in loaders	`glob()` and `file()` for local files
Custom loaders	Fetch from any external source
Zod 4 schemas	Full TypeScript type safety
`astro sync`	Generates types from collections

Core Concepts

Config File Location

The config file moved from src/content/config.ts to src/content.config.ts in Astro 5+.

Collection Types

Loader	Use Case
`glob()`	Multiple files in a directory (MD, MDX, JSON, YAML)
`file()`	Single JSON/YAML file with multiple entries
Custom	Remote API, database, or any async data source

Key APIs

API	Description
`getCollection(name)`	Fetch all entries in a collection
`getEntry(name, id)`	Fetch a single entry by ID
`render(entry)`	Render a content entry to HTML + headings
`defineCollection()`	Define a collection with loader and schema

Reference Guide

Need	Reference
Overview & concepts	overview.md
Config file setup	config.md
Glob, file, custom loaders	loaders.md
getCollection / getEntry	querying.md
render() + headings	rendering.md
MDX + Remark/Rehype	mdx.md
Blog collection example	templates/blog-collection.md
Custom remote loader	templates/custom-loader.md

Best Practices

Always define schemas — Never skip Zod validation
Run astro sync — After changing content.config.ts
Use glob() for local files — Supports MD, MDX, JSON, YAML, TOML
Custom loaders for remote data — CMS, REST API, GraphQL
render() for MDX — Returns Content component + headings array