Ui To Vue
Use when the user has UI screenshots or design exports that need batch conversion into Vue 3 components, especially with Vant, Element Plus, or Ant Design Vue.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Ui To Vue when an AI agent needs a reusable SKILL.md workflow for this job: Use when the user has UI screenshots or design exports that need batch conversion into Vue 3 components, especially with Vant, Element Plus, or Ant Design Vue.
When not to use it
Skip Ui To Vue when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/ui-to-vue # Save SKILL.md to ~/.claude/skills/ui-to-vue/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/ui-to-vue/SKILL.md. For a shared project, commit the folder at .claude/skills/ui-to-vue/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Ui To Vue skill for this task: The user provides a directory of design screenshots or design-export images. Confirm any required inputs or files before making changes.
What supports this recommendation?
83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 92/100
- Practical detail
- 92/100
- Source evidence
- 63/100
- Source signals
- 68/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# UI To Vue
Batch-convert UI design screenshots into Vue 3 Composition API component code.
## When to Use
- The user provides a directory of design screenshots or design-export images. - The target application is Vue 3. - The user wants a first pass of page components, shared components, and router wiring. - The user specifies Vant, Element Plus, or Ant Design Vue as the component library.
## When Not to Use
- The user has only one screenshot and wants a bespoke component. - The target project is not Vue. - The design requires detailed interaction logic, data flow, or accessibility review. - The screenshots contain private customer data that cannot be sent to an external model API.
## Inputs
Use an input directory that groups screenshots by module and page state:
```text screenshots/ |-- HomePage/ | |-- List/ | | |-- [email protected] | | `-- cut-images/ | |-- cut-images/ | `-- [email protected] `-- cut-images/ ```
Supported cut-image directory names include `assets`, `icons`, `sprites`, `cut`, `images`, and `cut-images`.
## Conversion Model
- Page grouping: combine related screenshots into one page component when they represent list, detail, form, loading, or empty states. - UI library mapping: map native visual elements to Vant, Element Plus, or Ant Design Vue components where practical. - Cut-image priority: prefer page-level assets, then module-level assets, then global shared assets. - Component extraction: extract repeated UI regions into shared components when they appear more than once.
## CLI Usage
Run the converter with `npx` so the documented command works without relying on a global binary:
```bash export DASHSCOPE_API_KEY=your_key npx [email protected] --input ./screenshots --ui vant --output ./src ```
For desktop UI libraries:
```bash npx [email protected] --input ./designs --ui element-plus --output ./src npx [email protected] --input ./designs --ui antd-vue --output ./src ```
If the package is installed globally, the `ui-to-vue` binary can be used directly:
```bash npm install -g [email protected] ui-to-vue --input ./screenshots --ui vant --output ./src ```
## Options
| Option | Description | Default | | --- | --- | --- | | `--input` | Design image directory | `./screenshots` | | `--ui` | UI library: `vant`, `element-plus`, or `antd-vue` | `vant` | | `--output` | Output directory | `./src` | | `--config` | Config file path | `./.ui-to-vue.config.json` |
## API Key Handling
The converter can read DashScope credentials from a config file or from the environment. Prefer an environment variable in repositories:
```bash export DASHSCOPE_API_KEY=your_key ```
If a local config file is required, keep it out of version control:
```json { "apiKey": "your_dashscope_key", "input": "./designs", "ui": "vant", "output": "./src" } ```
```gitignore .ui-to-vue.config.json ```
## Security and Privacy
- Treat design screenshots as source material that may be sent to an external model API. - Do not run this flow on private customer designs without permission. - Pin the converter version in repeatable workflows instead of using `@latest`. - Review generated Vue code before committing it. - Do not commit `.ui-to-vue.config.json`, API keys, generated secrets, or customer screenshots.
## Output Review Checklist
- [ ] Page components were generated under `views/` or the chosen output directory. - [ ] Repeated UI regions were extracted into `components/` only when reuse is clear. - [ ] Router output is compatible with the target project's router style. - [ ] Generated components use the requested UI library consistently. - [ ] Generated CSS units match the design baseline. - [ ] The code passes the project's formatter, linter, type checker, and build. - [ ] Placeholder copy, mock data, and generated assets were reviewed before commit.
## Troubleshooting
| Issue | Check | | --- | --- | | `401` or authentication error | Confirm `DASHSCOPE_API_KEY` is set in the shell running the command. | | `command not found: ui-to-vue` | Use the `npx [email protected]` form or install the package globally. | | Cut images are ignored | Confirm the asset directory name is supported and nested under the matching page or module. | | Components ignore the requested UI library | Re-run with an explicit `--ui` value and inspect the generated imports. | | Generated layout dimensions look wrong | Confirm the screenshot export width matches the target library baseline. |
## References
- npm package: `ui-to-vue-converter`
Intended uses
- The user provides a directory of design screenshots or design-export images.
- The target application is Vue 3.
- The user wants a first pass of page components, shared components, and router wiring.
- The user specifies Vant, Element Plus, or Ant Design Vue as the component library.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.