typeui-cli
Guide for agentic tools to use the typeui.sh CLI for generating, updating, listing, and pulling design system skill files.
Best use case
typeui-cli is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Guide for agentic tools to use the typeui.sh CLI for generating, updating, listing, and pulling design system skill files.
Teams using typeui-cli should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/typeui-cli/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How typeui-cli Compares
| Feature / Agent | typeui-cli | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Guide for agentic tools to use the typeui.sh CLI for generating, updating, listing, and pulling design system skill files.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# typeui.sh CLI Operator Skill ## Mission Use `typeui.sh` to generate, update, list, and pull design-system skill files for agentic tooling in a project. ## When To Use This Skill - User asks to create or refresh design-system instructions for agents. - User wants to pull an existing style by slug. - User wants to browse available styles and select one interactively. - User asks for preview-only runs before writing files. ## Preconditions - Run commands from the target project root. - Node.js 18+ is available. - If running from this repository source, build first: - `npm install` - `npm run build` ## Command Reference - `npx typeui.sh generate` - Run interactive prompts and create new managed skill content. - `npx typeui.sh update` - Update existing managed sections in generated files. - `npx typeui.sh pull <slug>` - Pull a specific registry skill and write it to selected provider paths. - `npx typeui.sh list` - List available registry slugs, show preview links, and pull one selection. ## Local Dev Invocation (This Repo) - `node dist/cli.js --help` - `node dist/cli.js generate` - `node dist/cli.js update` - `node dist/cli.js list` - `node dist/cli.js pull <slug>` ## Shared Flags - `-p, --providers <providers>` - Comma-separated providers (example: `cursor,codex`). - `--dry-run` - Preview file changes without writing. ## Provider Behavior - Universal target is always included: `.agents/skills/design-system/SKILL.md`. - Selected providers add extra output targets (for example `.cursor/...`, `.codex/...`). ## Registry Behavior - Source of truth for list/pull data is: - `https://github.com/bergside/awesome-design-skills` - Registry index used by CLI: - `https://raw.githubusercontent.com/bergside/awesome-design-skills/main/skills/index.json` - `pull <slug>` flow: 1. Validate slug format. 2. Resolve `skillPath` from index. 3. Fetch markdown from the raw GitHub path. - `list` flow: - Reads the same index and shows preview links from: - `https://www.typeui.sh/design-systems/<slug>` ## Recommended Agent Workflow 1. If user knows the style: run `pull <slug> --dry-run` first. 2. If user does not know the style: run `list` and select one. 3. Re-run without `--dry-run` when preview looks correct. 4. Report generated/updated file paths and whether each changed. ## Troubleshooting - `Registry pull failed: not_found` - Slug is not in registry index or markdown path is missing. - Run `list` and pick a valid slug. - `Slug must contain only lowercase letters, numbers, dashes, or underscores` - Normalize slug format before retrying. - `No existing managed design system found` during `update` - Run `generate` first to create managed blocks.
Related Skills
workspace-surface-audit
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.
ui-demo
Record polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.
token-budget-advisor
Offers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: "token budget", "token count", "token usage", "token limit", "response length", "answer depth", "short version", "brief answer", "detailed answer", "exhaustive answer", "respuesta corta vs larga", "cuántos tokens", "ahorrar tokens", "responde al 50%", "dame la versión corta", "quiero controlar cuánto usas", or clear variants where the user is explicitly asking to control answer size or depth. DO NOT TRIGGER when: user has already specified a level in the current session (maintain it), the request is clearly a one-word answer, or "token" refers to auth/session/payment tokens rather than response size.
skill-comply
Visualize whether skills, rules, and agent definitions are actually followed — auto-generates scenarios at 3 prompt strictness levels, runs agents, classifies behavioral sequences, and reports compliance rates with full tool call timelines
santa-method
Multi-agent adversarial verification with convergence loop. Two independent review agents must both pass before output ships.
safety-guard
Use this skill to prevent destructive operations when working on production systems or running agents autonomously.
repo-scan
Cross-stack source code asset audit — classifies every file, detects embedded third-party libraries, and delivers actionable four-level verdicts per module with interactive HTML reports.
project-flow-ops
Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.
product-lens
Use this skill to validate the "why" before building, run product diagnostics, and pressure-test product direction before the request becomes an implementation contract.
openclaw-persona-forge
为 OpenClaw AI Agent 锻造完整的龙虾灵魂方案。根据用户偏好或随机抽卡， 输出身份定位、灵魂描述(SOUL.md)、角色化底线规则、名字和头像生图提示词。 如当前环境提供已审核的生图 skill，可自动生成统一风格头像图片。 当用户需要创建、设计或定制 OpenClaw 龙虾灵魂时使用。 不适用于：微调已有 SOUL.md、非 OpenClaw 平台的角色设计、纯工具型无性格 Agent。 触发词：龙虾灵魂、虾魂、OpenClaw 灵魂、养虾灵魂、龙虾角色、龙虾定位、 龙虾剧本杀角色、龙虾游戏角色、龙虾 NPC、龙虾性格、龙虾背景故事、 lobster soul、lobster character、抽卡、随机龙虾、龙虾 SOUL、gacha。
manim-video
Build reusable Manim explainers for technical concepts, graphs, system diagrams, and product walkthroughs, then hand off to the wider ECC video stack if needed. Use when the user wants a clean animated explainer rather than a generic talking-head script.
laravel-plugin-discovery
Discover and evaluate Laravel packages via LaraPlugins.io MCP. Use when the user wants to find plugins, check package health, or assess Laravel/PHP compatibility.