registry
Skill755 starsChanged 2 months agoMITView on GitHub
Add or change simple-ai registry items. Dual generate (GitHub + hosted /r), generate:check, mocked gallery and chat-page, ui/_registry.ts + examples, block folders. Load before editing packages/registry or apps/docs/public/r.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- JetBrains/intellij-communitytheir own version, first seen Nov 13, 2026
- JetBrains/MPStheir own version, first seen Nov 3, 2026
- Kairos-commu/socletheir own version, first seen Oct 22, 2026
- DetachHead/rebasedtheir own version, first seen Oct 8, 2026
- YevheniiVolosiuk/the-registrytheir own version, first seen May 12, 2026
- xeeva/Genesistheir own version, first seen Mar 29, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- JetBrains/intellij-community★ 21ksame name
- DetachHead/rebased★ 6.5ksame name
- JetBrains/MPS★ 1.7ksame name
- xeeva/Genesis★ 17same name
- frames-engineering/skills★ 4same name
- Kairos-commu/socle★ 2same name
- YevheniiVolosiuk/the-registry★ 0same 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 repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- architectureSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
After changing anything under packages/registry/registry/:
- Very specific: line 17
Commit all of: registry.json, packages/registry/src/generated.ts, apps/docs/public/r.
- Very specific: line 27
Do not add demos to registry.json.
- Very specific: line 32
If the item has docs or envVars, keep them aligned with apps/docs/content/docs/installation.mdx.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Registry
Generate
After changing anything under packages/registry/registry/:
pnpm --filter @workspace/registry generate
pnpm --filter @workspace/registry generate:checkCommit all of: registry.json, packages/registry/src/generated.ts,
apps/docs/public/r. Do not hand-edit those outputs. generate:check diffs
all three and parses items with registryItemSchema from shadcn/schema.
Item source
- UI — one file in
packages/registry/registry/ui/<name>.tsxand a row inui/_registry.ts.item.files[].pathis relative toui/. - Demos —
packages/registry/registry/examples/<name>-demo.tsx. Docs only. Point at them withpreview(extensionless path underregistry/). Do not add demos toregistry.json. - Blocks —
packages/registry/registry/blocks/<name>/withitem.ts.item.files[].pathis relative to that directory.previewis the extensionless file inside the block folder.
If the item has docs or envVars, keep them aligned with
apps/docs/content/docs/installation.mdx.
Catalog
apps/docs/content/docs/components/meta.json is the public list. Items not on
that list can still exist as registry internals (shell, reasoning for
chat-page). Do not add docs pages for internals just because the item exists.
Gallery stays mocked
chat-page and the blocks gallery use the scripted mock. Do not point the docs
site at a live /api/chat. A consumer app can switch chat-transport.ts after
add; that is outside this repo's gallery.
Checks before a PR
pnpm --filter @workspace/registry generate
pnpm --filter @workspace/registry generate:check
pnpm typecheck
pnpm lint:checkDoes 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.

