Skills that make coding agents more reliable.
Browse curated, copy-ready instructions for AI coding assistants. Filter by assistant, discipline, setup file, and task type.
124 skills
Showing 1-24 of 124
Portable instructions
Skills map the same workflow into files like AGENTS.md, CLAUDE.md, .cursorrules, and .windsurfrules so teams can reuse agent behavior across tools.
Task-specific behavior
Each skill includes trigger phrases, use cases, and focused guidance so the assistant knows when to switch into a specialized workflow.
Built for real teams
Use them to standardize design reviews, SEO audits, analytics work, performance fixes, and development practices across projects.
Rules your assistant can actually follow
Agent skills are project instructions, not magic prompts.
A good skill tells the assistant when to slow down, what files to inspect, which standards matter, and how to report the work. That sounds plain because it is. The payoff is that Claude, Cursor, Windsurf, OpenCode, Cline, and Copilot stop guessing your process every time you open a new task.
Pick
Choose a skill by the work, not by the assistant. SEO audit, code review, UI polish, analytics setup, and MCP building all need different instructions.
Paste
Copy the generated rules into the config file your assistant reads. Keep it close to the repo so the workflow travels with the code.
Tune
Add project details: stack, tone, test commands, accessibility rules, analytics naming, or anything your team repeats every week.
Build skill stacks for the work you repeat.
Most teams do not need one giant rules file. They need a small stack that matches how they ship.
Growth stack
AI SEO, content refresh, schema, analytics, CRO
Frontend stack
UI design, accessibility, React performance, responsive QA
Engineering stack
Code review, tests, TypeScript, API design, security