// Scaffold a new documentation page for the Skeleton documentation site (sites/skeleton.dev), including frontmatter, optional boilerplate, examples, and API reference.
| name | create-doc |
| description | Scaffold a new documentation page for the Skeleton documentation site (sites/skeleton.dev), including frontmatter, optional boilerplate, examples, and API reference. |
Scaffold a new .mdx documentation page for sites/skeleton.dev/ (Astro + MDX).
docs collection<Preview>, <Framework>, <ApiReference> are globally available in MDX (no import needed)| Category | Reference page to model after |
|---|---|
framework-components/ | accordion.mdx — Default + per-feature sections + Anatomy + API Reference |
tailwind-components/ | buttons.mdx — Default .astro + per-feature sections |
tailwind-utilities/ | presets.mdx — utility class doc with <Preview> examples per variant |
design/ | colors.mdx — long-form prose with summary |
get-started/ | introduction.mdx |
guides/ | mode.mdx |
integrations/ | melt-ui.mdx — <Process> + linker CTAs |
resources/ | llms.mdx |
Match the structure of the reference page for the chosen category.
Filename and title must be derived from the source artifact, never invented. Recommend the derived name, explain the source, accept overrides.
packages/skeleton-{framework}/src/components/{ComponentName}. Accordion → accordion.mdx, title Accordion. If the component doesn't exist yet, flag this — user may need /create-component first.@btn lives in buttons.css → buttons.mdx, title Buttons. Plural CSS filename verbatim.presets.css → presets.mdx, title Presets. Use this category for cross-cutting utility classes (Presets, etc.) rather than discrete component blocks.Ask one at a time, confirm each answer, write nothing until all are answered and the user confirms.
<category>/<slug>.mdx per naming conventions, explain the derivation, surface the typography/forms exception when relevant. Allow override.Default as the first). Per example, infer the type from the parent category — don't re-prompt: tailwind pages → .astro; framework pages → react + svelte pair. Note any exceptions the user mentions (e.g. "make group framework-specific on a tailwind page").<ApiReference id="<framework>/<slug>" /> blocks (see accordion.mdx). The id must match an entry in the components collection loader; warn if the component isn't registered yet.linker CTA, summary/order/stability overrides, references URLs, cross-links.See content.config.ts for the full schema. Required: title, description. Useful optionals: summary, order, stability, references.{source,styles,a11y,zag}.
Refer to the /create-example skill for general best practices. Avoid the prompt-flow for each example as this could be tedious. Just use your best judgement from the information received and the skill spec.
After writing files, list: page path, examples handed to /create-example, anything needing manual follow-up (e.g. component registration for <ApiReference>, asset imports, populating example bodies).
Create framework components across all supported packages using the repository's anatomy/modules conventions.
Create or update Skeleton React and Svelte playground component pages for a given component, including route generation steps.
Scaffold a new Tailwind utility (CSS-only utility class) in the Skeleton core package, following @utility conventions used by buttons, badges, cards, etc.
Scaffold an example file (Astro or framework-specific) for a Skeleton documentation page, including the MDX import wiring and Preview/Framework blocks.