vitejs/vite
GitHubNext generation frontend tooling. It's fast!
- build-tool
- dev-server
- frontend
- hmr
- vite
- Stars:
- 83.7k
- Language:
- TypeScript
- Default branch:
- main
- Last scored:
At a glance
- Rank
- #365 of 401
- #78 of 82 TypeScript repos
- Checks passed
- 5 of 17
- Full list below
- Best set up for
- Devin
- Score 55.1
- Needs most work for
- Cursor
- Biggest fix: Cursor rules (.cursor/rules) (+11.5 pts)
What it has
What it's missing
What to fix first
Showing fixes for Claude Code
- 1AGENTS.md / CLAUDE.mdAdd an AGENTS.md covering project goals, layout, setup commands, and conventions. Aim for 800+ chars of real guidance (not boilerplate).+13.2 pts
- 2Linter / formatter configConfigure a linter/formatter (ESLint+Prettier, Biome, Ruff, rustfmt+clippy, golangci-lint) and commit the config.+7.9 pts
- 3Type configurationAdd a type config (tsconfig.json for JS/TS, mypy.ini or pyrightconfig.json for Python). Rust/Go/JVM/Scala/Swift/C#/OCaml/Haskell/Zig are typed by default.+7.9 pts
Score for each AI agent
Each agent weighs the checks by its own docs. Under each score are its top three. How each agent is scored →
Does vitejs/vite have agent instructions?
An AGENTS.md (or CLAUDE.md) at the root tells AI coding agents how to build, test and work in the repo. A few agents also read a file of their own.
- AGENTS.md / CLAUDE.md
- None at the root (no AGENTS.md, CLAUDE.md, AGENT.md, .claude/CLAUDE.md or .claude/AGENTS.md)
- Agent-specific files
- None: no GEMINI.md, .cursor/rules, .openhands/setup.sh, .aider.conf.yml or .agents/skills
- Repos that have one
- 62 of 82 TypeScript repos · 221 of 401 repos on the leaderboard · See examples →
Get a starter AGENTS.md
From the files the checks found. Fill in the commands, then commit it at the root.
# AGENTS.md
Guidance for AI coding agents working in vitejs/vite. Next generation frontend tooling. Written mainly in TypeScript.
## Where things are
- Dependencies are declared in `package.json`.
- Test files are spread through the tree, e.g. `packages/create-vite/__tests__/cli.spec.ts`.
- CI is defined in `.github/workflows`; read it for the exact install, lint and test steps.
- Project tasks are the `scripts` in `package.json`.
- Follow the conventions in `CONTRIBUTING.md`.
## Commands
<!-- Fill in the exact commands CI runs. -->
- Install: TODO
- Test: TODO
- Lint: TODO
All 17 checks · 5 passed
How vitejs/vite compares
- vs leaderboard average
- 16.9 pts below
- Average 66.8
- vs TypeScript average
- 21.3 pts below
- Average 71.2
- Stars among TypeScript repos
- #19 of 82
Missing here, and how many repos have it
- Type configuration · passed by 68% of leaderboard repos, 68% of TypeScript repos
- Linter / formatter config · passed by 65% of leaderboard repos, 57% of TypeScript repos
- Pre-commit / git hooks · passed by 29% of leaderboard repos, 48% of TypeScript repos
One fix for the most agents: Linter / formatter config would raise the score for all 9 agents, by up to 14.1 points.
Similar repos
Same language and host as this repo, closest in overall score.
- TypeScript · 24.4k ★
- TypeScript · 36.7k ★
- TypeScript · 198.5k ★
- TypeScript · 154.5k ★
- TypeScript · 39.5k ★
- cloudflare/ai46.7TypeScript · 1.2k ★
Same topics, any language
Repos tagged with the same GitHub topics, most shared first.
- expo/expo74.0TypeScript · frontend
- react/react64.1JavaScript · frontend
- nrwl/nx86.3TypeScript · build tool
- webpack/webpack82.3JavaScript · build tool
- vercel/turborepo79.9Rust · build tool
- TypeScript · vite
Add a badge to your README
Paste this at the top of the README. It shows the score, and links back to this page.
[](https://agentfriendlycode.com/repo/github/vitejs/vite)Check the score on every pull request
A GitHub Action posts one comment per pull request with how the score changed and why.