astro-content

Solid

Use when managing structured content, blog posts, or typed data collections in Astro via the Content Layer API (content.config.ts).

Web & Frontend 25 stars 4 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
47
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

<objective> Implements Astro's Content Layer API: the `src/content.config.ts` config file, built-in `glob()` and `file()` loaders for local Markdown/MDX/JSON/YAML content, custom loaders for remote APIs/CMS/databases, Zod 4 schemas for type-safe frontmatter, and the query APIs `getCollection()`, `getEntry()`, and `render()` (which returns a `Content` component plus headings). Also covers MDX authoring with Remark/Rehype plugins and the `astro sync` workflow for generating collection types. Does not cover form submission via Astro Actions (astro-actions) or SEO metadata generation from content (astro-seo) — those are handled by their own skills. </objective> # Astro Content Layer Expert Type-safe content management with loaders, Zod schemas, and the unified Content Layer API. ## Agent Workflow (MANDATORY) Before ANY implementation, spawn 3 agents in parallel, one `Agent` call each with a `name`: 1. **fuse-ai-pilot:explore-codebase** - Check existing collections, loaders, and content structure 2. **fuse-ai-pilot:research-expert** - Verify latest Content Layer docs via Context7/Exa 3. **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 conte...

Details

Author
fusengine
Repository
fusengine/agents
Created
8 months ago
Last Updated
6 days ago
Language
CSS
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category