Agent skill

Migrate Component Doc

by wot-ui in wot-ui/wot-ui

迁移组件 Markdown 文档到新规范。用户明确要求迁移文档结构、重排 Demo 章节、合并 Attributes/Options 列、迁移最低版本标记或升级旧文档格式时调用;不用于仅做一致性核对。

MITAuto-check passedFrontend & Design

Install Migrate Component Doc

skills CLI
$ npx skills add wot-ui/wot-ui --skill migrate-component-doc -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wot-ui/wot-ui migrate-component-doc --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wot-ui/wot-ui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/migrate-component-doc .claude/skills/migrate-component-doc && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
migrate-component-doc
GitHub stars
384
Token cost
~610 tokens
SKILL.md length
176 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

迁移组件 Markdown 文档到新规范。用户明确要求迁移文档结构、重排 Demo 章节、合并 Attributes/Options 列、迁移最低版本标记或升级旧文档格式时调用;不用于仅做一致性核对。

  • Works in 3 steps: API 一致性核对 → Demo 顺序与分组规范 → Attributes / Options 表迁移
  • Frontend & Design work in your project
  • SKILL.md covers 何时使用, 何时不要使用, 目标输出 and 核心规则, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Migrate Component Doc is an agent skill from wot-ui/wot-ui. 迁移组件 Markdown 文档到新规范。用户明确要求迁移文档结构、重排 Demo 章节、合并 Attributes/Options 列、迁移最低版本标记或升级旧文档格式时调用;不用于仅做一致性核对。

Its SKILL.md is about 610 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design. It works with Vue.js. The repository describes itself as: 一个轻量、美观、AI友好的 uni-app 组件库。 The licence is MIT.

When your agent uses it

  • Frontend & Design work in your project

Example prompts

  • “/migrate-component-doc”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. API 一致性核对
  2. Demo 顺序与分组规范
  3. Attributes / Options 表迁移

What it can do on your machine

Read from SKILL.md and the folder at commit 0abe2c2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Migrate Component Doc loads about 610 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 176 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~610

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wot-ui/wot-ui at commit 0abe2c2, republished under its MIT licence (© wot-ui). 176 words, ~610 tokens.

Download SKILL.mdSave it as .claude/skills/migrate-component-doc/SKILL.md (or your agent's skills folder).
name
migrate-component-doc
description
迁移组件 Markdown 文档到新规范。用户明确要求迁移文档结构、重排 Demo 章节、合并 Attributes/Options 列、迁移最低版本标记或升级旧文档格式时调用;不用于仅做一致性核对。

组件文档迁移技能

本技能用于将组件文档迁移到统一新规范,覆盖 API 对齐、Demo 结构统一、Attributes/Options 表结构迁移与最低版本标记迁移。

默认遵循 wot-ui-component-baseline 中的共享约束。

何时使用

  • 用户要求“迁移某组件文档到新规范”。
  • 用户要求“按 Demo 规则整理文档中的示例章节”。
  • 用户要求“将最低版本并入参数列、合并说明与可选值列”。

何时不要使用

  • 用户只要求核对 props、events、slots、methods 是否准确,且未要求改文档结构。

以上场景应优先使用 check-doc-component-consistency。

目标输出

  • 文档 API 与组件实现一致:Attributes / Events(Emits) / Slots / Methods。
  • Demo 章节与演示页组织顺序一致,满足 create-demo-page 规则。
  • Attributes/Options 表结构迁移完成,版本标记迁移到参数列。
  • 产出差异清单、修改说明与验证结果。

核心规则

1) API 一致性核对
  • 组件源码核对范围:
    • props:types.ts、defineProps、默认值
    • emits:defineEmits 与模板事件转发
    • slots:模板 <slot> 与具名插槽
    • methods:defineExpose 暴露方法
  • 文档核对范围:
    • ## Attributes
    • ## Events
    • ## Slots
    • ## Methods(若无对外方法可省略)
  • 差异处理原则:
    • 文档缺失:补齐
    • 文档冗余:删除
    • 命名不一致:统一为组件真实 API 命名
2) Demo 顺序与分组规范
  • Demo 内容来源必须以“对应组件 demo 页面 + 组件源码能力”为准,不凭主观补充或删减。
  • 先对齐 src/subPages/<component>/Index.vue 的示例能力,再与组件 props/slots/events/methods 交叉校验覆盖面。
  • 使用 create-demo-page 作为默认基线顺序与命名规则,但允许按组件语义做自适应调整。
  • 若文档存在介绍性章节(如适用场景、使用前说明、平台差异、注意事项),应保留在 Demo 分组之前,不强制重排。
  • 当进入 Demo 能力展示区时,章节顺序、标题口径、可选分组启用方式均复用 create-demo-page,不要重复定义另一套规则。
  • 若组件存在强语义能力分组(如“异步流程”“平台能力”“业务模式”),可插入到最贴近语义的位置,并在迁移说明中记录原因。
  • 同类顺序保持稳定:primary -> success -> info -> warning -> danger。
