vercel/swr
GitHubReact Hooks for Data Fetching
- Stars:
- 32.5k
- Language:
- TypeScript
- Default branch:
- main
- Last scored:
At a glance
- Rank
- #183 of 401
- Top 46% · #52 of 82 TypeScript repos
- Checks passed
- 9 of 17
- Full list below
- Best set up for
- Claude Code
- Score 74.2
- 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
- 3Reproducible dev envAdd a Makefile or devcontainer or Dockerfile so the agent can set up the project in one command.+4.7 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 vercel/swr 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 vercel/swr. React Hooks for Data Fetching. Written mainly in TypeScript.
## Where things are
- Dependencies are declared in `package.json`.
- Tests live in `test`.
- Type checking is configured in `tsconfig.json`.
- CI is defined in `.github/workflows`; read it for the exact install, lint and test steps.
- Commit hooks are set up in `.husky`; don't skip them.
- Project tasks are the `scripts` in `package.json`.
- Follow the conventions in `.github/CONTRIBUTING.md`.
## Commands
<!-- Fill in the exact commands CI runs. -->
- Install: TODO
- Test: TODO
- Lint: TODO
All 17 checks · 9 passed
How vercel/swr compares
- vs leaderboard average
- 2.4 pts above
- Average 66.8
- vs TypeScript average
- 2.0 pts below
- Average 71.2
- Stars among TypeScript repos
- #54 of 82
Missing here, and how many repos have it
- Linter / formatter config · passed by 65% of leaderboard repos, 57% of TypeScript repos
- Skills (.agents/skills) · passed by 17% of leaderboard repos, 30% of TypeScript repos
- Cursor rules (.cursor/rules) · passed by 4% of leaderboard repos, 13% of TypeScript repos
Passes checks most repos miss
- Pre-commit / git hooks · only 29% of repos pass it
- Manageable size · only 16% of repos pass it
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 · 114.5k ★
- refinedev/refine69.6TypeScript · 36k ★
- solidjs/solid69.5TypeScript · 36.2k ★
- prisma/orm69.3TypeScript · 47.7k ★
- TanStack/ai69.2TypeScript · 3.3k ★
- TypeScript · 118.2k ★
Same topics, any language
Repos tagged with the same GitHub topics, most shared first.
- TanStack/query63.6TypeScript · cache, data, fetch, hooks, stale while revalidate
- vercel/next.js86.9JavaScript · Next.js, vercel
- vercel/ai67.7TypeScript · Next.js, vercel
- TypeScript · Next.js, react native
- pmndrs/zustand72.8TypeScript · hooks
- sindresorhus/ky66.8TypeScript · fetch
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/vercel/swr)Check the score on every pull request
A GitHub Action posts one comment per pull request with how the score changed and why.