nuxt-content

Use when working with Nuxt Content v3, markdown content, or CMS features in Nuxt - provides collections (local/remote/API sources), queryCollection API, MDC rendering, database configuration, NuxtStudio integration, hooks, i18n patterns, and LLMs integration

683stars33forksUpdated 6/22/2026

Web Development Documentation #cms #nuxt #markdown #content-management #typescript #vue

Security Assessment

Medium Risk(50/100)

Detected risks:

Secret Exposure([references/studio.md] TOKEN=, [references/config.md] TOKEN=)

Sensitive File Access([references/collections.md] .env, [references/studio.md] .env, [references/config.md] .env)

Security Score50/100

About nuxt-content

The nuxt-content skill provides comprehensive guidance for building content-driven applications using Nuxt Content v3. It helps developers implement typed content collections, configure SQL-backed content queries, and integrate markdown rendering with Vue components. This skill addresses the complexity of managing structured content in modern Nuxt applications by offering progressive guidance through collections, remote sources, and database configurations.

Key capabilities include setting up content collections with schema validation using Zod, querying content through a SQL-like fluent API, rendering MDC (Markdown Components) with Vue integration, and configuring various database backends including SQLite, PostgreSQL, D1, and LibSQL. The skill also covers remote content sources from GitHub repositories or external APIs, content hooks for transformation pipelines, and integration with NuxtStudio for live editing and preview modes.

This skill is designed for Nuxt developers building blogs, documentation sites, headless CMS implementations, or any content-heavy application requiring structured data management. It's particularly valuable for teams working with multi-language content through i18n patterns, implementing content search and navigation features, or integrating LLMs for content generation. The modular reference system allows developers to load only relevant documentation based on their current task, avoiding information overload.

FAQ

When should I use this skill instead of the document-writer or nuxt skills?

Use nuxt-content when working specifically with Nuxt Content v3 features like collections, queryCollection API, or MDC rendering. Use document-writer for creating documentation content itself, and use the nuxt skill for general Nuxt framework features unrelated to content management.

What database options are supported for content storage?

Nuxt Content v3 supports SQLite, PostgreSQL, Cloudflare D1, and LibSQL (Turso) as database backends. The configuration is handled through the config.md reference file.

How do I load content from external sources like GitHub?

Use source.repository for GitHub repositories or defineCollectionSource for custom API sources. The collections.md reference provides detailed guidance on configuring remote content sources.

What's the difference between 'page' and 'data' collection types?

Page collections include routes and markdown body content for rendering full pages, while data collections store structured data only without body content, useful for metadata, configuration, or API-like data.

Do I need to load all reference files at once?

No, load only the reference files relevant to your current task. For example, load collections.md when defining schemas, querying.md when implementing search, or rendering.md when working with ContentRenderer components.