agentleFS
HeyEddi-comHeyEddi-com/heyeddi-skills/skills/vue-design-system/SKILL.md

vue-design-system

Skill0 starsChanged 7 days agoMITView on GitHub

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.

  • Reads credentials

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 6 are distinctive, and 11 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 11

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After either GUI branch, load @motion-physics, then @layout-morph only when a shared element moves, then @fancy-ui-craft only when depth …

    line 31
  2. Very specific:

    Read the primary skill's SKILL.md and its component table before choosing a component.

    line 70
  3. Very specific:

    Read the supporting skill.

    line 71
  4. Distinctive:

    When generating or heavily refactoring a visual component:

    line 90
  5. Very specific:

    Verify the local dev server is running (http://localhost:5173).

    line 92
  6. Very specific:

    Use the Playwright MCP (browser_navigate, browser_resize, browser_take_screenshot) to capture the route.

    line 93
  7. Distinctive:

    When asked to build CLI utilities or terminal views, do not write browser HTML/CSS.

    line 101
  8. Very specific:

    Use @clack/prompts for interactive question trees and inputs.

    line 102
  9. Very specific:

    Use consola for badges, status reports, and structured log displays.

    line 103
  10. Very specific:

    Keep output formatting within 16-color ANSI palettes using picocolors.

    line 104
  11. Distinctive:

    Run the script in the terminal and inspect stdout to verify alignment.

    line 105
  12. Very specific:

    Do not output raw hex colors (#1a2b3c) or inline styling coordinates in components.

    line 109
  13. Distinctive:

    All animations must use spring physics:

    line 117
  14. Distinctive:

    Avoid linear transitions, unmotivated continuous bounces, and stagger delays over 40ms.

    line 120
  15. Very specific:

    Prefer the named presets in @motion-physics when they match the moment.

    line 121
  16. Very specific:

    Start the Penpot server only when a designer visual, a redesign, or a demo export is in scope.

    line 154
  17. Distinctive:

    When you have finished the user's request for this skill, suggest what to run next:

    line 160

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

SurfacePrimary skillSupporting 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-designTerminal execution (run the script, read ANSI stdout)
Theming and color@aura-design-tokens@quasar-foundation
Visual QA of the live page@visual-verificationPlaywright 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:

ScopePrimarySupportingPackages
App framing and native packagingquasar-foundationaura-design-tokensquasar, @quasar/extras
Complex tables, forms, overlaysprimevue-auramotion-physicsprimevue, @primevue/themes
Micro-interactionsmotion-physicsaura-design-tokens@vueuse/motion
Shared-element morphlayout-morphquasar-foundationQuasar v-morph (gsap only across routes)
Spotlight, glass, 3D, Lottiefancy-ui-craftmotion-physics@vueuse/core, @tresjs/core, @lottiefiles/dotlottie-vue
Visual QA and screenshot inspectionvisual-verificationPlaywright MCP@playwright/mcp
Terminal / CLIcli-interface-designTerminal execution@clack/prompts, consola, picocolors
Themingaura-design-tokensquasar-foundationCSS custom properties

Instructions

  1. Classify the prompt: visual UI or terminal. A GUI screen that also has a CLI is two skills, in that order.
  2. Read the primary skill's SKILL.md and its component table before choosing a component.
  3. 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.
  4. App bootstrap (Vite plugin order, main.js load order) lives in @primevue-aura. Quasar CSS loads first. PrimeVue Aura loads second. Motion loads third.
  5. Map colors through @aura-design-tokens. Do not write raw hex in components.
  6. 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:

  1. Verify the local dev server is running (http://localhost:5173).
  2. Use the Playwright MCP (browser_navigate, browser_resize, browser_take_screenshot) to capture the route.
  3. Inspect the image for visual overlap, broken flex wrap, misaligned padding, or unstyled raw fonts.
  4. 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:

  1. Run:

    python .agents/skills/heyeddi/scripts/suggest_next_skill.py --current-skill vue-design-system --project-root .
  2. Include the script's ### Next step block in your final reply.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.