3) Attributes / Options 表迁移
  • 目标列结构:参数 | 说明 | 类型 | 默认值。
  • 迁移规则:
    • 合并“说明 + 可选值”到说明列。
    • “最低版本”迁移到参数列后缀。
    • 支持识别版本标记语法 ^(x.y.z) 并在构建时转换为 Badge。
  • 文档编写要求:
    • 不手写 <Badge /> 或 <el-tag />。
    • 使用约定标记,由文档插件统一转换。
    • 可选值统一写法:在说明列使用“可选值为 a、b、c”,不使用 a / b / c 斜杠串写。
    • 示例代码尽量同时提供 vue/html 与 ts 两段,保证可直接复现。
    • 多段示例优先使用 ::: code-group 组织(如“模板/脚本”分组),提升可读性。
    • 当示例非常长、影响阅读体验时,使用 ::: details 折叠长代码。

执行步骤

  1. 识别目标组件与文档文件路径。
  2. 核对源码 API(props/emits/slots/methods)与文档章节差异。
  3. 以对应 demo 页面与组件源码能力为基准抽取示例,再保留组件介绍性章节,按 create-demo-page 基线与组件语义重排 Demo 章节顺序与命名,并按“vue/html + ts”成对补齐示例。
  4. 迁移 Attributes/Options 表:列合并、最低版本迁移到参数列。
  5. 应用版本标记约定(例如 ^(1.3.6))。
  6. 运行诊断与文档构建验证,输出剩余问题。

验收清单

  • API 四要素核对完成且文档与源码一致。
  • Demo 示例均可追溯到对应 demo 页面与组件真实能力。
  • Demo 分组顺序符合“create-demo-page 基线 + 组件语义自适应”规则。
  • Attributes/Options 已完成列合并与最低版本迁移。
  • 未手写组件标签,版本标签由约定格式生成。
  • 当前改动无新增语法或构建错误。

示例触发语句

  • “帮我把 button 文档迁移到新规范并对齐源码”
  • “按 demo 规范整理 calendar 文档示例顺序”
  • “把最低版本并到参数列,说明和可选值合并”

© wot-ui, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/migrate-component-doc of wot-ui/wot-ui.

Open the folder on GitHubat commit 0abe2c2

Compare with similar skills

Migrate Component Doc next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Migrate Component Doc compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Migrate Component Doc this skillwot-ui/wot-ui384—~610Automated safety check: PassMIT
Tailwindcss Developmentanonaddy/anonaddy4.9k10 repos~865Automated safety check: PassMIT
GSAP Core Animationgreensock/gsap-skills16k4 repos~3.7kAutomated safety check: PassMIT
GSAP in Vue, Nuxt and Sveltegreensock/gsap-skills16k4 repos~2.6kAutomated safety check: PassMIT
Vuetify Playgroundvuetifyjs/vuetify41k—~730Automated safety check: PassCustom licence
Boneyard0xGF/boneyard7.5k—~2.2kAutomated safety check: NotesMIT

Similar skills

  • Tailwindcss Development

    anonaddy/anonaddy

    Always invoke when the user's message includes 'tailwind' in any form.

    4.9k GitHub starsUsed in 10 repos~865 tokens
    Frontend & DesignAuto-check passed
  • GSAP Core Animation

    greensock/gsap-skills

    Covers the GSAP core API for tweens, easing, staggers, defaults and matchMedia, and when to choose GSAP over CSS animations or other JavaScript animation libraries.

    16k GitHub starsUsed in 4 repos~3.7k tokens
    Frontend & DesignAuto-check passed
  • GSAP in Vue, Nuxt and Svelte

    greensock/gsap-skills

    Shows how to use GSAP in Vue, Nuxt, Svelte and other lifecycle-based frameworks: create after mount, scope selectors to the component, and revert on unmount.

    16k GitHub starsUsed in 4 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Vuetify Playground

    vuetifyjs/vuetify

    Maintains the Vuetify repo's local Playground.vue so contributors get a realistic reproduction and a short demo they can paste into a pull request description.

    41k GitHub stars~730 tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Boneyard

    0xGF/boneyard

    Use boneyard-js to add, configure, debug, or rebuild skeleton screens.

    7.5k GitHub stars~2.2k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check: notes
  • Rules for writing Vue 3 templates with Buefy components on Bulma CSS: install options, prop conventions, b-field wrapping, tables, theming and dialogs.

    9.5k GitHub stars~8.2k tokensUpdated 29 days ago
    Frontend & DesignAuto-check passed

