Vue Component Formatter skill for Claude and Codex
Assembles the template markup, state, and methods you already have into one clean, lint-ready Vue single-file component with Composition API conventions…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when you already have the markup, state, and methods for a Vue component as loose pieces and want them combined into one lint-clean single-file component. Do not use for designing a component from a spec with nothing written, or breaking an oversized component into smaller ones. Related topics: coding, vue.
What it will ask you for
- Component name (free text, e.g. "ProfileForm")
- Template markup (longer free text)
- Props (longer free text)
- Reactive state (longer free text)
- Methods and functions (longer free text)
- Script style (choose one: Vue 3 script setup, Vue 3 Composition API with setup(), Vue 2 Options API)
- Styles (choose one: Scoped, Global, None)
- Lint rules (choose one: eslint-plugin-vue recommended, Prettier plus Vue recommended, Project default)
How it works
- Place the supplied template, script, and style in the conventional order for the chosen style; nothing is added or dropped.
- Convert state and functions to the chosen script style (ref, reactive, setup or Options API) with their bodies unchanged.
- Apply naming conventions: PascalCase component, camelCase script identifiers, kebab-case template events and attributes.
- Fix the lint rules the recommended config flags: v-for keys, v-if and v-for separation, void element closing, attribute order.
- List each lint fix applied and each reference in the template that no supplied piece defines.
What you get
One vue code block with the assembled single-file component, then a bulleted list of lint fixes applied and unresolved references.
What it watches out for
- Rewriting the supplied method bodies while converting them, which changes behaviour the author did not ask to change.
- Leaving v-for without a key or combining it with v-if, which the recommended rules reject on the first lint run.
- Inventing a fetch call or default styling to fill a gap instead of listing the gap for the author.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.