vue

Build token-driven Vue 3 components with the Composition API and TypeScript.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/ChoreShore/Version1 --skill vue-choreshore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vue
Source: https://github.com/ChoreShore/Version1/tree/main/.windsurf/skills/vue
Command: npx skills add https://github.com/ChoreShore/Version1 --skill vue-choreshore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a clear, repeatable pattern for building Vue 3 component libraries and Nuxt design system pieces that integrate design tokens, TypeScript typing, composables, and accessibility so teams avoid inconsistent UI, duplicated logic, and brittle components.

Core Features & Use Cases

  • Token-driven styling: Use CSS custom properties or provide/inject to consume design tokens across components.
  • Composition API & TypeScript: Define typed props, emits, and composables for predictable component contracts.
  • Accessibility & patterns: Built-in ARIA attributes, keyboard handling, focus management, and testing examples to ensure production readiness.
  • Use Case: Convert a Figma button and input design into a VButton and VInput pair that share tokens, support multiple sizes/variants, and are test-covered for interactions.

Quick Start

Create a VButton component that uses design tokens for color/spacing, TypeScript props for variants and size, composables for shared logic, and accessibility attributes for keyboard and loading states.

Frequently Asked Questions about vue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build Vue 3 components with design tokens and TypeScript?

Build Vue 3 components with design tokens and TypeScript by using the Composition API to define typed props and emits, then consuming CSS custom properties or provide/inject to apply token-driven styling across your component library.

What is the best way to structure a Nuxt design system using the Composition API?

Structure a Nuxt design system by creating reusable primitives and composites using Vue 3 composables to extract shared logic, ensuring typed contracts and consistent design token integration across all UI components.

How do I add accessibility patterns to Vue 3 components?

Add accessibility to Vue 3 components by implementing built-in ARIA attributes, keyboard handling, and focus management to ensure production readiness, validating these interactions through included component testing patterns.

Can I convert Figma designs into reusable Vue 3 components?

Yes, you can convert Figma designs into reusable Vue 3 components by translating visual elements into typed primitives like VButton and VInput, applying design tokens for variants and sizes while maintaining predictable TypeScript contracts.

Does this approach work for component libraries that need composable-based logic extraction?

Yes, this approach works for component libraries by using composable-based logic extraction to separate concerns, allowing teams to define typed props and emits while consuming shared design tokens to avoid duplicated logic and brittle components.

Why should I use design tokens instead of hardcoded styles in Vue 3 components?

Use design tokens instead of hardcoded styles in Vue 3 components to provide a clear, repeatable pattern for styling, ensuring teams avoid inconsistent UI and duplicated logic while maintaining token-driven styling via CSS custom properties or provide/inject.