前端开发

beui

starc007/ui-components

Pick and install beUI (@beui) animated React components through public MCP or the shadcn registry. Use when building motion UI, agent/chat interfaces, toasts, docks, bottom sheets, drawers, popovers, sliders, loaders, 404 pages, or any beui.dev component. Maps user intent to exact @beui install slugs instead of inventing custom widgets.

  • 867 次安装
  • 1900 星标
  • 收录于

安装命令

npx skills add https://github.com/starc007/ui-components --skill beui

SKILL.md

beUI

Use beUI as copy-paste source through its public MCP or the @beui shadcn registry.

See the AI agents guide for current connection instructions and endpoints. The public MCP at https://mcp.beui.dev/mcp needs no license key or Pro authentication. For licensed components, use the separate beui-pro skill and Pro connection.

Workflow

  1. Discover current components with the public MCP's list_components or search_components when connected. Otherwise, fetch the live registry:
curl -fsS https://beui.dev/r/registry.json
  1. For CLI installation, pick the closest install slug from items[].name in the live registry. Public MCP catalog slugs can name documentation pages with multiple installable variants. Do not assume every page slug is an install slug.
  2. Inspect the selected component with MCP get_component, or inspect an installable item through the CLI:

beUI

Use beUI as copy-paste source through its public MCP or the @beui shadcn registry.

See the AI agents guide for current connection instructions and endpoints. The public MCP at https://mcp.beui.dev/mcp needs no license key or Pro authentication. For licensed components, use the separate beui-pro skill and Pro connection.

Workflow

  1. Discover current components with the public MCP's list_components or search_components when connected. Otherwise, fetch the live registry:
curl -fsS https://beui.dev/r/registry.json
  1. For CLI installation, pick the closest install slug from items[].name in the live registry. Public MCP catalog slugs can name documentation pages with multiple installable variants. Do not assume every page slug is an install slug.
  2. Inspect the selected component with MCP get_component, or inspect an installable item through the CLI: