Output format·Design & Media

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…

You say
Buy it · $24 Read it before you buy $24 Written by affaan-m · unverified publisher
Context cost
1.2k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 4.8 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

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.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Output format

Produces one artefact, exactly shaped.

designvue
Filed under

Design & Media

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md4.8 kB · 136 lines
--- name: ui-to-vue description: 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. metadata: origin: community ---
8# UI To Vue
9
10Batch-convert UI design screenshots into Vue 3 Composition API component code.
11
12## When to Use
13
14- The user provides a directory of design screenshots or design-export images.
15- The target application is Vue 3.
16- The user wants a first pass of page components, shared components, and router wiring.
17- The user specifies Vant, Element Plus, or Ant Design Vue as the component library.
18
19## When Not to Use
20
21- The user has only one screenshot and wants a bespoke component.
22- The target project is not Vue.
23- The design requires detailed interaction logic, data flow, or accessibility review.
24- The screenshots contain private customer data that cannot be sent to an external model API.
25
26## Inputs
27
28Use an input directory that groups screenshots by module and page state:
29
30```text
31screenshots/
32|-- HomePage/
33| |-- List/
34| | |-- HomePage-List-Default@3x.png
35| | `-- cut-images/
36| |-- cut-images/
37| `-- HomePage-Default@3x.png
38`-- cut-images/
39```
40
41Supported cut-image directory names include assets, icons, sprites, cut, images, and cut-images.
42
43## Conversion Model
44
45- Page grouping: combine related screenshots into one page component when they represent list, detail, form, loading, or empty states.
46- UI library mapping: map native visual elements to Vant, Element Plus, or Ant Design Vue components where practical.
47- Cut-image priority: prefer page-level assets, then module-level assets, then global shared assets.
48- Component extraction: extract repeated UI regions into shared components when they appear more than once.
49
50## CLI Usage
51
52Run the converter with npx so the documented command works without relying on a global binary:
53
54```bash
55export DASHSCOPE_API_KEY=your_key
56npx ui-to-vue-converter@1.0.2 --input ./screenshots --ui vant --output ./src
57```
58
59For desktop UI libraries:
60
61```bash
62npx ui-to-vue-converter@1.0.2 --input ./designs --ui element-plus --output ./src
63npx ui-to-vue-converter@1.0.2 --input ./designs --ui antd-vue --output ./src
64```
65
66If the package is installed globally, the ui-to-vue binary can be used directly:
67
68```bash
69npm install -g ui-to-vue-converter@1.0.2
70ui-to-vue --input ./screenshots --ui vant --output ./src
71```
72
73## Options
74
75| Option | Description | Default |
76| --- | --- | --- |
77| --input | Design image directory | ./screenshots |
78| --ui | UI library: vant, element-plus, or antd-vue | vant |
79| --output | Output directory | ./src |
80| --config | Config file path | ./.ui-to-vue.config.json |
81
82## API Key Handling
83
84The converter can read DashScope credentials from a config file or from the environment. Prefer an environment variable in repositories:
85
86```bash
87export DASHSCOPE_API_KEY=your_key
88```
89
90If a local config file is required, keep it out of version control:
91
92```json
93{
94 "apiKey": "your_dashscope_key",
95 "input": "./designs",
96 "ui": "vant",
97 "output": "./src"
98}
99```
100
101```gitignore
102.ui-to-vue.config.json
103```
104
105## Security and Privacy
106
107- Treat design screenshots as source material that may be sent to an external model API.
108- Do not run this flow on private customer designs without permission.
109- Pin the converter version in repeatable workflows instead of using @latest.
110- Review generated Vue code before committing it.
111- Do not commit .ui-to-vue.config.json, API keys, generated secrets, or customer screenshots.
112
113## Output Review Checklist
114
115- [ ] Page components were generated under views/ or the chosen output directory.
116- [ ] Repeated UI regions were extracted into components/ only when reuse is clear.
117- [ ] Router output is compatible with the target project's router style.
118- [ ] Generated components use the requested UI library consistently.
119- [ ] Generated CSS units match the design baseline.
120- [ ] The code passes the project's formatter, linter, type checker, and build.
121- [ ] Placeholder copy, mock data, and generated assets were reviewed before commit.
122
123## Troubleshooting
124
125| Issue | Check |
126| --- | --- |
127| 401 or authentication error | Confirm DASHSCOPE_API_KEY is set in the shell running the command. |
128| command not found: ui-to-vue | Use the npx ui-to-vue-converter@1.0.2 form or install the package globally. |
129| Cut images are ignored | Confirm the asset directory name is supported and nested under the matching page or module. |
130| Components ignore the requested UI library | Re-run with an explicit --ui value and inspect the generated imports. |
131| Generated layout dimensions look wrong | Confirm the screenshot export width matches the target library baseline. |
132
133## References
134
135- npm package: ui-to-vue-converter
136
In the file
SKILL.md736 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈60
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
1,140
on trigger
The instruction body, read only when the skill fires.
0.60%
of a 200k window
Ten skills this size would take about 6% of the window before you open a file.
050k100k150k200k context window

1.2k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 4.8 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md4.8 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$24 once
UI To Vue · MIT · affaan-m
one-time
Price$24 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$24
Referenceaffaan-m/ui-to-vue

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Publisher
Servers0