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
Who's talking about skeletonlabs/skeleton
- storybookjs/storybook“[Bug]: Storybook + Tailwind does not load tailwind plugins”GitHub · Sep 22, 2023 · 6 reactions
- AdrianGonz97/vite-plugin-tailwind-purgecss“Fixed: Peer Dep versioning”GitHub · Dec 15, 2023 · 5 reactions
- A Hacker News story“Skeleton UI – v2.0 Release Candidate”Hacker News · Aug 15, 2023 · 3 points
- A Hacker News story“Skeleton v4.0 has launched (Tailwind-based component library)”Hacker News · Oct 14, 2025 · 2 points
- @htnabe.bsky.social“skeltonとかいうtailwindベースのCSSライブラリを見つけた ちょっと使ってみたさがある github.com/skeletonlabs...”Bluesky · Jun 12, 2026 · 1 likes
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
- Sep 22, 2023[Bug]: Storybook + Tailwind does not load tailwind plugins — storybookjs/storybook6 reactions · 10 comments
- Dec 15, 2023Fixed: Peer Dep versioning — AdrianGonz97/vite-plugin-tailwind-purgecss5 reactions · 2 comments
- Feb 12, 2025Superforms + Skeleton V3 modals [maybe minor doc update] — ciscoheat/sveltekit-superforms1 reaction · 1 comment
- Oct 23, 2024Svelte: Combobox $state.frozen is now $state.raw — chakra-ui/zag1 reaction
- Oct 26, 2023Faux Italic and Faux Bold Issue in iPhone Safari — skeletonlabs/create-skeleton-app1 reaction · 3 comments
45 more on GitHub
- Nov 13, 2026chore(deps-dev): bump @skeletonlabs/skeleton from 3.2.2 to 5.0.4 — synyx/kudos0 reactions
- Nov 13, 2026chore(deps-dev): bump @skeletonlabs/skeleton-svelte from 1.5.3 to 5.0.4 — synyx/kudos0 reactions
- Nov 13, 2026fix(deps): bump the web group in /svelte with 8 updates — FreezeManny/FSTouchCompanion0 reactions
- Nov 13, 2026fix(deps-dev): bump @skeletonlabs/skeleton from 5.0.1 to 5.0.4 in /fsConnect/frontend in the companion-web group — FreezeManny/FSTouchCompanion0 reactions
- Nov 13, 2026chore(deps-dev): bump the skeleton group with 2 updates — akiomik/nosey0 reactions · 1 comment
- Nov 12, 2026build(deps): bump the minor-and-patch group across 1 directory with 21 updates — xoxd-ai/scheduling-bridge.tinyland.dev0 reactions
- Nov 12, 2026dependabot: bump the minor-and-patch group across 1 directory with 2 updates — mirasen-io/cloudflare-site0 reactions · 3 comments
- Nov 12, 2026chore(deps-dev): bump @skeletonlabs/skeleton from 5.0.1 to 5.0.4 — br1ansouza/portfolio-v30 reactions
- Nov 10, 2026chore(deps-dev): bump @skeletonlabs/skeleton from 2.11.0 to 5.0.1 — NathanielBrewer/svelte-sveltkit-template0 reactions
- Nov 10, 2026chore(deps-dev): bump the frontend group across 1 directory with 2 updates — NathanielBrewer/svelte-sveltkit-template0 reactions
- Nov 3, 2026Bump the node-deps group across 1 directory with 30 updates — RosstheRoss/trinkets0 reactions · 3 comments
- Oct 26, 2026[pnpm] Bump @skeletonlabs/skeleton-svelte from 1.5.1 to 5.0.1 — hms-dbmi/PIC-SURE-Frontend0 reactions · 4 comments
- Oct 14, 2026feat(sveltekit): migrate SVForge templates and tooling to SvelteKit 3 — lelabdev/svforge0 reactions
- Oct 10, 2026Adopt Changesets for package versions, changelogs and release PRs — lelabdev/svforge0 reactions
- Oct 10, 2026Automate Changesets stable releases and npm canary snapshots — lelabdev/svforge0 reactions · 1 comment
- Sep 13, 2026build(deps-dev): bump @skeletonlabs/skeleton-svelte from 4.15.2 to 5.0.0 — rabbit-will-run/astro-charts0 reactions
- Aug 29, 2026Bump @skeletonlabs/skeleton from 3.2.2 to 5.0.1 in /psp-ui — oMaN-Rod/palstudio0 reactions
- Aug 29, 2026Bump @skeletonlabs/skeleton-svelte from 1.5.3 to 5.0.1 in /psp-ui — oMaN-Rod/palstudio0 reactions
- Aug 28, 2026Bump @skeletonlabs/skeleton-svelte from 5.0.0 to 5.0.1 in /extension — alexeyfv/slopless0 reactions
- Aug 28, 2026Bump @skeletonlabs/skeleton from 5.0.0 to 5.0.1 in /extension — alexeyfv/slopless0 reactions
- Jul 24, 2026chore(deps-dev): bump @skeletonlabs/skeleton from 2.11.0 to 5.0.0 — Sub-organization-maternal-mind/UBAG0 reactions
- Jul 21, 2026Bump the frontend group across 1 directory with 3 updates — BreathCodeFlow/t3lang0 reactions · 1 comment
- Jul 20, 2026Bump @skeletonlabs/skeleton-svelte from 1.5.1 to 5.0.0 — simmons-tech/new-simmons0 reactions · 1 comment
- Jul 20, 2026Bump @skeletonlabs/skeleton from 3.2.2 to 5.0.0 — simmons-tech/new-simmons0 reactions · 1 comment
- Jul 19, 2026build(deps): Bump the frontend group across 1 directory with 3 updates — beardcoder/t3lang0 reactions · 1 comment
- Jul 15, 2026build(deps-dev): bump @skeletonlabs/skeleton from 3.2.2 to 4.15.2 in /ui — JunesuChoi/Palworld-save-pal-rust-KR-0 reactions
- Jun 14, 2026Bump @skeletonlabs/skeleton-svelte from 1.5.3 to 4.15.2 — BCYCAData/soc-dev0 reactions · 1 comment
- Jun 14, 2026Bump @skeletonlabs/skeleton from 3.2.2 to 4.15.2 — BCYCAData/soc-dev0 reactions · 1 comment
- Jun 8, 2026Bump @skeletonlabs/skeleton from 2.11.0 to 4.15.2 — Fraser-Chapman/qr-code-utils0 reactions
- May 25, 2026Implement baseline blocks — skeletonlabs/skeleton-plus-free0 reactions
- Apr 13, 2026chore(deps-dev): bump @skeletonlabs/skeleton from 4.15.1 to 4.15.2 in /sveltekit-embed/template — arielsrv/recipes0 reactions · 1 comment
- Feb 28, 2026chore(deps-ui): bump svelte, @skeletonlabs/skeleton, @sveltejs/kit and svelte-check in /ui — ebarped/sego0 reactions · 1 comment
- Jan 2, 2026build(deps): bump @skeletonlabs/skeleton-svelte from 4.8.0 to 4.9.0 — DerTyp7214/synara-electron0 reactions
- Jan 2, 2026build(deps): bump @skeletonlabs/skeleton from 4.8.0 to 4.9.0 — DerTyp7214/synara-electron0 reactions
- Dec 31, 2025Carousel component is non-functional in RTL mode — chakra-ui/zag0 reactions · 2 comments
- Oct 30, 2025chore(deps-dev): bump @skeletonlabs/skeleton-svelte from 1.2.1 to 4.2.2 — jarpex/ssdlc-svelte-frontend0 reactions
- Oct 27, 2025chore(deps-dev): bump @skeletonlabs/skeleton-svelte from 1.5.3 to 4.1.5 — CristiCriss17G/ESP32-SMS-Sender-Control-App0 reactions
- Oct 27, 2025Bump @skeletonlabs/skeleton from 2.11.0 to 4.1.5 — Fraser-Chapman/valentines-20250 reactions
- Oct 27, 2025Bump @skeletonlabs/skeleton-svelte from 1.4.0 to 4.1.5 — ST2Projects/vizgraph0 reactions · 1 comment
- Oct 27, 2025chore(deps-dev): bump @skeletonlabs/skeleton-svelte from 1.5.3 to 4.1.5 — mistersilver-uk/fabricate-legacy0 reactions · 1 comment
- Oct 17, 2025Svelte class props not properly merged in `mergeProps` — chakra-ui/zag0 reactions · 1 comment
- Apr 28, 2025Bump @skeletonlabs/skeleton from 2.11.0 to 3.1.3 — strangelightstudios/cuddlepuff0 reactions · 1 comment
- Mar 12, 2025Migrate to stable Skeleton v3 — Mesnage-Org/glam0 reactions · 2 comments
- Feb 25, 2025Migrate Skeleton to RC2 + Tailwind v4 — SnotyMe/snoty-frontend0 reactions · 1 comment
- Jan 17, 2025Svelte Adapter is broken for DatePicker component — chakra-ui/zag0 reactions
On Hacker News · 2
- Aug 15, 2023Skeleton UI – v2.0 Release Candidate3 points
- Oct 14, 2025Skeleton v4.0 has launched (Tailwind-based component library)2 points
On Bluesky · 1
- Jun 12, 2026skeltonとかいうtailwindベースのCSSライブラリを見つけた ちょっと使ってみたさがある github.com/skeletonlabs... — @htnabe.bsky.social1 likes and repost
In this repository4 other files it gives its agents.
- create-docSkill
- create-exampleSkill
- create-playground-entrySkill
- create-tailwind-utilitySkill
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
- Distinctive: line 22
Use existing components as implementation references:
- Distinctive: line 45
Create the following in each framework package:
- Distinctive: line 69
Always mirror APIs across frameworks:
- Distinctive: line 144
Ask one question at a time.
- Distinctive: line 175
Before writing files, show:
- Distinctive: line 182
Wait for confirmation before scaffolding.
- Distinctive: line 188
Add component re-exports to:
- Distinctive: line 192
Keep ordering consistent with neighboring entries.
- Distinctive: line 196
Add tests for every framework package.
- Distinctive: line 216
Add the component to each corresponding playground package:
- Distinctive: line 222
Update generated docs by running:
≈ “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.
Files
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.tsindex.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.tstype exports reference.jsxpaths- 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-scopedata-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:
ProviderContextuseX- 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 generateinside:
packages/docs5. Optional docs scaffolding
If requested, trigger:
/create-docusing 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
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
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.

