How to write the per-plugin documentation pages for the atomic-payload (@pro-laico/*) project — the docs/content/docs/plugins/*.mdx pages on the Fumadocs site. Use whenever creating, rewriting, or reviewing a plugin doc page. Covers the plain-language, benefit-first tone for a surface-level Payload/Next/React reader; the full page structure (intro → installation → setup walkthrough → using it in your app → options → environment variables → exports → related); the Fumadocs components to use; and the rule to ground every setup/frontend step in the real package source and the templates/atomic-payload template rather than inventing it. Trigger when documenting or editing any @pro-laico plugin's docs page, even when the user just says "document this plugin", "the plugin docs are incomplete", or "fix the setup section".
The shared, docs-wide guide for the Atomic Payload (@pro-laico/*) documentation site — the Fumadocs project under docs/. Use whenever creating, editing, or reviewing ANY docs/content/docs/**/*.mdx page. Covers the conventions every doc type shares — frontmatter, meta.json navigation, the plain benefit-first tone for a surface-level Payload/Next/React reader, the Fumadocs components to use, Shiki-safe code fences, link rules, and grounding content in real source — and maps each doc type to its focused companion skill (ap-docs-guide-plugin / -feature / -concept / -getting-started / -example / -template / -contributing). Trigger for any docs-site editing, even when the user just says "fix the docs" or "write a docs page"; then also read the matching type skill for that page's structure.
How to write the Core Concepts pages for the Atomic Payload docs — docs/content/docs/concepts/*.mdx (architecture, kernel, type-augmentation, caching, slugs). Use when creating, editing, or reviewing a concept page. These explain how Atomic Payload is built and why, for readers who want the mental model rather than a procedure. Builds on the ap-docs-guide skill for shared conventions.
How to write the Contributing pages for the Atomic Payload docs — docs/content/docs/contributing/*.mdx (index, releasing). Use when creating, editing, or reviewing contributor/maintainer docs. Unlike the rest of the site, these address people working ON the monorepo (its layout, local dev, the plugin shape, releasing/publishing), not people using the plugins. Builds on the ap-docs-guide skill for shared conventions.
How to write the Example app pages for the Atomic Payload docs — docs/content/docs/examples/*.mdx (fonts-only, icons-only, styles-only). Use when creating, editing, or reviewing an example page. These document the minimal demo apps that exercise ONE standalone plugin in isolation. Builds on the ap-docs-guide skill for shared conventions.
How to write the Feature guide pages for the Atomic Payload docs — docs/content/docs/features/*.mdx (styles, actions, forms, icons, media, fonts, site, tracking, atomic-blocks, seeding). Use when creating, editing, or reviewing a feature page. These are the friendly "what it does / how it works / how to use it" capability guides, each paired with a plugin reference page. Builds on the ap-docs-guide skill for shared conventions (frontmatter, tone, components, fences, links).
How to write the Getting Started pages for the Atomic Payload docs — docs/content/docs/getting-started/*.mdx (quick-start, existing-project, environment, project-structure). Use when creating, editing, or reviewing a getting-started page. These are procedural, do-this-then-that guides that land the reader on a working project. Builds on the ap-docs-guide skill for shared conventions.
How to write the Template pages for the Atomic Payload docs — docs/content/docs/templates/*.mdx (atomic-payload). Use when creating, editing, or reviewing the starter-template guide. This documents the full Payload + Next.js + Tailwind starter that wires up every plugin — setup, environment, deployment, and optional integrations. Builds on the ap-docs-guide skill for shared conventions.