vue-component-scaffolder

name	vue-component-scaffolder
audience	team
description	Scaffolds a single Vue / TypeScript single-file component (SFC) or route with typed props via defineProps, a co-located Vue Testing Library test, an accessibility baseline, and an optional Storybook story. Vue analog of fastapi-scaffolder — the SFC/route is the front-end "unit". Use when creating a new Vue component, adding a route/page, generating a typed presentational or container SFC, or standing up a component with its test and story.

Vue Component Scaffolder

"A component is a contract. Make its props explicit, its output accessible, its behavior tested." -- Adapted from API design practice

"Accessibility by default means the inaccessible path requires more work than the accessible one." -- Adapted from OWASP Secure Design Principles

Core Philosophy

A Vue SFC is the front-end unit the way an endpoint is the back-end unit. Like an endpoint, it has a contract (its props/emits), an output that must be safe and well-formed (accessible, escaped template interpolation), and a test that proves it behaves. A component shipped without typed defineProps, a test, and an accessibility baseline is a black box that future changes will break silently.

Accessibility by default means semantic HTML and keyboard support are the scaffold, not a follow-up ticket. The inaccessible <div @click> must be the path that requires extra justification.

Grounding note: the KB has a Vue 2/3 corpus under collection="javascript" (alongside TS). Use collection="ui_ux" for WCAG/ARIA and cite vuejs.org for component/composable patterns. Never invent a vue collection.

Non-Negotiable Constraints:

1. Typed props — every component uses defineProps<Props>(); no implicit any
2. Test co-located — a *.test.ts is created with the component, not after
3. Accessible by default — semantic elements, labels, keyboard reachability; eslint-plugin-vuejs-accessibility clean
4. Presentational by default — a new component takes data + emits via props; data fetching is opt-in and explicit
5. No business logic in the template — branching/logic goes in a composable or a computed

What this skill is NOT:

• It is NOT a feature-architecture tool — use vue-feature-slice to organize many components
• It is NOT an app bootstrapper — use vue-app-scaffolder to create the project skeleton
• It is NOT a styling system — bring your own (CSS Modules, Tailwind, etc.)

The 10 domain principles, KB lookup queries, AI discipline rules, anti-patterns, and error-recovery procedures live in references/conventions.md.

Workflow

Phase 1: DETECT

# Vue + TS + test runner + storybook
grep -E '"(vue|typescript|vitest|@testing-library/vue|@storybook)"' package.json

# Where components live and the existing convention
find src -type d -name components | head
ls src/features 2>/dev/null

# Test + story file conventions already in use
find src -name "*.test.ts" | head -3
find src -name "*.stories.ts" | head -3

Record: Vue version, test runner (Vitest), whether Storybook is present, naming/location convention.

Phase 2: SCAFFOLD

Objective: Create the component with its typed props, test, and (optional) story.

See references/component-template.md for full skeletons (presentational, container, form).

src/<location>/<Name>/
  <Name>.vue               # the component (presentational by default)
  <Name>.test.ts            # component test (co-located, required)
  <Name>.stories.ts         # Storybook story (optional)
  index.ts                  # re-export

Phase 3: ACCESSIBILITY

Objective: Meet the a11y baseline. See references/accessibility-baseline.md.

npx eslint src/<location>/<Name> --plugin vuejs-accessibility

Phase 4: VERIFY

npx vue-tsc --noEmit
npx eslint src/<location>/<Name>
npx vitest run src/<location>/<Name>
# Story renders (if Storybook present):
npx storybook build --quiet >/dev/null 2>&1 && echo "stories build OK"

State Block

<vue-component-scaffold-state>
  phase: DETECT | SCAFFOLD | ACCESSIBILITY | VERIFY | COMPLETE
  component_name: [name]
  kind: presentational | container | form | route
  test_runner: vitest
  storybook_present: true | false
  props_typed: true | false
  test_created: true | false
  a11y_clean: true | false | not_run
  last_action: [description]
  next_action: [description]
</vue-component-scaffold-state>

Output Template

The scaffold checklist (Contract / Accessibility / Tests / Story / Verification) lives in references/conventions.md under "Output: Scaffold Checklist". Emit it filled-in at COMPLETE.

Integration with Other Skills

Skill	Relationship
vue-feature-slice	Provides the feature structure; this skill generates the individual components inside a slice.
vue-app-scaffolder	Stands up the project (Vite + TS + Vitest + Storybook) this skill scaffolds components into.
vue-security-review	After scaffolding, audit link/URL handling and any v-html usage in the component.
vue-architecture-checklist	Quality gate for reactivity discipline and render performance across components.
tdd	Drive the component test-first (RED → GREEN → REFACTOR) instead of scaffolding code ahead of the test.