This skill covers the points where Vue JSX departs from React JSX. Its one reference explains why Vue uses class and for as attribute names, how to set jsx and jsxImportSource in tsconfig.json, and how to register the Vue JSX plugin in a Vite project.
It is useful when migrating React components to Vue or when TypeScript reports attribute type errors in a Vue JSX file.
What You Get
- Correct and incorrect examples of Vue JSX attributes
- A table mapping React names such as className and htmlFor to Vue names
- tsconfig settings: jsx preserve and jsxImportSource vue
- A vite.config.ts example with the Vue JSX plugin
Common Use Cases
- Migrating a React component to Vue JSX
- Fixing TypeScript errors about className or htmlFor in a Vue project
- Setting up JSX support in a new Vite and Vue project
What Makes It Unique
It targets one translation problem, React habits in Vue JSX. The reference notes that Vue’s runtime tolerates React names but its types reject them, which explains why errors appear only under strict TypeScript.
Under The Hood
The agent loads a tiny Markdown file and reads one reference when JSX is involved. There are no scripts. The skill does not tell the agent to fetch web pages, call APIs or run commands. The agent may edit tsconfig.json and vite.config.ts in your project if you ask for JSX setup.