Vue Design System
Target stack: Vue 3 (Composition API, <script setup>) · no React · no Tailwind · no Bootstrap · web, desktop, mobile, and CLI.
This skill is the Vue and CLI build router. It does not invent a second look. @taste-penpot is the general design skill and owns aesthetic direction. @heyeddi-design records it in .heyeddi/design.md. This skill decides which package builds the surface, then you load that skill and follow it.
When to use
Load this skill before writing interface code when the prompt is a screen, shell, dashboard, form, menu, theme, motion, or terminal UI.
| Surface |
Primary skill |
Supporting skill |
| App framing, drawers, tabs, mobile or desktop shell |
@quasar-foundation |
@aura-design-tokens |
| Tables, trees, pickers, SaaS forms, overlays |
@primevue-aura |
@motion-physics |
| Micro-interactions and transitions |
@motion-physics |
@aura-design-tokens |
| A card or row that expands in the same view |
@layout-morph |
@quasar-foundation |
| Spotlight, glass, one 3D accent, or a local Lottie |
@fancy-ui-craft |
@motion-physics |
| Terminal, CLI, dev tools |
@cli-interface-design |
Terminal execution (run the script, read ANSI stdout) |
| Theming and color |
@aura-design-tokens |
@quasar-foundation |
| Visual QA of the live page |
@visual-verification |
Playwright MCP |
| Designer boards, demo exports |
@taste-penpot |
@aura-design-tokens |
After either GUI branch, load @motion-physics, then @layout-morph only when a shared element moves, then @fancy-ui-craft only when depth was requested, then @visual-verification.
Routing
Agent prompt
│
├─ Visual UI (GUI)
│ ├─ App shell / native layout → @quasar-foundation
│ │ navigation, drawers, tabs, mobile/desktop shell
│ └─ Data-dense / form UI → @primevue-aura
│ tables, trees, pickers, SaaS dashboards
│ then @motion-physics
│ then @layout-morph when a shared element moves
│ then @fancy-ui-craft when the page needs depth
│ then @visual-verification
│ Vite HMR, Playwright MCP screenshot, fix what you see
│
└─ Terminal / CLI → @cli-interface-design
@clack/prompts, consola, picocolors
then run the script and read ANSI stdout
Packages:
| Scope |
Primary |
Supporting |
Packages |
| App framing and native packaging |
quasar-foundation |
aura-design-tokens |
quasar, @quasar/extras |
| Complex tables, forms, overlays |
primevue-aura |
motion-physics |
primevue, @primevue/themes |
| Micro-interactions |
motion-physics |
aura-design-tokens |
@vueuse/motion |
| Shared-element morph |
layout-morph |
quasar-foundation |
Quasar v-morph (gsap only across routes) |
| Spotlight, glass, 3D, Lottie |
fancy-ui-craft |
motion-physics |
@vueuse/core, @tresjs/core, @lottiefiles/dotlottie-vue |
| Visual QA and screenshot inspection |
visual-verification |
Playwright MCP |
@playwright/mcp |
| Terminal / CLI |
cli-interface-design |
Terminal execution |
@clack/prompts, consola, picocolors |
| Theming |
aura-design-tokens |
quasar-foundation |
CSS custom properties |
Instructions
- Classify the prompt: visual UI or terminal. A GUI screen that also has a CLI is two skills, in that order.
- Read the primary skill's
SKILL.md and its component table before choosing a component.
- Read the supporting skill. GUI work also reads
@motion-physics, @aura-design-tokens, then @layout-morph only when a shared element moves, then @fancy-ui-craft only when depth was requested, then @visual-verification.
- App bootstrap (Vite plugin order,
main.js load order) lives in @primevue-aura. Quasar CSS loads first. PrimeVue Aura loads second. Motion loads third.
- Map colors through
@aura-design-tokens. Do not write raw hex in components.
- Designer visuals and Penpot demos:
@taste-penpot using only @zcubekr/penpot-mcp-server (npx -y @zcubekr/penpot-mcp-server). If that server is missing, @taste-penpot installs it after the user approves. A redesign or from-scratch request loads references/code-to-design.md first. Never use unscoped penpot-mcp-server, the plugin MCP (@penpot/mcp, execute_code), or penpot-api-mcp.
Agent directives
Core architecture
- Framework: Vue 3 (Composition API with
<script setup>).
- Prohibited libraries: do not introduce or suggest React, Tailwind CSS, or Bootstrap.
- Layout vs data:
- Quasar (
<q-layout>, <q-drawer>, <q-header>) for application framing and cross-platform native builds.
- PrimeVue (Aura preset) for data tables, form fields, badges, and contextual menus.
@vueuse/motion for animations.
- Page regions use the Flex or CSS Grid named in the spec (
@taste-penpot references/flex-grid.md). Copy display, gap, tracks, and Fit / Fill / Fix. Do not restack that CSS as margins. The app frame stays the Quasar view that matches the spec (lHh Lpr lFf when the sidebar is full height and the header sits in the main column).
Visual self-correction (GUI)
When generating or heavily refactoring a visual component:
- Verify the local dev server is running (
http://localhost:5173).
- Use the Playwright MCP (
browser_navigate, browser_resize, browser_take_screenshot) to capture the route.
- Inspect the image for visual overlap, broken flex wrap, misaligned padding, or unstyled raw fonts.
- Correct those defects before declaring the task complete.
Desktop is 1440×900. Mobile is 390×844. Details are in @visual-verification.
Terminal and CLI
- When asked to build CLI utilities or terminal views, do not write browser HTML/CSS.
- Use
@clack/prompts for interactive question trees and inputs.
- Use
consola for badges, status reports, and structured log displays.
- Keep output formatting within 16-color ANSI palettes using
picocolors.
- Run the script in the terminal and inspect stdout to verify alignment. Do not screenshot a CLI.
Styling and tokens
- Do not output raw hex colors (
#1a2b3c) or inline styling coordinates in components.
- Reference CSS custom properties:
- Surface layers:
var(--app-bg), var(--app-surface-card)
- Borders:
1px solid var(--app-border)
- Text tones:
var(--app-text-main), var(--app-text-muted)
Motion
- All animations must use spring physics:
- Interactive elements:
{ type: 'spring', stiffness: 350, damping: 25 }
- Dialogs and overlays:
{ type: 'spring', stiffness: 280, damping: 22 }
- Avoid linear transitions, unmotivated continuous bounces, and stagger delays over 40ms.
- Prefer the named presets in
@motion-physics when they match the moment.
- A shared element that grows in the same view uses Quasar
v-morph via @layout-morph, not a spring on position.
MCP servers
PrimeVue, Quasar, Playwright, and Penpot run over stdio. Penpot is @zcubekr/penpot-mcp-server. Unscoped penpot-mcp-server and @penpot/mcp are the wrong packages.
{
"mcpServers": {
"primevue": {
"command": "npx",
"args": ["-y", "@primevue/mcp"]
},
"quasar": {
"command": "npx",
"args": ["-y", "--fetch-retries=0", "@quasar/mcp@latest"]
},
"playwright": {
"command": "npx",
"args": ["-y", "@playwright/mcp@latest"]
},
"penpot": {
"command": "npx",
"args": ["-y", "@zcubekr/penpot-mcp-server"],
"env": {
"PENPOT_API_URL": "https://design.penpot.app"
}
}
}
}
Start the Penpot server only when a designer visual, a redesign, or a demo export is in scope. Add it to .cursor/mcp.json only after the user approves. PENPOT_ACCESS_TOKEN stays in the environment. Never print it and never write it into config. See @taste-penpot → references/penpot-mcp.md.
@primevue-openprops-architect is a compatibility name. If it loads, follow this skill. Do not add OpenProps unless the project already depends on open-props.
When the task is complete: suggest next skills
When you have finished the user's request for this skill, suggest what to run next:
Run:
python .agents/skills/heyeddi/scripts/suggest_next_skill.py --current-skill vue-design-system --project-root .
Include the script's ### Next step block in your final reply.
1---2name: vue-design-system3description: "Routes Vue 3 UI and CLI work to Quasar shells, PrimeVue Aura, spring motion, shared-element morphs, depth effects, CSS tokens, visual verification, or terminal UI. No React, no Tailwind, no Bootstrap. GUI work ends in a Playwright MCP screenshot of the Vite server. CLI work ends by running the script and reading stdout."4version: 1.0.15product-version: 3.8.186author: HeyEddi-com7metadata:8 source: https://skillmd.com/skills/heyeddi-com/vue-design-system9---1011# Vue Design System1213**Target stack:** Vue 3 (Composition API, `<script setup>`) · no React · no Tailwind · no Bootstrap · web, desktop, mobile, and CLI.1415This skill is the Vue and CLI build router. It does not invent a second look. `@taste-penpot` is the general design skill and owns aesthetic direction. `@heyeddi-design` records it in `.heyeddi/design.md`. This skill decides which package builds the surface, then you load that skill and follow it.1617## When to use1819Load this skill before writing interface code when the prompt is a screen, shell, dashboard, form, menu, theme, motion, or terminal UI.2021| Surface | Primary skill | Supporting skill |22|---------|---------------|------------------|23| App framing, drawers, tabs, mobile or desktop shell | `@quasar-foundation` | `@aura-design-tokens` |24| Tables, trees, pickers, SaaS forms, overlays | `@primevue-aura` | `@motion-physics` |25| Micro-interactions and transitions | `@motion-physics` | `@aura-design-tokens` |26| A card or row that expands in the same view | `@layout-morph` | `@quasar-foundation` |27| Spotlight, glass, one 3D accent, or a local Lottie | `@fancy-ui-craft` | `@motion-physics` |28| Terminal, CLI, dev tools | `@cli-interface-design` | Terminal execution (run the script, read ANSI stdout) |29| Theming and color | `@aura-design-tokens` | `@quasar-foundation` |30| Visual QA of the live page | `@visual-verification` | Playwright MCP |31| Designer boards, demo exports | `@taste-penpot` | `@aura-design-tokens` |3233After either GUI branch, load `@motion-physics`, then `@layout-morph` only when a shared element moves, then `@fancy-ui-craft` only when depth was requested, then `@visual-verification`.3435## Routing3637```38Agent prompt39 │40 ├─ Visual UI (GUI)41 │ ├─ App shell / native layout → @quasar-foundation42 │ │ navigation, drawers, tabs, mobile/desktop shell43 │ └─ Data-dense / form UI → @primevue-aura44 │ tables, trees, pickers, SaaS dashboards45 │ then @motion-physics46 │ then @layout-morph when a shared element moves47 │ then @fancy-ui-craft when the page needs depth48 │ then @visual-verification49 │ Vite HMR, Playwright MCP screenshot, fix what you see50 │51 └─ Terminal / CLI → @cli-interface-design52 @clack/prompts, consola, picocolors53 then run the script and read ANSI stdout54```5556Packages:5758| Scope | Primary | Supporting | Packages |59|-------|---------|------------|----------|60| App framing and native packaging | `quasar-foundation` | `aura-design-tokens` | `quasar`, `@quasar/extras` |61| Complex tables, forms, overlays | `primevue-aura` | `motion-physics` | `primevue`, `@primevue/themes` |62| Micro-interactions | `motion-physics` | `aura-design-tokens` | `@vueuse/motion` |63| Shared-element morph | `layout-morph` | `quasar-foundation` | Quasar `v-morph` (gsap only across routes) |64| Spotlight, glass, 3D, Lottie | `fancy-ui-craft` | `motion-physics` | `@vueuse/core`, `@tresjs/core`, `@lottiefiles/dotlottie-vue` |65| Visual QA and screenshot inspection | `visual-verification` | Playwright MCP | `@playwright/mcp` |66| Terminal / CLI | `cli-interface-design` | Terminal execution | `@clack/prompts`, `consola`, `picocolors` |67| Theming | `aura-design-tokens` | `quasar-foundation` | CSS custom properties |6869## Instructions70711. Classify the prompt: visual UI or terminal. A GUI screen that also has a CLI is two skills, in that order.722. Read the primary skill's `SKILL.md` and its component table before choosing a component.733. Read the supporting skill. GUI work also reads `@motion-physics`, `@aura-design-tokens`, then `@layout-morph` only when a shared element moves, then `@fancy-ui-craft` only when depth was requested, then `@visual-verification`.744. App bootstrap (Vite plugin order, `main.js` load order) lives in `@primevue-aura`. Quasar CSS loads first. PrimeVue Aura loads second. Motion loads third.755. Map colors through `@aura-design-tokens`. Do not write raw hex in components.766. Designer visuals and Penpot demos: `@taste-penpot` using **only** `@zcubekr/penpot-mcp-server` (`npx -y @zcubekr/penpot-mcp-server`). If that server is missing, `@taste-penpot` installs it after the user approves. A redesign or from-scratch request loads `references/code-to-design.md` first. Never use unscoped `penpot-mcp-server`, the plugin MCP (`@penpot/mcp`, `execute_code`), or `penpot-api-mcp`.7778## Agent directives7980### Core architecture8182- Framework: Vue 3 (Composition API with `<script setup>`).83- Prohibited libraries: do not introduce or suggest React, Tailwind CSS, or Bootstrap.84- Layout vs data:85 - Quasar (`<q-layout>`, `<q-drawer>`, `<q-header>`) for application framing and cross-platform native builds.86 - PrimeVue (Aura preset) for data tables, form fields, badges, and contextual menus.87 - `@vueuse/motion` for animations.88- Page regions use the Flex or CSS Grid named in the spec (`@taste-penpot` `references/flex-grid.md`). Copy `display`, `gap`, tracks, and Fit / Fill / Fix. Do not restack that CSS as margins. The app frame stays the Quasar `view` that matches the spec (`lHh Lpr lFf` when the sidebar is full height and the header sits in the main column).8990### Visual self-correction (GUI)9192When generating or heavily refactoring a visual component:93941. Verify the local dev server is running (`http://localhost:5173`).952. Use the Playwright MCP (`browser_navigate`, `browser_resize`, `browser_take_screenshot`) to capture the route.963. Inspect the image for visual overlap, broken flex wrap, misaligned padding, or unstyled raw fonts.974. Correct those defects before declaring the task complete.9899Desktop is 1440×900. Mobile is 390×844. Details are in `@visual-verification`.100101### Terminal and CLI102103- When asked to build CLI utilities or terminal views, do not write browser HTML/CSS.104- Use `@clack/prompts` for interactive question trees and inputs.105- Use `consola` for badges, status reports, and structured log displays.106- Keep output formatting within 16-color ANSI palettes using `picocolors`.107- Run the script in the terminal and inspect stdout to verify alignment. Do not screenshot a CLI.108109### Styling and tokens110111- Do not output raw hex colors (`#1a2b3c`) or inline styling coordinates in components.112- Reference CSS custom properties:113 - Surface layers: `var(--app-bg)`, `var(--app-surface-card)`114 - Borders: `1px solid var(--app-border)`115 - Text tones: `var(--app-text-main)`, `var(--app-text-muted)`116117### Motion118119- All animations must use spring physics:120 - Interactive elements: `{ type: 'spring', stiffness: 350, damping: 25 }`121 - Dialogs and overlays: `{ type: 'spring', stiffness: 280, damping: 22 }`122- Avoid linear transitions, unmotivated continuous bounces, and stagger delays over 40ms.123- Prefer the named presets in `@motion-physics` when they match the moment.124- A shared element that grows in the same view uses Quasar `v-morph` via `@layout-morph`, not a spring on position.125126## MCP servers127128PrimeVue, Quasar, Playwright, and Penpot run over stdio. Penpot is `@zcubekr/penpot-mcp-server`. Unscoped `penpot-mcp-server` and `@penpot/mcp` are the wrong packages.129130```json131{132 "mcpServers": {133 "primevue": {134 "command": "npx",135 "args": ["-y", "@primevue/mcp"]136 },137 "quasar": {138 "command": "npx",139 "args": ["-y", "--fetch-retries=0", "@quasar/mcp@latest"]140 },141 "playwright": {142 "command": "npx",143 "args": ["-y", "@playwright/mcp@latest"]144 },145 "penpot": {146 "command": "npx",147 "args": ["-y", "@zcubekr/penpot-mcp-server"],148 "env": {149 "PENPOT_API_URL": "https://design.penpot.app"150 }151 }152 }153}154```155156Start the Penpot server only when a designer visual, a redesign, or a demo export is in scope. Add it to `.cursor/mcp.json` only after the user approves. `PENPOT_ACCESS_TOKEN` stays in the environment. Never print it and never write it into config. See `@taste-penpot` → `references/penpot-mcp.md`.157158`@primevue-openprops-architect` is a compatibility name. If it loads, follow this skill. Do not add OpenProps unless the project already depends on `open-props`.159160## When the task is complete: suggest next skills161162When you have **finished the user's request** for this skill, suggest what to run next:1631641. Run:165166 ```bash167 python .agents/skills/heyeddi/scripts/suggest_next_skill.py --current-skill vue-design-system --project-root .168 ```1691702. Include the script's **`### Next step`** block in your **final** reply.