Back to Details

wot-ui-cli

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Wot UI CLI Skill

Wot UI CLI Skill

这个 skill 用于让 Agent 在处理 
@wot-ui/cli
本身相关的问题时，优先基于本仓库 README 与实际命令能力回答，而不是把它误当成纯组件库文档。
This skill is designed to enable Agents to prioritize answers based on the repository's README and actual command capabilities when handling issues related to 
@wot-ui/cli
itself, rather than mistaking it for pure component library documentation.

适用场景

Applicable Scenarios

  • 用户询问 
    wot
    命令怎么用。
  • 用户需要区分 
    list
    、
    info
    、
    doc
    、
    demo
    、
    token
    、
    changelog
    、
    doctor
    、
    usage
    、
    lint
    、
    mcp
    、
    extract
    的用途。
  • 用户要接入 MCP Server，或需要 
    wot mcp
    的配置与调试方法。
  • 用户要在本仓库中调试 
    @wot-ui/cli
    、验证构建产物、重新提取数据。
  • 用户的问题本质上是 open-wot 仓库维护问题，而不是单纯的 wot-ui 组件使用问题。
  • Users ask how to use the 
    wot
    command.
  • Users need to distinguish the purposes of 
    list
    , 
    info
    , 
    doc
    , 
    demo
    , 
    token
    , 
    changelog
    , 
    doctor
    , 
    usage
    , 
    lint
    , 
    mcp
    , 
    extract
    .
  • Users want to integrate with MCP Server, or need configuration and debugging methods for 
    wot mcp
    .
  • Users want to debug 
    @wot-ui/cli
    in this repository, verify build artifacts, or re-extract data.
  • Users' issues are essentially open-wot repository maintenance problems, rather than pure wot-ui component usage issues.

适用范围

Scope of Application

  • 关注对象是 
    @wot-ui/cli
    这个工具包，以及仓库 
    open-wot
    的开发维护流程。
  • 重点覆盖命令能力、通用参数、MCP、离线数据来源、提取流程、本地调试和发布包边界。
  • 如果任务是生成 
    wd-*
    页面代码、解释组件 props 或给出主题定制方案，应优先使用 
    wot-ui-v2
    skill。
  • Focuses on the 
    @wot-ui/cli
    toolkit and the development and maintenance process of the 
    open-wot
    repository.
  • Covers command capabilities, general parameters, MCP, offline data sources, extraction processes, local debugging, and release package boundaries in key areas.
  • If the task is to generate 
    wd-*
    page code, explain component props, or provide theme customization solutions, prioritize using the 
    wot-ui-v2
    skill.

推荐流程

Recommended Process

  1. 先确认用户是在问 CLI 工具本身，还是在借 CLI 查询组件知识。
  2. 如果是命令使用问题，优先按命令类别回答：组件知识、项目分析、MCP、数据提取、仓库开发。
  3. 如果是仓库维护问题，优先给出本仓库里的实际调试命令，而不是泛泛而谈。
  4. 如果涉及组件内容本身，可引导或切换到 
    wot-ui-v2
    skill。
  1. First confirm whether the user is asking about the CLI tool itself, or using the CLI to query component knowledge.
  2. If it's a command usage issue, answer by command category first: component knowledge, project analysis, MCP, data extraction, repository development.
  3. If it's a repository maintenance issue, prioritize providing actual debugging commands in this repository rather than general discussions.
  4. If component content is involved, guide or switch to the 
    wot-ui-v2
    skill.

命令分组

Command Groups

组件知识查询

Component Knowledge Query

  • wot list
  • wot info <Component>
  • wot doc <Component>
  • wot demo <Component> [name]
  • wot token [Component]
  • wot changelog [version] [component]
  • wot list
  • wot info <Component>
  • wot doc <Component>
  • wot demo <Component> [name]
  • wot token [Component]
  • wot changelog [version] [component]

项目分析

Project Analysis

  • wot doctor [dir]
  • wot usage [dir]
  • wot lint [dir]
  • wot doctor [dir]
  • wot usage [dir]
  • wot lint [dir]

MCP

MCP

  • wot mcp
  • wot mcp

数据提取与仓库维护

Data Extraction and Repository Maintenance

  • pnpm extract:cli --wot-dir ../wot-ui --output data/v2.json
  • pnpm extract:clone
  • pnpm exec tsx src/index.ts <command>
  • pnpm build
  • node dist/index.mjs <command>
  • pnpm extract:cli --wot-dir ../wot-ui --output data/v2.json
  • pnpm extract:clone
  • pnpm exec tsx src/index.ts <command>
  • pnpm build
  • node dist/index.mjs <command>

工作规则

Working Rules

  • 包名是 
    @wot-ui/cli
    ，实际可执行命令是 
    wot
    。
  • 回答命令问题时，优先用仓库 README 中已承诺的行为和参数，不臆造未声明子命令。
  • 回答本地调试问题时，优先给源码入口：
    pnpm exec tsx src/index.ts ...
    。
  • 回答构建产物问题时，再给 
    node dist/index.mjs ...
    。
  • 回答 MCP 问题时，要说明 
    wot mcp
    走 stdio，终端无交互输出通常是正常现象。
  • 回答提取逻辑问题时，要说明数据主要来自上游 
    wot-ui/wot-ui
    的 markdown 与 SCSS 源码。
  • 当用户问的是组件知识但入口是 CLI，也要保留“这是通过 CLI 查询组件知识”这一层语义。
  • The package name is 
    @wot-ui/cli
    , and the actual executable command is 
    wot
    .
  • When answering command-related questions, prioritize using the behaviors and parameters promised in the repository's README, and do not invent undeclared subcommands.
  • When answering local debugging questions, prioritize providing the source code entry: 
    pnpm exec tsx src/index.ts ...
    .
  • When answering build artifact questions, provide 
    node dist/index.mjs ...
    instead.
  • When answering MCP-related questions, explain that 
    wot mcp
    uses stdio, and no interactive output in the terminal is usually a normal phenomenon.
  • When answering extraction logic questions, explain that data mainly comes from the markdown and SCSS source code of the upstream 
    wot-ui/wot-ui
    .
  • When users ask about component knowledge but access it via the CLI, retain the semantic layer of "querying component knowledge through the CLI".

参考资料

Reference Materials

  • Wot UI CLI 概览
  • Wot UI CLI Overview