agentleFS
skeletonlabsskeletonlabs/skeleton/.agents/skills/create-doc/SKILL.md

create-doc

Skill6.1k starsChanged 4 days agoMITView on GitHub

Scaffold a new documentation page for the Skeleton documentation site (sites/skeleton.dev), including frontmatter, optional boilerplate, examples, and API reference.

2 other projects use a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 2 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 1 mentionMay 2026: 1 mentionJun 2026: 4 mentionsJul 2026: 6 mentionsAug 2026: 4 mentionsSep 2026: 1 mentionOct 2026: 4 mentionsNov 2026: 11 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the skeletonlabs/skeleton repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about skeletonlabs/skeleton

The biggest 5 of 53 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 53

Talked about on GitHub, Hacker News and Bluesky (53 times).

On GitHub · 50

45 more on GitHub
  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. avibebuilder/claude-prime★ 119same name
    2. DGouron/review-flow★ 44same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask one at a time, confirm each answer, write nothing until all are answered and the user confirms.

    line 44
  2. Very specific:

    After writing files, list: page path, examples handed to /create-example, anything needing manual follow-up (e.g.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create Doc

Scaffold a new .mdx documentation page for sites/skeleton.dev/ (Astro + MDX).

Where things live

  • Pages: sites/skeleton.dev/src/content/docs/
  • Examples (mirrors docs structure): sites/skeleton.dev/src/components/examples/
  • Frontmatter schema (Zod): sites/skeleton.dev/src/content.config.ts — docs collection
  • <Preview>, <Framework>, <ApiReference> are globally available in MDX (no import needed)

Categories

CategoryReference 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.

Naming conventions

Filename and title must be derived from the source artifact, never invented. Recommend the derived name, explain the source, accept overrides.

  • Framework Components — derived from 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.
  • Tailwind Components — derived from the CSS filename. @btn lives in buttons.css → buttons.mdx, title Buttons. Plural CSS filename verbatim.
  • Tailwind Utilities — derived from the CSS filename of the utility set. presets.css → presets.mdx, title Presets. Use this category for cross-cutting utility classes (Presets, etc.) rather than discrete component blocks.
  • Tailwind exceptions (no new page) — typography utilities go into design/typography.mdx; form/input fields go into tailwind-components/forms.mdx. Recommend extending those instead of creating a new page.
  • All other categories — kebab-case slug from the topic, Title Case title.

Prompt flow

Ask one at a time, confirm each answer, write nothing until all are answered and the user confirms.

  1. Topic — title and one-line description.
  2. Destination — recommend <category>/<slug>.mdx per naming conventions, explain the derivation, surface the typography/forms exception when relevant. Allow override.
  3. Boilerplate vs blank — blank = frontmatter only; boilerplate = match the category reference page.
  4. Examples — collect a list of example names (always include 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").
  5. API Reference — append <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.
  6. Other notes — linker CTA, summary/order/stability overrides, references URLs, cross-links.

Frontmatter

See content.config.ts for the full schema. Required: title, description. Useful optionals: summary, order, stability, references.{source,styles,a11y,zag}.

Examples

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.

Final summary

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).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.