agentleFS
skeletonlabsskeletonlabs/skeleton/.agents/skills/create-framework-component/SKILL.md

create-framework-component

Skill6.1k starsChanged 4 days agoMITView on GitHub

Create framework components across all supported packages using the repository's anatomy/modules conventions.

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

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use existing components as implementation references:

    line 22
  2. Distinctive:

    Create the following in each framework package:

    line 45
  3. Distinctive:

    Always mirror APIs across frameworks:

    line 69
  4. Distinctive:

    Ask one question at a time.

    line 144
  5. Distinctive:

    Before writing files, show:

    line 175
  6. Distinctive:

    Wait for confirmation before scaffolding.

    line 182
  7. Distinctive:

    Add component re-exports to:

    line 188
  8. Distinctive:

    Keep ordering consistent with neighboring entries.

    line 192
  9. Distinctive:

    Add tests for every framework package.

    line 196
  10. Distinctive:

    Add the component to each corresponding playground package:

    line 216
  11. Distinctive:

    Update generated docs by running:

    line 222

≈ “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 Framework Component

Scaffold a new component across all supported framework packages using the existing anatomy/modules authoring style and API conventions.

Repository Structure

This repository contains implementations for multiple frameworks. Unless otherwise specified, apply the same patterns, conventions, and API design consistently across all framework packages.

Component Sources

  • Components: packages/<framework>/src/components/
  • Component tests: packages/<framework>/test/components/
  • Public package exports: packages/<framework>/src/index.ts

Reference Components

Use existing components as implementation references:

  • Static / non-machine component:
    • packages/<framework>/src/components/app-bar/index.ts
  • Machine-backed component:
    • packages/<framework>/src/components/accordion/index.ts

Framework Packages

Available framework package directories include:

  • packages/skeleton-react/
  • packages/skeleton-svelte/

Replace <framework> with the appropriate package when navigating the repository.

File destination rules

Recommend structure based on component complexity, explain the reasoning, and accept overrides.

Simple / Static component

Create the following in each framework package:

  • anatomy/*
  • modules/anatomy.ts
  • index.ts

Machine-backed component

To view the documentation of a machine: https://zagjs.com/api/mdx/components/<framework>/<machine>

In addition to anatomy files, include provider/context modules as needed:

React

  • modules/provider.ts
  • Context and hook files as needed

Svelte

  • modules/provider.svelte.ts
  • Context and store files as needed

API consistency

Always mirror APIs across frameworks:

  • Namespace members
  • Part names
  • Prop interface names
  • Provider naming
  • Hook/composable naming
  • Context exports

Conventions

Based on the existing app-bar, accordion, and dialog implementations.

Naming

  • Folder names use kebab-case:
    • app-bar
  • Exported namespaces use PascalCase:
    • AppBar

File organization

Maintain the anatomy/modules split:

anatomy/*

Renderable component parts only.

modules/*

Context, providers, namespace composition, machines, and framework glue.

index.ts

Type exports and namespace exports only.

React conventions

  • Anatomy files use .tsx
  • index.ts type exports reference .jsx paths
  • Use PropsWithElement + HTMLAttributes
  • Build attributes with mergeProps
  • Support element override fallback patterns

Svelte conventions

  • Anatomy files use .svelte
  • Interfaces live in <script lang="ts" module>
  • Maintain prop and slot parity with React where possible

Namespace composition

Compose namespaces using:

Object.assign(Root, {
	...parts,
});

Inside:

  • modules/anatomy.ts

Static anatomy parts

Include:

  • data-scope
  • data-part

attributes on all renderable anatomy parts.

Prompt flow

Ask one question at a time. Confirm each step. Do not generate files until all answers are confirmed.

1. Component name

Determine:

  • kebab-case folder name
  • PascalCase namespace

Recommend both and accept overrides.

2. Component type

Determine whether the component is:

  • Static/simple
  • Machine-backed (Zag or equivalent)

This determines required module/provider files.

3. Public exports

Determine whether to expose:

  • Provider
  • Context
  • useX
  • Other framework-specific hooks/composables

4. Confirmation

Before writing files, show:

  • Planned file tree for every framework
  • Planned namespace API
  • Provider/context structure
  • Public exports

Wait for confirmation before scaffolding.

After scaffolding

1. Root exports

Add component re-exports to:

  • packages/<framework>/src/index.ts

Keep ordering consistent with neighboring entries.

2. Tests

Add tests for every framework package.

Test files

  • Fixture:
    • packages/<framework>/test/components/<component>.<ext>
  • Suite:
    • packages/<framework>/test/components/<component>.test.<ext>

Test coverage requirements

For every anatomy part:

  • Include render assertions (toBeInTheDocument)
  • Validate namespace exports
  • Validate prop delegation and attribute forwarding
  • Validate provider/context behavior where applicable

3. Playground integration

Add the component to each corresponding playground package:

  • playgrounds/skeleton-<framework>

4. Docs generation

Update generated docs by running:

pnpm generate

inside:

packages/docs

5. Optional docs scaffolding

If requested, trigger:

/create-doc

using the new component slug.

Final summary

Summarize:

  • Files created per framework
  • Namespace members exported
  • Provider/context/hook files added
  • Root index exports added
  • Playground updates
  • Test coverage added
  • Prop delegation coverage
  • Docs generation status

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.