code-virtuoso

In the author's own words, from each skill's SKILL.md — showing the first 30 of 47 files.

• accessibility

  Web accessibility patterns and WCAG 2.1/2.2 compliance for inclusive user interfaces. Use when the user asks to build accessible components, audit a UI for a11y issues, fix screen reader problems, implement keyboard navigation, check color contrast ratios, add ARIA attributes, create accessible forms, or establish accessibility standards for a team. Covers the POUR principles (Perceivable, Operab…

  skills/knowledge/accessibility/SKILL.md on GitHub (opens in a new tab)

• api-design

  REST and GraphQL API design principles for consistent, predictable, and evolvable APIs. Use when the user asks to design a new API, review an existing API, choose between REST and GraphQL, plan API versioning, define error response contracts, implement pagination, or establish API standards for a team. Covers resource modeling, endpoint naming, HTTP methods, status codes, authentication patterns,…

  skills/knowledge/api-design/SKILL.md on GitHub (opens in a new tab)

• cicd

  CI/CD pipeline patterns and deployment strategies for automated, reliable software delivery. Use when the user asks to design a build pipeline, choose a deployment model (blue-green, canary, rolling), configure environment promotion, manage build artifacts, implement zero-downtime deployments, set up quality gates, or improve delivery workflow speed and reliability. Covers pipeline stage ordering…

  skills/knowledge/cicd/SKILL.md on GitHub (opens in a new tab)

• clean-architecture

  Clean Architecture, Hexagonal Architecture (Ports and Adapters), and Domain-Driven Design fundamentals. Use when the user asks to design system architecture, define layer boundaries, apply DDD tactical patterns (entities, value objects, aggregates, repositories), structure a hexagonal application, enforce dependency rules, or evaluate whether a codebase needs architectural refactoring. Covers bou…

  skills/knowledge/clean-architecture/SKILL.md on GitHub (opens in a new tab)

• database-design

  Database design patterns and data modeling for relational and NoSQL databases. Use when the user asks to design a database schema, normalize or denormalize tables, create indexing strategies, plan schema migrations, model temporal data, implement audit trails, set up table partitioning, or optimize data access patterns. Covers entity relationships, naming conventions, constraint design, migration…

  skills/knowledge/database-design/SKILL.md on GitHub (opens in a new tab)

• debugging

  Systematic debugging methodology for finding and fixing bugs through root cause analysis. Use when the user encounters a bug, test failure, flaky behavior, production error, performance degradation, or integration failure. Covers the reproduce-investigate-hypothesize-fix-prevent workflow, evidence-based diagnosis, bug category strategies (logic errors, race conditions, memory leaks, integration f…

  skills/knowledge/debugging/SKILL.md on GitHub (opens in a new tab)

• design-patterns

  Comprehensive skill for all 26 Gang of Four design patterns with practical implementations and real-world examples. Use when the user asks to apply a design pattern, refactor code using patterns, choose between competing patterns, or review existing pattern usage. Covers creational (Abstract Factory, Builder, Factory Method, Prototype, Singleton, Object Pool), structural (Adapter, Bridge, Composi…

  skills/knowledge/design-patterns/SKILL.md on GitHub (opens in a new tab)

• dispatching-parallel-agents

  Patterns for effective subagent delegation and parallel execution. Use when a task decomposes into independent subtasks, when research spans multiple areas, when building features that require coordinated specialist work, or when sequential execution is wasting time. Covers work decomposition patterns (fan-out/fan-in, map-reduce, pipelines, scatter-gather), precise subagent briefing, context and…

  skills/knowledge/dispatching-parallel-agents/SKILL.md on GitHub (opens in a new tab)

• git-workflow

  Git workflow patterns and version control best practices for teams of any size. Use when the user asks to choose a branching strategy (trunk-based, GitHub Flow, Git Flow, GitLab Flow), define commit conventions, set up PR workflows, plan release management, structure a monorepo, or establish team git standards. Covers branch naming, merge vs rebase, conventional commits, semantic versioning, chan…

  skills/knowledge/git-workflow/SKILL.md on GitHub (opens in a new tab)

• microservices

  Microservices and distributed systems architecture patterns for scalable, resilient services. Use when the user asks to decompose a monolith, design service boundaries, implement saga orchestration, apply CQRS or event sourcing, configure circuit breakers, set up API gateways, handle eventual consistency, or evaluate monolith vs microservices trade-offs. Covers service decomposition strategies, i…

  skills/knowledge/microservices/SKILL.md on GitHub (opens in a new tab)

• performance

  Application performance optimization patterns and profiling-driven methodology. Use when the user asks to optimize application speed, reduce latency, diagnose slow queries, fix N+1 problems, implement caching layers, profile memory usage, tune database queries, apply lazy loading, configure connection pooling, or set performance budgets. Covers CPU and memory profiling, caching strategies (applic…

  skills/knowledge/performance/SKILL.md on GitHub (opens in a new tab)

• refactoring

  Comprehensive skill for 89 refactoring techniques and 22 code smells with practical examples. Use when the user asks to refactor code, detect code smells, improve code quality, reduce complexity, or clean up technical debt. Covers composing methods, moving features between objects, organizing data, simplifying conditionals and method calls, dealing with generalization, and detecting smells across…

  skills/knowledge/refactoring/SKILL.md on GitHub (opens in a new tab)

• scrum

  Scrum framework fundamentals, sprint goal writing, and agile ceremony facilitation. Use when the user asks to plan a sprint, write sprint goals, facilitate daily scrums, run sprint reviews or retrospectives, define scrum roles, manage the product backlog, or apply agile estimation techniques. Covers the three pillars (transparency, inspection, adaptation), scrum artifacts, goal-writing templates…

  skills/knowledge/scrum/SKILL.md on GitHub (opens in a new tab)

• security

  Application security principles and OWASP Top 10 for building secure web applications. Use when the user asks to review code for security vulnerabilities, implement authentication or authorization, handle secrets or API keys, configure security headers, prevent injection attacks (SQL, XSS, CSRF), prepare for a security audit, or respond to a vulnerability report. Covers input validation, data pro…

  skills/knowledge/security/SKILL.md on GitHub (opens in a new tab)

• solid

  SOLID principles for object-oriented design with multi-language examples (PHP, Java, Python, TypeScript, C++). Use when the user asks to review SOLID compliance, fix a SOLID violation, evaluate class design, reduce coupling, improve extensibility, or apply Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, or Dependency Inversion principles. Covers motivation, violati…

  skills/knowledge/solid/SKILL.md on GitHub (opens in a new tab)

• subagent-driven-development

  Execute a multi-task implementation plan by dispatching one fresh subagent per task with isolated context, then applying a two-stage review (spec compliance and code quality) before advancing. Use when you have a written plan with 3+ tasks, when tasks would otherwise cause context bleed, when you need reproducible per-task output, or when review gates are non-negotiable. Covers per-task briefing…

  skills/knowledge/subagent-driven-development/SKILL.md on GitHub (opens in a new tab)

• testing

  Stack-agnostic testing principles, strategies, and patterns for building reliable test suites. Use when the user asks to design a test strategy, choose between unit/integration/e2e tests, apply TDD, fix flaky tests, improve test quality, use test doubles (mocks, stubs, fakes, spies), or review tests for antipatterns. Covers the testing pyramid, test design heuristics, arrange-act-assert structure…

  skills/knowledge/testing/SKILL.md on GitHub (opens in a new tab)

• verification-before-completion

  Evidence-based completion discipline. Use before claiming any work is 'done', complete, finished, or ready — whether it is code, config, documentation, a migration, or a bugfix. Requires running verification commands (tests, lints, type checks, builds, smoke tests), capturing output, and citing concrete evidence rather than assertions. Covers tiered definitions of done, evidence patterns, verific…

  skills/knowledge/verification-before-completion/SKILL.md on GitHub (opens in a new tab)

• composer-dependencies

  Composer dependency management playbook for safe, systematic package updates. Use when the user asks to update Composer dependencies, audit packages for security vulnerabilities, manage composer.lock, configure Dependabot or Renovate for automated updates, replace abandoned packages, or resolve version conflicts. Covers patch/minor/major update strategies, composer audit, semantic versioning cons…

  skills/playbooks/composer-dependencies/SKILL.md on GitHub (opens in a new tab)

• finishing-branch

  End-to-end workflow for finishing a development branch. Use when implementation is complete and the branch is ready to ship - runs verification checks, reviews the diff, picks the integration path (direct merge, pull request, squash-and-merge, stacked PR), writes the PR/merge message, pushes to the remote, and cleans up branches and worktrees. Covers rebase vs merge vs squash decisions, pre-push…

  skills/playbooks/finishing-branch/SKILL.md on GitHub (opens in a new tab)

• php-upgrade

  Step-by-step PHP version upgrade playbook for PHP 8.0 through 8.4+ with automated tooling. Use when the user asks to upgrade PHP to a new version, check PHP compatibility, fix deprecation warnings, run Rector for automated refactoring, audit code with PHPCompatibility, or plan a PHP migration strategy. Covers breaking changes per version, php.ini configuration updates, extension compatibility, Re…

  skills/playbooks/php-upgrade/SKILL.md on GitHub (opens in a new tab)

• ticket-delivery

  End-to-end ticket workflow - from ticket analysis through investigation, planning, TDD implementation, committing, and PR creation. Adapts to your environment via a supplement file created on first run. Use when starting work on a ticket, implementing a feature end-to-end, or following a structured development workflow from ticket to PR.

  skills/playbooks/ticket-delivery/SKILL.md on GitHub (opens in a new tab)

• worktree-ops

  Manage git worktrees for isolated parallel development sessions. Create, list, switch between, and remove worktrees with safety checks for uncommitted changes and unpushed commits. Use when the user wants to work on multiple branches simultaneously, run parallel sessions, or isolate experimental changes.

  skills/playbooks/worktree-ops/SKILL.md on GitHub (opens in a new tab)

• architect

  Agent team role for system design and technical decision-making. Use when the user asks to design system architecture, define component boundaries, write Architecture Decision Records (ADRs), select technologies, define API contracts, or evaluate architectural trade-offs. Owns the "how" — translates product requirements into components, data flows, and technology choices.

  skills/roles/architect/SKILL.md on GitHub (opens in a new tab)

• backend-dev

  Agent team role for backend implementation and service reliability. Use when the user asks to implement API endpoints, design data models, write backend services, create database queries, build service integrations, or write backend tests. Owns production backend code — translates architectural designs and API contracts into working, tested implementations.

  skills/roles/backend-dev/SKILL.md on GitHub (opens in a new tab)

• frontend-dev

  Agent team role for UI implementation and frontend architecture. Use when the user asks to build UI components, implement responsive layouts, manage client-side state, integrate with backend APIs, ensure accessibility compliance, or write frontend tests. Owns the user-facing interface — translates design specs into working, accessible, performant components.

  skills/roles/frontend-dev/SKILL.md on GitHub (opens in a new tab)

• product-manager

  Agent team role for product ownership and requirements definition. Use when the user asks to write a PRD, gather requirements, define acceptance criteria, prioritize features, scope an MVP, write user stories, or make product trade-off decisions. Owns the "what" and "why" — translates business goals and user needs into clear, prioritized requirements for the engineering team.

  skills/roles/product-manager/SKILL.md on GitHub (opens in a new tab)

• project-manager

  Agent team role for project delivery management using PRINCE2 principles. Use when the user asks to plan project stages, manage risks, track progress, write highlight reports, handle exceptions, create work packages, or ensure continued business justification. Owns the "when" and "how much" — controls stages, timelines, resources, and escalates when tolerances are exceeded.

  skills/roles/project-manager/SKILL.md on GitHub (opens in a new tab)

• qa-engineer

  Agent team role for quality assurance and test management. Use when the user asks to create test plans, design test cases, perform exploratory testing, write bug reports, verify fixes, define test coverage requirements, or sign off on releases. Owns the quality gate — translates requirements and acceptance criteria into structured test strategies across the delivery pipeline.

  skills/roles/qa-engineer/SKILL.md on GitHub (opens in a new tab)

• scrum-master

  Agent team role for Scrum Master facilitation, coaching, and servant leadership. Use when the user asks to facilitate scrum events, coach a team on self-management, resolve impediments, run retrospectives, improve team processes, or address scrum anti-patterns. Owns the "how we work" - ensures the team applies scrum effectively, removes obstacles, and continuously improves.

  skills/roles/scrum-master/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• reaby morluto Reverse engineer anything with agents, from app behavior down to native binaries. 270k stars · 1 skill
• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 164k stars · 6 skills
• agent-skillsby addyosmani Production-grade engineering skills for AI coding agents. 107k stars · 25 skills
• taste-skillby Leonxlnx Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages 97.3k stars · 13 skills
• archifyby tt-a1i Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more. 84.1k stars · 2 skills
• awesome-claude-skillsby ComposioHQ A curated list of awesome Claude Skills, resources, and tools for customizing Claude AI workflows 77.2k stars