AI Coding Skills
The techniques, knowledge, and agent skills that make AI-assisted development actually work. Curated for quality — every entry is relevant, documented, and maintained.
How to Use This Hub
Skills are grouped by category. If you're new to AI-assisted development, start with Rapid Prototyping Skills then move to Prompt Engineering. If you're already building, explore Agent Skill Directories and Spec-Driven Development to level up.
Agent Skill Directories
Open directories and registries for installing procedural knowledge into AI coding agents.
Prompt Engineering Skills
The core skill of communicating effectively with AI coding tools — from basic prompting to advanced techniques.
Prompt Engineering for AI Code Tools
The 5 golden rules for talking to AI coding assistants effectively.
Read moreMastering Cursor Composer
Advanced prompting and multi-file editing techniques for Cursor.
Read moreAdvanced Vibe Coding Techniques
Level up from basics — context management, multi-file refactors, and production patterns.
Read moreSpec-Driven Development
Skills for structuring AI work with specifications, plans, and task files — keeping projects on track as they grow.
Rapid Prototyping Skills
Skills for going from idea to deployed prototype as fast as possible using AI builders.
Frequently Asked Questions
What are AI coding skills?
AI coding skills are specific techniques, knowledge packages, or procedural instructions that make AI coding agents more effective. They range from prompt engineering patterns to installable skill files (like Skills.sh) that give agents domain-specific expertise.
How are skills different from tools?
Tools are the software products you use (Cursor, Claude Code, Bolt.new). Skills are the techniques and knowledge that make you — and your AI agents — more effective with those tools. Think of tools as instruments and skills as the ability to play them well.
How does curation work on this page?
Every skill listed here meets our inclusion criteria: it must be directly relevant to building software, have a clear primary use-case, have accessible documentation, and show evidence of active maintenance. We exclude abandoned, vague, or low-trust entries.