skills/antfu/antfu/SKILL.md
Anthony Fu's {Opinionated} preferences and best practices for web development
npx skillsauth add aiskillstore/marketplace antfuInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill covers Anthony Fu's preferred tooling, configurations, and best practices for web development. This skill is opinionated.
| Category | Preference |
|----------|------------|
| Package Manager | pnpm |
| Language | TypeScript (strict mode) |
| Module System | ESM ("type": "module") |
| Linting & Formatting | @antfu/eslint-config (no Prettier) |
| Testing | Vitest |
| Git Hooks | simple-git-hooks + lint-staged |
| Documentation | VitePress (in docs/) |
Use pnpm as the package manager.
For monorepo setups, use pnpm workspaces:
# pnpm-workspace.yaml
packages:
- 'packages/*'
Use pnpm named catalogs in pnpm-workspace.yaml to manage dependency versions:
| Catalog | Purpose |
|---------|---------|
| prod | Production dependencies |
| inlined | Dependencies inlined by bundler |
| dev | Development tools (linter, bundler, testing, dev-server) |
| frontend | Frontend libraries bundled into frontend |
Catalog names are not limited to the above and can be adjusted based on needs. Avoid using default catalog.
Use @antfu/ni for unified package manager commands. It auto-detects the package manager (pnpm/npm/yarn/bun) based on lockfile.
| Command | Description |
|---------|-------------|
| ni | Install dependencies |
| ni <pkg> | Add dependency |
| ni -D <pkg> | Add dev dependency |
| nr <script> | Run script |
| nu | Upgrade dependencies |
| nun <pkg> | Uninstall dependency |
| nci | Clean install (like pnpm i --frozen-lockfile) |
| nlx <pkg> | Execute package (like npx) |
Install globally with pnpm i -g @antfu/ni if the commands are not found.
Always use TypeScript with strict mode enabled.
{
"compilerOptions": {
"target": "ESNext",
"module": "ESNext",
"moduleResolution": "bundler",
"strict": true,
"esModuleInterop": true,
"skipLibCheck": true,
"resolveJsonModule": true,
"isolatedModules": true,
"noEmit": true
}
}
Always work in ESM mode. Set "type": "module" in package.json.
Use @antfu/eslint-config for both formatting and linting. This eliminates the need for Prettier.
Create eslint.config.js with // @ts-check comment:
// @ts-check
import antfu from '@antfu/eslint-config'
export default antfu()
Add script to package.json:
{
"scripts": {
"lint": "eslint ."
}
}
When getting linting errors, try to fix them with nr lint --fix. Don't add lint:fix script.
Use simple-git-hooks with lint-staged for pre-commit linting:
{
"simple-git-hooks": {
"pre-commit": "pnpm i --frozen-lockfile --ignore-scripts --offline && npx lint-staged"
},
"lint-staged": {
"*": "eslint --fix"
},
"scripts": {
"prepare": "npx simple-git-hooks"
}
}
Use Vitest for unit testing.
{
"scripts": {
"test": "vitest"
}
}
Conventions:
foo.ts → foo.test.ts (same directory)tests/ directory in each packagedescribe and it API (not test)expect API for assertionsassert only for TypeScript null assertionstoMatchSnapshot for complex output assertionstoMatchFileSnapshot with explicit file path and extension for language-specific output (exclude those files from linting)For library projects, publish through GitHub Releases triggered by bumpp:
{
"scripts": {
"release": "bumpp -r"
}
}
Use VitePress for documentation. Place docs under docs/ directory.
docs/
├── .vitepress/
│ └── config.ts
├── index.md
└── guide/
└── getting-started.md
Add script to package.json:
{
"scripts": {
"docs:dev": "vitepress dev docs",
"docs:build": "vitepress build docs"
}
}
| Topic | Description | Reference | |-------|-------------|-----------| | @antfu/eslint-config | ESLint flat config for formatting and linting | antfu-eslint-config | | GitHub Actions | Preferred workflows using sxzz/workflows | github-actions | | .gitignore | Preferred .gitignore for JS/TS projects | gitignore | | VS Code Extensions | Recommended extensions for development | vscode-extensions |
| Topic | Description | Reference | |-------|-------------|-----------| | App Development | Preferences for Vue/Vite/Nuxt/UnoCSS web applications | app-development | | Library Development | Preferences for bundling and publishing TypeScript libraries | library-development | | Monorepo | pnpm workspaces, centralized alias, Turborepo | monorepo |
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.