Practical overview
When it fits
Use the registry when an AI-assisted UI workflow needs explicit visual, component, accessibility, writing, or quality-gate guidance drawn from a design system.
Who it is for
- Developers using AI coding tools who want UI generation guided by a selected design system.
- Design-system maintainers who need agent-readable rules alongside human-facing rationale.
- Teams seeking a documented starting point for packaging and contributing reusable design skills.
Documented uses
- Browse design-system skills and select one by slug.
- Pull a skill's agent instructions into configured tool locations.
- Preview intended file writes or target particular providers.
- Create a custom skill folder and prepare it for contribution.
Requirements & limits
The repository is public and MIT-licensed. The documented pull workflow uses the TypeUI CLI and npx.
- A skill consists of both SKILL.md agent instructions and a DESIGN.md human-facing companion.
- The CLI fetches SKILL.md into configured provider paths; DESIGN.md remains alongside the skill in the registry.
- The registry describes constraints and quality gates, but those instructions are not evidence that generated code meets them.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Pull a design skill into a project
Fetch a registry skill into the configured locations for selected AI tools.
Before you start
- Node.js package execution via npx
- The TypeUI CLI
- A skill slug from the registry
Steps
Use the CLI list command to browse available skills and preview links.
Run the command below to fetch a skill.
npx typeui.sh pullUse
-p cursor,claudeto target named providers, or--dry-runto preview the files that would be written.
Expected outcome
The CLI fetches the skill's SKILL.md into configured provider paths; the companion DESIGN.md remains in the registry.
Guide limitations
- The pull command fetches SKILL.md; DESIGN.md is retained in the registry for reference and maintenance.
- The dry-run option previews intended writes rather than making them.
Create and contribute a design skill
Add a custom design-system skill to the registry through the documented contribution process.
Before you start
- A slug for the skill folder
- A SKILL.md file and companion DESIGN.md
- An entry in skills/index.json
Steps
Create a folder under skills/ using the skill slug.
Add SKILL.md and DESIGN.md following the existing format.
Add the skill entry to skills/index.json.
Submit a pull request.
Expected outcome
A proposed skill is organized in the registry format and submitted for contribution.
Guide limitations
- The instructions describe submission by pull request, not acceptance or publication.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 10 October 2026
- Original website title
- bergside/awesome-design-skills · Official homepage title · retained in its source language

