antfu

Configure JavaScript/TypeScript projects with Anthony Fu's tooling conventions.

12|2|Updated Oct 13, 2025
One-click install
npx skills add https://github.com/pleaseai/claude-code-plugins --skill antfu-pleaseai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: antfu
Source: https://github.com/pleaseai/claude-code-plugins/tree/main/plugins/antfu/skills/antfu
Command: npx skills add https://github.com/pleaseai/claude-code-plugins --skill antfu-pleaseai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Anthony Fu's tooling conventions help standardize JavaScript/TypeScript projects, reducing setup time and decision fatigue.

Core Features & Use Cases

  • Establishes consistent project structure, ESLint/Prettier setups, and monorepo patterns.
  • Guides library publishing, tooling choices, and code organization for scalable projects.
  • Use Case: When starting a new JS/TS repo, apply Anthony Fu's conventions to align with community best practices.

Quick Start

Set up a new project following Anthony Fu's preferences to generate a consistent baseline configuration and folder structure.

Frequently Asked Questions about antfu

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a new TypeScript monorepo with ESLint and Prettier?

To set up a TypeScript monorepo, this Skill applies Anthony Fu's opinionated ESLint and Prettier configurations to establish a consistent project structure and standardize code organization across packages.

What are opinionated code conventions for JavaScript and TypeScript projects?

Opinionated code conventions provide predefined tooling choices and configurations for JavaScript and TypeScript projects, reducing decision fatigue and ensuring community best practices for scalable project scaffolding.

Can I use these TypeScript configurations for library publishing?

Yes, these TypeScript configurations are designed to guide library publishing by establishing a consistent baseline configuration, folder structure, and tooling setup for publish-ready project scaffolding.

Does this ESLint setup work for standardizing code organization across teams?

Yes, this ESLint setup standardizes code organization across teams by enforcing Anthony Fu's opinionated tooling conventions, ensuring consistent project structure and code formatting guidelines.

What is the best way to configure an opinionated TypeScript project from scratch?

The best way to configure an opinionated TypeScript project is to apply Anthony Fu's conventions, generating a consistent baseline configuration and folder structure tailored for scalable JavaScript and TypeScript setups.