Fumadocs Registry Integration

CommunityPopular

TheOrcDev

fumadocs-registry-integration

Register 8-bit components in registry.json for shadcn/ui add command. Apply when adding new components to the component library distribution.

Overview

Publisher	TheOrcDev
Repository	`8bitcn-ui`
Skill name	`fumadocs-registry-integration`
Stars	2K
Forks	121
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by TheOrcDev on GitHub. Read the source before you install it.

Installation

Install the Fumadocs Registry Integration AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/TheOrcDev/8bitcn-ui/tree/main/.claude/skills/fumadocs-registry-integration
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/TheOrcDev/8bitcn-ui/tree/main/.claude/skills/fumadocs-registry-integration

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/TheOrcDev/8bitcn-ui.git /tmp/8bitcn-ui
mkdir -p .claude/skills
cp -r /tmp/8bitcn-ui/.claude/skills/fumadocs-registry-integration .claude/skills/fumadocs-registry-integration

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Fumadocs Registry Integration in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Fumadocs Registry Integration on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Fumadocs Registry Integration is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Registry Integration

Component Entry Pattern

json
{
  "name": "button",
  "type": "registry:component",
  "title": "8-bit Button",
  "description": "A simple 8-bit button component",
  "registryDependencies": ["button"],
  "files": [
    {
      "path": "components/ui/8bit/button.tsx",
      "type": "registry:component",
      "target": "components/ui/8bit/button.tsx"
    },
    {
      "path": "components/ui/8bit/styles/retro.css",
      "type": "registry:component",
      "target": "components/ui/8bit/styles/retro.css"
    }
  ]
}

Block Entry Pattern

For pre-built layouts like game UIs:

json
{
  "name": "quest-log",
  "type": "registry:block",
  "title": "8-bit Quest Log",
  "description": "An 8-bit quest and mission tracking system.",
  "registryDependencies": ["card", "accordion"],
  "categories": ["gaming"],
  "files": [
    {
      "path": "components/ui/8bit/quest-log.tsx",
      "type": "registry:block",
      "target": "components/ui/8bit/quest-log.tsx"
    },
    {
      "path": "components/ui/8bit/styles/retro.css",
      "type": "registry:component",
      "target": "components/ui/8bit/styles/retro.css"
    }
  ]
}

Required retro.css

Always include retro.css in files array:

json
"files": [
  {
    "path": "components/ui/8bit/new-component.tsx",
    "type": "registry:component",
    "target": "components/ui/8bit/new-component.tsx"
  },
  {
    "path": "components/ui/8bit/styles/retro.css",
    "type": "registry:component",
    "target": "components/ui/8bit/styles/retro.css"
  }
]

Registry Dependencies

List base shadcn dependencies (not 8-bit versions):

json
"registryDependencies": ["button", "dialog", "progress"]

For blocks with multiple components:

json
"registryDependencies": ["card", "button", "progress", "tabs"]

Type Selection

registry:component - Single reusable component:

json
{
  "type": "registry:component",
  "files": [...]
}

registry:block - Pre-built layout or feature:

json
{
  "type": "registry:block",
  "categories": ["gaming"],
  "files": [...]
}

Complete Example

json
{
  "name": "health-bar",
  "type": "registry:component",
  "title": "8-bit Health Bar",
  "description": "An 8-bit health bar component for game UI.",
  "registryDependencies": ["progress"],
  "files": [
    {
      "path": "components/ui/8bit/health-bar.tsx",
      "type": "registry:component",
      "target": "components/ui/8bit/health-bar.tsx"
    },
    {
      "path": "components/ui/8bit/progress.tsx",
      "type": "registry:component",
      "target": "components/ui/8bit/progress.tsx"
    },
    {
      "path": "components/ui/8bit/styles/retro.css",
      "type": "registry:component",
      "target": "components/ui/8bit/styles/retro.css"
    }
  ]
}

Key Principles

Type - Use registry:component for single, registry:block for layouts
retro.css required - Always include in files array
Target path - Same path for source and target
Categories - Use gaming for retro-themed blocks
Dependencies - List base shadcn/ui components (not 8-bit)
Description - Clear, concise for CLI output
Files order - Component first, retro.css last

Adding a New Component

Create component in components/ui/8bit/component.tsx
Create documentation in content/docs/components/component.mdx
Add entry to registry.json:
- Copy existing component as template
- Update name, title, description
- Set correct registryDependencies
- Include retro.css in files
Test: pnpm dlx shadcn@latest add @8bitcn/component

Reference

registry.json - Full component registry
content/docs/components/*.mdx - Component documentation

Frequently asked questions

What does the Fumadocs Registry Integration AI skill do?

Register 8-bit components in registry.json for shadcn/ui add command. Apply when adding new components to the component library distribution.

Why use Fumadocs Registry Integration on TypingMind?

Because you install it once and use it with any model. Fumadocs Registry Integration is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Fumadocs Registry Integration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/TheOrcDev/8bitcn-ui/tree/main/.claude/skills/fumadocs-registry-integration. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Fumadocs Registry Integration?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Fumadocs Registry Integration?

As many as you like. As long as a model supports skills, you can use Fumadocs Registry Integration with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Fumadocs Registry Integration AI skill free?

Yes. It is published on GitHub by TheOrcDev under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Sketch

NousResearch

OrganizationPopular

Throwaway HTML mockups: 2-3 design variants to compare.

Tldraw Offline

Drive and script tldraw offline canvases with an agent.

Brand Guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual…

Solid

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Registry Integration

Component Entry Pattern

Block Entry Pattern

Required retro.css

Categories

Registry Dependencies

Type Selection

Complete Example

Key Principles

Adding a New Component

Reference

Frequently asked questions

Related AI Skills

Set up your own AI workspace now