{"id":"33afba76-2688-4242-9492-711dcd83b706","shortId":"uRx9Yd","kind":"skill","title":"antfu","tagline":"Anthony Fu's opinionated tooling and conventions for JavaScript/TypeScript projects. Use when setting up new projects, configuring ESLint/Prettier alternatives, monorepos, library publishing, or when the user mentions Anthony Fu's preferences.","description":"## Coding Practices\n\n### Code Organization\n\n- **Single responsibility**: Each source file should have a clear, focused scope/purpose\n- **Split large files**: Break files when they become large or handle too many concerns\n- **Type separation**: Always separate types and interfaces into `types.ts` or `types/*.ts`\n- **Constants extraction**: Move constants to a dedicated `constants.ts` file\n\n### Runtime Environment\n\n- **Prefer isomorphic code**: Write runtime-agnostic code that works in Node, browser, and workers whenever possible\n- **Clear runtime indicators**: When code is environment-specific, add a comment at the top of the file:\n\n```ts\n// @env node\n// @env browser\n```\n\n### TypeScript\n\n- **Explicit return types**: Declare return types explicitly when possible\n- **Avoid complex inline types**: Extract complex types into dedicated `type` or `interface` declarations\n\n### Comments\n\n- **Avoid unnecessary comments**: Code should be self-explanatory\n- **Explain \"why\" not \"how\"**: Comments should describe the reasoning or intent, not what the code does\n\n### Testing (Vitest)\n\n- Test files: `foo.ts` → `foo.test.ts` (same directory)\n- Use `describe`/`it` API (not `test`)\n- Use `toMatchSnapshot` for complex outputs\n- Use `toMatchFileSnapshot` with explicit path for language-specific snapshots\n\n---\n\n## Tooling Choices\n\n### @antfu/ni Commands\n\n| Command | Description |\n|---------|-------------|\n| `ni` | Install dependencies |\n| `ni ` / `ni -D ` | Add dependency / dev dependency |\n| `nr