writing-registry-meta
Automates the creation of required .meta.json files for MUI Treasury component registries.
Install
mkdir -p .claude/skills/writing-registry-meta && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/160" && unzip -o skill.zip -d .claude/skills/writing-registry-meta && rm skill.zipInstalls to .claude/skills/writing-registry-meta
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when writing meta file for MUI Treasury registry.Key capabilities
- →Enforces JSON schema for registry component indexing
- →Standardizes naming conventions for registry items
- →Generates machine-readable interface documentation
- →Categorizes components into primitive or AI types
- →Configures container-level preview CSS classes
How it works
Validates and structures component information into a strict JSON format that the build tool uses to populate the registry index.
Inputs & outputs
When to use writing-registry-meta
- →Creating registry metadata for new UI components
- →Updating existing component documentation
- →Standardizing registry file formats
- →Preparing components for the registry index
About this skill
- The meta file must be in JSON format.
- The meta file must be located in the same directory as the registry file.
- The meta file must have the same name as the registry file, but with a .meta.json extension.
- The meta file must contain the following fields:
name: The registry name in kebab-case, same as file name without extension.title: The name of the registry usually the same as the component name in Pascal case.type: always"registry:item".description: IMPORTANT! Describe the registry in detail to help LLM understand what the interface looks like and its purpose. Start with "Integrated [library name]" if using third-party libraries (e.g., Base UI). Focus on visible features (buttons, labels, states) and accessibility. DO NOT list individual Material UI components.meta: Additional metadata about the registrycategory: one of "primitive", "ai"previewClassName: The extra class name to add to the preview container.
IMPORTANT! after writing/updating a meta file, run pnpm registry:build to populate the registry index.
When not to use it
- →General markdown documentation for standard code files
- →Projects not using the MUI Treasury registry system
Prerequisites
Limitations
- →Strict schema enforcement allows no flexibility in field naming
- →Requires manual post-update build command execution
- →Limited to describing UI components in a registry
How it compares
It is a rigid, rule-based schema generator designed specifically for machine discovery within a registry rather than generic documentation.
Compared to similar skills
writing-registry-meta side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| writing-registry-meta (this skill) | 5 | 7mo | No flags | Beginner |
| tsx | 0 | 2mo | Review | Beginner |
| React + Ant Design Frontend | 0 | 5mo | Review | Intermediate |
| new-component | 0 | 4mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by siriwatknp
View all by siriwatknp →You might also like
tsx
javimosch
TSX namespace for Netsnek e.U. TypeScript component toolkit. React component scaffolding, type-safe props, Storybook integration, and component docs.
React + Ant Design Frontend
daithang-organization
Complete guide for the SE104_VLEAGUE React frontend — pages, services, components, auth flow, i18n, and patterns
new-component
7sferry
Scaffold a new React component following project conventions
mcp-integration
Siamese001
Use this skill when choosing among repository-configured MCP servers, diagnosing MCP availability, or coordinating a cross-server workflow. Use adg-sqlite directly for structural dependency analysis.
nextjs-developer
zenobi-us
Expert Next.js developer mastering Next.js 14+ with App Router and full-stack features. Specializes in server components, server actions, performance optimization, and production deployment with focus on building fast, SEO-friendly applications.
zustand
lobehub
Zustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.