agentleFS
skeletonlabsskeletonlabs/skeleton/.agents/skills/create-playground-entry/SKILL.md

create-playground-entry

Skill6.1k starsChanged 4 days agoMITView on GitHub

Create or update Skeleton React and Svelte playground component pages for a given component, including route generation steps.

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.

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

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create playground pages for a component in one or both playground apps.

    line 8
  2. Very specific:

    Use this when a component needs a hands-on demo page under components/<slug> in:

    line 10
  3. Distinctive:

    If the component exists in only one framework, create only that framework's playground page.

    line 35
  4. Very specific:

    Import component(s) from @skeletonlabs/skeleton-react

    line 42
  5. Distinctive:

    Use matching demo structure with idiomatic Svelte syntax

    line 49
  6. Distinctive:

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

    line 59
  7. Distinctive:

    Ensure the route files compile in each target playground.

    line 70
  8. Distinctive:

    If requested, run checks:

    line 73

≈ “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 Playground Entry

Create playground pages for a component in one or both playground apps.

Use this when a component needs a hands-on demo page under components/<slug> in:

  • playgrounds/skeleton-react/
  • playgrounds/skeleton-svelte/

Where things live

  • React playground routes: playgrounds/skeleton-react/src/routes/components/
  • Svelte playground routes: playgrounds/skeleton-svelte/src/routes/components/
  • React route shell and nav list source: playgrounds/skeleton-react/src/routes/__root.tsx
  • Svelte route shell and nav list source: playgrounds/skeleton-svelte/src/routes/+layout.svelte

Important behavior

  • Both playgrounds auto-build the component nav from filesystem globs in their root layouts.
  • Adding a route file in the right folder is enough to make it appear in the sidebar.

File destination rules

Recommend destination from component slug and target framework(s), explain why, then accept overrides.

  • Component slug my-component:
    • React file: playgrounds/skeleton-react/src/routes/components/my-component/index.tsx
    • Svelte file: playgrounds/skeleton-svelte/src/routes/components/my-component/+page.svelte
  • Usually create both files for framework components.
  • If the component exists in only one framework, create only that framework's playground page.

Conventions (from existing playground entries)

  • Route folder is kebab-case and mirrors component slug.
  • React files:
    • Include 'use client';
    • Import component(s) from @skeletonlabs/skeleton-react
    • Export Route with createFileRoute('/components/<slug>/')
    • Define function Page() and return demo JSX
  • Svelte files:
    • Start with <script lang="ts">
    • Import component(s) from @skeletonlabs/skeleton-svelte
    • Exported route is filesystem-based (+page.svelte), no explicit route helper
    • Use matching demo structure with idiomatic Svelte syntax
  • Demo scope should be aligned across frameworks for parity.

Reference files:

  • Simple: playgrounds/skeleton-react/src/routes/components/accordion/index.tsx, playgrounds/skeleton-svelte/src/routes/components/accordion/+page.svelte
  • Multi-section: playgrounds/skeleton-react/src/routes/components/carousel/index.tsx, playgrounds/skeleton-svelte/src/routes/components/carousel/+page.svelte

Prompt flow

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

  1. Component slug - kebab-case route segment (for example floating-panel).
  2. Framework targets - react, svelte, or both (recommend both when the component exists in both packages).
  3. Demo scope - minimal single example or multi-section showcase.
  4. Feature coverage - list the states/variants/interactions to include.
  5. Parity level - strict parity or framework-idiomatic differences.
  6. Confirm - show planned files and summarize route/codegen actions before writing.

After scaffolding

  1. Ensure the route files compile in each target playground.
  2. Regenerate React route tree after new or renamed React route files:
    • pnpm --filter @skeletonlabs/playground-skeleton-react exec tsr generate
  3. If requested, run checks:
    • React: pnpm --filter @skeletonlabs/playground-skeleton-react run check
    • Svelte: pnpm --filter @skeletonlabs/playground-skeleton-svelte run check

Final summary

List: framework targets, files created/updated, whether React route generation was run, and any intentional parity differences between React and Svelte demos.

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.