Anthony Fu's Skills
A skill set for the Vue, Vite and Nuxt stack: the author's conventions plus digests of official tool documentation
- 6,019 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The skills consist of documentation and conventions
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/anthony-fu-s-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skills consist of documentation and conventions
This is third-party code. Review the repository files before installing.
What it does
Anthony Fu, a Vue, Vite and Nuxt core team member, assembled three kinds of skills. Two are hand-maintained: antfu with his project setup for eslint, pnpm, vitest and vue, and antfu-design with UnoCSS and semantic token UI principles. vue, nuxt, pinia, vite, vitepress, vitest, unocss and pnpm are generated from official docs via git submodules and tuned by the author. The rest are synced from repositories where projects maintain their own skills: slidev, tsdown, turborepo, vueuse, Vue best practices and Vercel's web-design-guidelines.
Who it is for. For frontend developers working with Vue, Nuxt and Vite.
Good fit when
- The agent mixes up Vue, Nuxt or Vite APIs and needs current docs to lean on
- You want a new project set up with the author's conventions
- You need a UnoCSS interface with light and dark themes
Not a fit when
- Your project uses React or another stack
- You disagree with the author's personal tooling conventions
Example request
Add a server route for the order list to the Nuxt project and cover it with a Vitest testLimitations
The author calls the project a proof of concept and says he has not fully tested how well the skills work in practice. antfu and antfu-design reflect personal preferences. Vendored skills keep their original licenses.
How to disable. Remove the installed skills with the skills CLI or delete the skill folders from the agent's directory.
FAQ
How do the skills stay current?
Source docs are linked as git submodules, so skills can be regenerated when upstream changes.
Can I build my own collection this way?
Yes, the repository is meant as a template: fork, edit meta.ts, run pnpm start init and sync, then have the agent generate skills.
Discussion
No questions or reviews yet.
Related
SkillsA set of skills for Vue 3 development: Composition API practices, router, Pinia, testing, JSX, Options API and debugging
A skill that points the agent to ready VueUse composables for Vue 3 and Nuxt, with a usage and type reference for each function
shadcn-vue skill for agents
shadcn-vue skill
The shadcn-vue skill reads your project settings and teaches an agent to add components, forms and themes of the Vue port of shadcn/ui by its rules
Bitrix24 UI skill for Vue and Nuxt
Bitrix24 UI
Bitrix24's official skill for its 130-plus b24ui-nuxt components: which component to reach for, semantic colors, forms and ready layouts
Frontend Design (Ilm-Alan)
frontend-design
A frontend design skill with eight aesthetic anchors: each fixes palette, type and texture in CSS tokens. A separate project, not from Anthropic
Skills for the Symfony UX frontend stack: Stimulus, Turbo, TwigComponent, LiveComponent, UX Icons and UX Map, with patterns and gotchas
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Anthony Fu's Skills (this entry) | no | 6,019 | ||
| Nuxt MCP Dev | no | not required | 913 | a Nuxt module and a Vite plugin start an MCP server on the dev server |
| VueUse Skills | yes | 402 | a skill that points the agent to ready VueUse composables for Vue 3 |
README in short
The README splits skills into hand-maintained, generated from docs and vendored, with a source for each. Install with one skills CLI command. The author explains how skills differ from llms.txt and AGENTS.md and how to build your own collection from this template. MIT licensed.
README badge
Original SKILL.md
--- name: antfu-design description: antfu-style design conventions, broadened. UnoCSS-first, class-based semantic tokens with dual light/dark for tooling and devtools UIs, plus design-read, anti-slop, and micro-interaction polish for landing pages and product surfaces. Use when building or refactoring any interface with UnoCSS. metadata: author: Anthony Fu version: "2026.06.22" --- Use this when building interfaces with UnoCSS in any framework (React, Vue, Svelte, Solid, or plain HTML), from dense devtools panels to landing pages. Read core-design-read first to set the direction, then apply the token system plus the polish and anti-slop rules. ## Core Rules - Use semantic shortcuts (`bg-base`, `border-base`, `color-active`, `btn-action`) instead of raw utility chains in markup. - Design light and dark mode together. Core tokens must work in both themes. - Name z-index layers (`z-top-nav`, `z-panel-content`, `z-drawer-content`). Do not use raw z values in templates. - Generate class-based utilities only (`class="..."`). Avoid Attributify syntax in generated code. - Keep icon/status class strings literal so UnoCSS can statically extract them (`// @unocss-include` when needed). - Use `font-mono` + `tabular-nums` for technical values (paths, SHAs, counters, timestamps, percentages). - For long paths and IDs, truncate visually but keep the full value in `title`. - Read the brief and set the three dials before choosing a look (core-design-read). - Borders for dense or structural surfaces, layered shadows for elevated ones (features-micro-interactions). - Zero em-dash and en-dash characters in any user-facing text (best-practices-anti-slop).