Install
pnpx skills add antfu/skills --skill='*'Who it's for
Use this curated set when your day-to-day is mostly Vite or Nuxt and you want a coding Agent to read Anthony Fu’s preferences, experience, and tool-usage notes first, instead of a generic frontend template. It follows the Agent Skills format and groups skills from different sources and scopes, aiming to be a one-stop Vite/Nuxt collection. The author calls it a proof of concept: skills are generated from source docs and kept in sync, and he has not fully tested real-world results; feedback is welcome. It fits people willing to treat output as advice and check it against the current project. If you still use other frameworks, or need skills already stably accepted, read the limits first. The page does not list concrete skill names and does not name clients; do not invent a roster or exclusive support.
First try in 3 minutes
Use only this official in-project install, installing all skills:
pnpx skills add antfu/skills --skill='*'
Quotes and the asterisk in the command must match the page. Do not change it to npx or any installer that never appears. The same page also has a global install with -g; that affects more projects and is not the first-try default path.
After install, open an existing Vite or Nuxt repository. The first time, do a read-only check: ask the Agent which kind of tool-usage notes from the set it plans to use to answer a question about the current config, for example explaining what the existing Vite config does. Have it repeat first: this is a proof of concept, the author has not fully tested it, and it will only explain, not change files. Allow it to read files only after you confirm. Success is an answer that matches the real config in your repo, without inventing short skill names the page never listed.
If the Agent starts changing config or adding plugins, interrupt. Official text welcomes feedback and contributions; that does not mean you must change the repo first.
Use cases
Case 1: Ask tool usage in a Vite/Nuxt project using the author’s preferences. After installing all skills, ask about build, the dev server, or Nuxt conventions in the current repo; require a citation of the usage notes in the skills, then a check against your files. This reduces generic framework advice. The page gives no skill directory, so do not pre-fill skill names; discard advice that does not match the files.
Case 2: Install globally, then verify in another project. The official second command is the same install plus -g. For people who want several Vite/Nuxt repos to see the same preference set. Before a global write, confirm you accept it affecting other projects. Switch to another repo and do the same read-only explanation to see whether the set is still loaded. Do not point -g at an undocumented directory, and do not invent uninstall steps.
Boundaries
Default install is pnpx skills add antfu/skills --skill='*'. -g is the global variant, not part of the first command. This is a proof of concept; the author has not fully tested behavior. Skills are generated from source docs and synced; results are whatever you verify locally. The set targets Vite/Nuxt and mixes sources and scopes; do not treat it as an official spec for every frontend stack, and do not infer extra install entries from the author’s homepage. The page gives no client roster, secrets, or short skill names. Do not invent undocumented paths or marketplace commands. Repository page:
https://github.com/antfu/skills