WXT Skill para Claude Code
meiazero/wxt-skill
Skill de referência para extensões web com WXT no Claude Code
Ver no GitHubSkill que ensina Claude Code a construir extensões web cross-browser com WXT (Chrome/Firefox, MV2/MV3) sem os erros comuns. Fornece mental model, regras decisórias e referência completa das APIs do framework.
Instalação
npx convez-ai meiazero/wxt-skill1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Gerar código correto de extensões web cross-browser com WXT
- Evitar erros de configuração de manifest, entrypoints e APIs
- Consultar rapidamente assinaturas de APIs e padrões do WXT
Veredito

Skill bem documentado que resolve problema real: WXT quebra padrões de extensões tradicionais e um agente precisa de referência precisa. O bundle inclui SKILL.md com mental model, 11 arquivos de referência checados contra fonte, e script para puxar docs live. Prático e atualizado.
README
A tradução para o português deste README ainda está na fila.
WXT skill
Helps Claude Code write WXT (wxt.dev) extension code without the usual mistakes, and works as a quick reference for me too.
WXT is a framework for cross-browser extensions (Chrome/Firefox, MV2/MV3) built on Vite. It does a
few things that throw off an agent working from general extension knowledge: there's no
manifest.json in your source (WXT generates it), most APIs are auto-imported, and entrypoint files
get run in Node at build time. Without the rules in here, an agent tends to guess and get it wrong.
What's in it
wxt/
├── SKILL.md # start here: mental model, the rules that matter, decision tables
├── reference/ # 11 files, one per WXT area, with the real signatures and patterns
└── scripts/
└── fetch-wxt-doc.sh # pull any official doc page as markdown
SKILL.md is the entry point. It has the mental model, the rules worth knowing, and a few decision
tables: what entrypoint a filename creates, which content-script UI helper to use, how to set up
storage.
The reference/ files cover project structure, entrypoints, content scripts and content-script UI,
config and manifest, the browser global and cross-browser targeting, storage, messaging and i18n,
assets, frameworks and modules, testing, and the CLI. I pulled them from the official .md docs and
then checked each one back against the source, so the API names, options and CLI flags should match
what WXT actually ships. The first pass had about 30 things wrong; those got fixed.
scripts/fetch-wxt-doc.sh grabs any doc page when something isn't covered here. WXT publishes a .md
for every page, so this stays current even when the bundled files fall behind.
Using it
The skill loads on its own when you're in a WXT project (a wxt.config.ts, an entrypoints/ folder,
or the wxt CLI), working on a background/content/popup/options/sidepanel entrypoint, or touching the
manifest. Run /wxt to load it by hand.
If you're an agent: read SKILL.md first, then open the matching reference/*.md when you need exact
details. Don't guess an API — use the fetch script instead.
Fetching live docs
scripts/fetch-wxt-doc.sh # table of contents
scripts/fetch-wxt-doc.sh search messaging # find a page by keyword
scripts/fetch-wxt-doc.sh guide/essentials/content-scripts # one page as markdown
scripts/fetch-wxt-doc.sh full | grep -n -A30 createShadowRootUi
Slugs, absolute paths, and full URLs all work; it adds the .md for you.
Updating
The reference files are current as of mid-2026. WXT moves fast, so when in doubt run the fetch script (it reads the live docs). To redo a file, re-pull it from the source and check it before saving.
License
MIT, see LICENSE. The reference text comes from WXT's own docs, which are MIT too.