Vue App taste — ChatGPT prompt: what it does, how to install
The Vue App taste ChatGPT prompt sets conventions for building Vue applications. It covers framework choice, component patterns, data handling, and tests.
CC0-1.0 ★ 178,201 updated 2026-10-24
Open on GitHubWhat Vue App taste does
The prompt lays out conventions for starting and maintaining Vue apps. It pairs Vite with Vue 3 for new projects and points to Nuxt when server rendering or file-based routing is needed. Components use Composition API with script setup, and TypeScript applies throughout; template checks with vue-tsc belong in CI.
For shared client state, it selects Pinia; for server data, it names TanStack Query for Vue or Nuxt useFetch. Reusable logic goes into composables, with VueUse suggested for common browser APIs. Other rules cover list keys, conditional rendering, styles, and lazy route imports. Component tests use Vitest and Vue Testing Library, while ESLint and Prettier handle code checks and formatting. The Claude Code file path is .claude/commands/prompts.csv.md.
What it helps with
- choose between Vite with Vue 3 and Nuxt
- set conventions for Vue components and typing
- organize client state and server-data fetching
- define testing and code-checking practices
Example prompts for the agent
- Start a Vue 3 app and follow the Vue App taste prompt.
- Refactor these components to use Composition API,
script setup, and TypeScript. - Set Vue project conventions for data fetching, tests, and styling.
How to install Vue App taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Vue App taste
How do I install Vue App taste in Claude Code?
The Claude Code file path is .claude/commands/prompts.csv.md.
What does Vue App taste do?
It provides Vue development conventions, including framework choice, component structure, typing, state management, testing, and styles.
Which testing tools does Vue App taste recommend?
It names Vitest and Vue Testing Library for component tests, with queries based on roles and text.
Source text
prompts.csv · CC0-1.0
# Vue App taste of a frontend engineer - Start new projects with Vite and Vue 3, or Nuxt when server rendering or file-based routing is needed. Confidence: 0.90 - Write components with script setup and the Composition API, not the Options API. Confidence: 0.90 - Use TypeScript everywhere and check templates with vue-tsc in CI. Confidence: 0.90 - Type props and emits with defineProps and defineEmits generics instead of runtime-only declarations. Confidence: 0.85 - Use Pinia for shared client state and keep stores small and focused on one domain. Confidence: 0.85 - Fetch server data with TanStack Query for Vue or Nuxt useFetch instead of hand-rolled loading flags in stores. Confidence: 0.80 - Extract reusable logic into composables named useSomething that return refs and functions. Confidence: 0.90 - Reach for VueUse before writing a custom composable for common browser APIs. Confidence: 0.75 - Prefer computed over watch, and use watch only for side effects. Confidence: 0.90 - Never mutate props; emit events or use defineModel for two-way binding. Confidence: 0.95 - Always give v-for items a stable key from the data, never the index. Confidence: 0.90 - Never combine v-if and v-for on the same element. Confidence: 0.90 - Keep components under about 200 lines and split them when the template gets hard to scan. Confidence: 0.70 - Use multi-word PascalCase component names and colocate components by feature, not by type. Confidence: 0.80 - Style with scoped CSS or Tailwind, and avoid global styles beyond a small reset and design tokens. Confidence: 0.75 - Lazy load route components with dynamic imports in Vue Router. Confidence: 0.85 - Test components with Vitest and Vue Testing Library, querying by role and text. Confidence: 0.85 - Lint with ESLint and eslint-plugin-vue using the recommended rules, and format with Prettier. Confidence: 0.85 - Avoid provide and inject for app state; use it only for component library internals and deep config. Confidence: 0.70 - Sanitize any HTML before using v-html, or better, avoid v-html altogether. Confidence: 0.95
© f · CC0-1.0 · f/prompts.chat