Skip to content
SkillModel-led51 tokens in use

vue-jsx-best-practices

Shows an agent how Vue JSX differs from React JSX: HTML attribute names, TypeScript settings and the Vite plugin.

3,364 stars on the repository MIT Licensevuejs-ai/skills · skills/vue-jsx-best-practices
npx skills add vuejs-ai/skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing vue-jsx-best-practices costs

24tokens idle
51tokens in use
1,027tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Fair
  • Frontmatter11/15
  • Structure0/25
  • Examples3/15
  • Output0/15
  • Size13/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Fair
  • Development activity68
  • Maintenance40
  • Community52
  • Maturity32
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers