Claude Code Skills
A collection of 49 reusable Claude Code skills for software engineering workflows.
Claude Code Skills
A collection of 49 reusable Claude Code skills for software engineering workflows. Drop them into any project's .claude/skills/ directory and get structured, opinionated guidance for the full engineering lifecycle.
Covers architecture, code review, debugging, testing, security, deployment, CI/CD, database design, observability, and more - everything a development team needs, packaged as ready-to-use AI agent skills.
Built to the Agent Skills open standard. Compatible with Claude Code, Claude API, Claude Agent SDK, and claude.ai.
What Are Skills?
Skills are markdown files that give Claude domain-specific expertise for your project. They work like reusable prompt templates with structured instructions - Claude loads skill metadata at startup and reads full instructions on demand, so only the relevant skill enters the context window.
You can invoke skills manually (/review, /scope-check) or let Claude use them automatically when relevant. Skills work in the CLI, IDE extensions, the API, and claude.ai.
For the full spec, see Agent Skills Overview and Best Practices.
Skills (49)
Core Dev Workflow
| Skill | Invoke | Description |
|---|---|---|
| architect | auto | System architecture - diagrams, concurrency models, design decisions |
| review | auto | Code review - performance, correctness, security, code quality |
| bug | auto | Bug investigation - categorize, trace root cause, fix, prevent |
| testing | auto | Testing strategy - what to test, how to test, coverage targets |
| workflow | auto | Git workflow - branching, commits, PRs, merge process |
| build | /build | Build & deploy - multi-language commands, release checklist |
| perf | auto | Performance audit - response time, memory, CPU, database, network |
| best-practices | auto | Code quality - separation of concerns, error handling, thread safety |
| scope-check | /scope-check | Feature creep guard - evaluate proposals against core goals |
| dev-setup | /dev-setup | Dev environment setup - prerequisites, install, configure, verify |
| phase-gate | /phase-gate | Milestone evaluation - deliverables, gate criteria, readiness |
| tech-stack | auto | Technology decisions - evaluation framework, dependency health |
| telemetry | auto | Observability - error tracking, metrics, logging, analytics |
| debug-latency | auto | Latency diagnosis - full request path tracing |
| qa | /qa | QA & user testing - session guides, checklists, metrics |
Engineering Practices
| Skill | Invoke | Description |
|---|---|---|
| refactor | auto | Safe refactoring - code smells, transformations, behavior preservation |
| migrate | auto | Migration planning - database, API, dependency, platform |
| security-audit | auto | Security audit - OWASP Top 10, auth, input validation, secrets |
| api-design | auto | API design - REST conventions, errors, pagination, versioning |
| api-integration | auto | Third-party APIs - client design, auth, webhooks, rate limits |
| incident | auto | Incident response - triage, mitigation, post-mortems |
| docs | /docs | Documentation - ADRs, runbooks, API docs, review |
| dependency-update | auto | Dependency updates - audit, risk assessment, security patches |
| deploy | auto | Deployment - strategies, pre/post checks, rollback |
| estimate | /estimate | Work estimation - task breakdown, complexity, risk flags |
| onboard | auto | Project onboarding - codebase overview, key files, workflows |
| pr-author | auto | PR authoring - sizing, self-review, descriptions, stacking |
Infrastructure & Ops
| Skill | Invoke | Description |
|---|---|---|
| ci-cd | auto | CI/CD pipelines - stages, caching, secrets, optimization |
| database-design | auto | Database design - schema, indexing, migrations, EXPLAIN |
| containerize | auto | Containerization - Dockerfiles, multi-stage builds, Compose |
| iac | auto | Infrastructure as Code - Terraform, state, modules, drift |
| monitoring | auto | Monitoring & alerting - golden signals, SLOs, dashboards |
| logging | auto | Structured logging - levels, correlation IDs, aggregation |
| caching | auto | Caching - placement, invalidation, stampede prevention |
| error-handling | auto | Error handling - retry, circuit breakers, degradation |
| config-management | auto | Configuration - env vars, feature flags, secrets, validation |
Architecture & Data
| Skill | Invoke | Description |
|---|---|---|
| data-modeling | auto | Domain modeling - entities, relationships, aggregates, state machines |
| schema-evolution | auto | Schema evolution - expand-contract, compatibility, coordination |
| async-patterns | auto | Async workflows - queues, pub/sub, events, eventual consistency |
| state-management | auto | Client state - server state, URL state, derived state |
| data-pipeline | auto | Data pipelines - ETL/ELT, idempotency, backfill, quality checks |
Reliability & Operations
| Skill | Invoke | Description |
|---|---|---|
| rollback | auto | Rollback - code, database, config, feature flags |
| load-testing | auto | Load testing - targets, realistic scenarios, bottleneck analysis |
| feature-flag-ops | auto | Feature flags - progressive rollout, kill switches, cleanup |
| observability-debug | auto | Production debugging - metrics + logs + traces correlation |
| git-recovery | auto | Git recovery - force-push, broken rebase, lost commits |
| tech-debt | auto | Tech debt - inventory, prioritize, business case, paydown |
Cross-Cutting
| Skill | Invoke | Description |
|---|---|---|
| accessibility | auto | Accessibility - WCAG 2.1, keyboard nav, screen readers |
| i18n | auto | Internationalization - string extraction, plurals, RTL, locales |
auto = Claude invokes automatically when relevant. /command = user invokes manually.
Quick Start
# Copy all skills into your project
git clone https://github.com/pvnarp/agent-skills.git /tmp/agent-skills
cp -r /tmp/agent-skills/skills/ .claude/skills/
# Or copy individual skills
cp -r /tmp/agent-skills/skills/review/ .claude/skills/review/
Install globally (all projects)
cp -r /tmp/agent-skills/skills/* ~/.claude/skills/
Symlink (stays up to date with pulls)
git clone https://github.com/pvnarp/agent-skills.git ~/.agent-skills
ln -s ~/.agent-skills/skills/ your-project/.claude/skills
Customization
These skills are intentionally generic. Customize for your project:
- Edit the skill - Add project-specific conventions, tools, or patterns
- Add reference files - Create a
reference/subdirectory for additional context (progressive disclosure - only loaded when needed) - Adjust frontmatter - Control invocation behavior
Frontmatter Reference
---
name: skill-name # Lowercase, hyphens, max 64 chars
description: What it does and when # Max 1024 chars, third person
user-invocable: true # Show in /command menu (default: true)
disable-model-invocation: true # Only manual invocation (default: false)
allowed-tools: Read, Grep, Glob # Restrict tool access when active
context: fork # Run in isolated subagent
argument-hint: "[issue-number]" # Hint shown during autocomplete
---
Skill Structure
my-skill/
├── SKILL.md # Main instructions (required, keep under 500 lines)
├── reference/
│ ├── patterns.md # Detailed reference (loaded on demand)
│ └── examples.md # Examples (loaded on demand)
└── scripts/
└── validate.sh # Utility scripts (executed, not loaded into context)
Authoring Guidelines
Following the official best practices:
- Be concise - Claude is already smart. Only add context it doesn't already have.
- Be opinionated - Take a stance. Generic advice is useless.
- Be structured - Checklists, tables, templates. Claude follows structure well.
- Include output formats - Tell Claude exactly how to format its response.
- Write descriptions in third person - "Designs..." not "I help you design..."
- Include "Use when..." - Help Claude know when to invoke the skill.
- Keep SKILL.md under 500 lines - Split into reference files for detailed content.
- One level of references - Link from SKILL.md to reference files, not deeper.
- Test with real tasks - Use the skill in a real project before sharing.
Why This Exists
I kept rebuilding the same skills across different projects. Every time I started something new, I'd write a review skill, an architecture skill, a testing skill... and they'd all end up slightly different but mostly the same.
So I pulled out the ones that kept working well across projects, cleaned them up, and put them here. These have been tested across a mix of backend APIs, frontend apps, CLI tools, and infrastructure work. Some started rough and got better after I noticed where Claude was giving me weak advice and tightened the instructions.
If a skill works for you, great. If it doesn't, open an issue or PR and I'll fix it.
Contributing
See CONTRIBUTING.md for guidelines on adding new skills or improving existing ones.