More from wot-ui/wot-ui

All 10 skills in this repo
  • Create Component

    wot-ui/wot-ui

    在 wot-ui 项目中创建新组件骨架与必要注册点。用户要求从零创建组件源码、补齐 types.vue.scss 结构或注册全局组件类型时调用;不负责 Demo 页、测试和文档迁移。

    384 GitHub stars~2.1k tokensUpdated 13 days ago
    Auto-check passed
  • Create Demo Page

    wot-ui/wot-ui

    为组件创建演示页面并统一组织结构。用户要求新建/重构组件 Demo、统一展示顺序或用 demo-group 与 demo-group-item 编排时调用。

    384 GitHub stars~547 tokensUpdated 13 days ago
    Auto-check passed
  • 为新组件或新特性快速生成符合设计系统规范的 SCSS 变量定义代码,或检查现有变量是否合规. An agent skill from wot-ui/wot-ui.

    384 GitHub stars~906 tokensUpdated 13 days ago
    Auto-check passed
  • Generate Theme

    wot-ui/wot-ui

    为 wot-ui 生成单文件主题 SCSS,并在 App.vue 中挂载语义变量. An agent skill from wot-ui/wot-ui.

    384 GitHub stars~2.4k tokensUpdated 13 days ago
    Auto-check passed
  • 优化 subPages 演示页面中的样式,将硬编码的颜色、字号、间距、圆角等替换为 wot-ui 设计系统语义变量。允许直接使用已全局注入的 variable.scss Sass 变量,也允许使用 CSS 自定义属性;不需要额外引入 variable.scss。消除手写的暗色模式覆盖块,统一使用语义变量实现自适应主题。同时将 class 命名统一为 BEM 规范。

    384 GitHub stars~4.9k tokensUpdated 13 days ago
    Auto-check passed
  • Vue Comment

    wot-ui/wot-ui

    统一 Vue 与 wot-ui 组件源码中的注释和命名规范。用户要求规范组件 Props 注释、函数命名、类型说明、变量命名或在创建组件后补齐代码注释时调用;不负责 Demo、测试和文档迁移。

    384 GitHub stars~965 tokensUpdated 13 days ago
    Auto-check passed

Works with

Questions about Migrate Component Doc

What does Migrate Component Doc do?

迁移组件 Markdown 文档到新规范。用户明确要求迁移文档结构、重排 Demo 章节、合并 Attributes/Options 列、迁移最低版本标记或升级旧文档格式时调用;不用于仅做一致性核对。. Migrate Component Doc is an agent skill from wot-ui/wot-ui.

When should I use Migrate Component Doc?

Migrate Component Doc fits situations like: frontend & Design work in your project.

How do I install Migrate Component Doc in Claude Code?

Run `npx skills add wot-ui/wot-ui --skill migrate-component-doc -a claude-code`. Or copy the skill folder (.agents/skills/migrate-component-doc in wot-ui/wot-ui) into .claude/skills/migrate-component-doc in your project. Claude Code loads it when a task matches its description.

How do I install Migrate Component Doc in Codex?

Run `npx skills add wot-ui/wot-ui --skill migrate-component-doc -a codex`. Or copy the skill folder (.agents/skills/migrate-component-doc in wot-ui/wot-ui) into .agents/skills/migrate-component-doc in your project. Codex loads it when a task matches its description.

Can I use Migrate Component Doc in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wot-ui/wot-ui --skill migrate-component-doc -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/migrate-component-doc, .gemini/skills/migrate-component-doc, .github/skills/migrate-component-doc and .opencode/skills/migrate-component-doc in your project.

What does Migrate Component Doc need to run?

SKILL.md names no scripts, command-line tools or credentials: Migrate Component Doc is instructions for the agent only.

Does Migrate Component Doc access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Migrate Component Doc safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Migrate Component Doc use?

Migrate Component Doc is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Migrate Component Doc use?

About 610 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Migrate Component Doc?

Skills that share tags, products or a category with Migrate Component Doc: Tailwindcss Development (anonaddy/anonaddy, 4.9k stars), GSAP Core Animation (greensock/gsap-skills, 16k stars), GSAP in Vue, Nuxt and Svelte (greensock/gsap-skills, 16k stars) and Vuetify Playground (vuetifyjs/vuetify, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Migrate Component Doc?

wot-ui (a GitHub organization) maintains it in wot-ui/wot-ui, which has 384 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 25, 2026.

Source: wot-ui/wot-ui on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.