前端开发

21st-registry

21st-dev/skill

Publish your own work to 21st.dev and manage it from the terminal with the `21st` CLI (`@21st-dev/cli`): publish a React component to a team library, publish a CSS theme or a template listing, edit / unpublish / delete your published items, list and reopen existing component work, and read/replace your public profile page (bento board). Triggers when the user says "publish/share/upload this to 21st", "залей в наш регистр", "опубликуй компонент/тему/темплейт", "share with team", "make this reusable", "unpublish/edit/delete my component", "change its visibility", "find/open my old component or draft", "найди/открой мой старый компонент или драфт", "add this to my 21st profile/bento", "update my profile page", "обнови мой профиль на 21st", "добавь блок в бенто", "add controls/knobs to my demo", "сделай демо с контролами". For finding and installing existing items use `21st-cli-use`; for turning a project's design tokens into a theme use `21st-design-sync`.

  • 1877 次安装
  • 31 星标
  • 收录于

安装命令

npx skills add https://github.com/21st-dev/skill --skill 21st-registry

SKILL.md

Publish & manage on the 21st registry

Publish components, themes and templates to 21st.dev, and manage what you've already published, all through the unified 21st CLI (@21st-dev/cli).

Pre-flight (always)

  1. Authenticate before publishing. Component publishing, inventory, checkout, metadata editing, and unpublishing accept either a 21st login session or a 21st_sk_… API key. Theme/template commands still require a real API key from https://21st.dev/settings/api-keys, passed via --api-key, TWENTYFIRST_TOKEN, or API_KEY_21ST.
  2. The CLI is the unified @21st-dev/cli (bin 21st). Don't reinvent — use it.
  3. Search before publishing (21st search "<query>") so you don't add a duplicate to the library.

Find existing components and drafts

Publish & manage on the 21st registry

Publish components, themes and templates to 21st.dev, and manage what you've already published, all through the unified 21st CLI (@21st-dev/cli).

Pre-flight (always)

  1. Authenticate before publishing. Component publishing, inventory, checkout, metadata editing, and unpublishing accept either a 21st login session or a 21st_sk_… API key. Theme/template commands still require a real API key from https://21st.dev/settings/api-keys, passed via --api-key, TWENTYFIRST_TOKEN, or API_KEY_21ST.
  2. The CLI is the unified @21st-dev/cli (bin 21st). Don't reinvent — use it.
  3. Search before publishing (21st search "<query>") so you don't add a duplicate to the library.

Find existing components and drafts