
Secret Scanner — Detects and prevents hardcoded secrets in code, configuration, and documentation. Enforces security best practices and integrates with CI/CD pipelines for proactive secret management.
Guidelines and protocols for mobile engineers to execute tasks effectively while adhering to the core mandate of not modifying backend systems, infrastructure, or deployment processes.
Guidelines and protocols for frontend engineers to execute tasks effectively while adhering to the core mandate of not modifying backend systems or infrastructure.
Feature Document Template — Structured template for documenting feature requirements and design upfront, serving as the source of truth for planning and implementation.
Guidelines and protocols for DevOps engineers to execute tasks effectively while adhering to the core mandate of not modifying frontend or backend systems, but focusing on infrastructure, CI/CD, and deployment processes.
Guidelines and protocols for Debuggers to execute tasks effectively while adhering to the core mandate of not modifying frontend or backend systems, infrastructure, or deployment processes.
Guidelines and protocols for backend engineers to execute tasks effectively while adhering to the core mandate of not modifying frontend systems or user-facing components.
Comprehensive web accessibility standards based on WCAG 2.2 AA, with anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Language-agnostic security scanner covering dependencies (SCA), code patterns (SAST), and application-layer vulnerabilities (XSS, CSRF, SQLi, Prompt Injection, etc.), with concrete vulnerable and secure code examples.
AAA (Arrange-Act-Assert) — Enforces the Arrange-Act-Assert pattern for writing clear, structured, and maintainable tests. Use when writing, reviewing, or refactoring any unit or integration tests that are hard to read, mix setup with assertions, have unclear intent, or lack a consistent structure. Applies to any language and any testing framework (Jest, PyTest, JUnit, RSpec, Go testing, etc.).
Guidelines and protocols for AI engineers to execute tasks effectively while adhering to the core mandate of not modifying frontend or backend systems, infrastructure, or deployment processes.
Standardized skill to request missing or ambiguous input from the user using native tools when available.
Atomic Design Pattern — Enforces the Atomic Design methodology for UI components: Atoms, Molecules, Organisms, Templates, and Pages.
Guidelines and protocols for backend engineers to execute tasks effectively while adhering to the core mandate of not modifying frontend systems or user-facing components.
Bug-Fix Plan Template — Structured plan template for debugging and fixing bugs, focused on diagnosis, impact analysis, and task breakdown without requiring a feature doc.
Guidelines and protocols for codebase analyst agents to execute their analysis effectively while adhering to the core mandate of not modifying frontend or backend systems, infrastructure, or deployment processes.
Guidelines and protocols for DevOps engineers to execute tasks effectively while adhering to the core mandate of not modifying frontend or backend systems, but focusing on infrastructure, CI/CD, and deployment processes.
Scans a Node.js project (JavaScript or TypeScript) to build a compact knowledge graph of file dependencies and exported symbols, storing it in the project's agent folder (.claude, .github, or .cursor) for use by GitHub Copilot, Claude Code, or any AI agent.
Feature Document Template — Structured template for documenting feature requirements and design upfront, serving as the source of truth for planning and implementation.
KISS (Keep It Simple, Stupid) — Enforces the KISS principle by favoring simple, readable, and obvious solutions over clever or over-engineered ones. Use when writing, reviewing, or refactoring code that is unnecessarily complex, over-abstracted, or hard to understand at a glance.
Guidelines and protocols for QA engineers to execute tasks effectively while adhering to the core mandate of not modifying frontend or backend systems, infrastructure, or deployment processes.
Guidelines and protocols for desktop app developers to execute tasks effectively while adhering to the core mandate of handling both frontend and backend aspects of desktop applications without modifying unrelated systems or infrastructure.
DRY (Don't Repeat Yourself) — Enforces the DRY principle by eliminating code duplication through abstraction, shared utilities, and single sources of truth. Use when writing, reviewing, or refactoring code that contains repeated logic, duplicated constants, copy-pasted blocks, or redundant data definitions in any language.
Guidelines and protocols for mobile engineers to execute tasks effectively while adhering to the core mandate of not modifying backend systems, infrastructure, or deployment processes.
Guidelines and protocols for Debuggers to execute tasks effectively while adhering to the core mandate of not modifying frontend or backend systems, infrastructure, or deployment processes.
Guidelines and protocols for frontend engineers to execute tasks effectively while adhering to the core mandate of not modifying backend systems or infrastructure.
Universal SQL performance optimization assistant for comprehensive query tuning, indexing strategies, and database performance analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Provides execution plan analysis, pagination optimization, batch operations, and performance monitoring guidance.
Secret Scanner — Detects and prevents hardcoded secrets in code, configuration, and documentation. Enforces security best practices and integrates with CI/CD pipelines for proactive secret management.
Separation of Concerns (SoC) — Enforces the Separation of Concerns principle by ensuring each module, layer, and component addresses exactly one well-defined concern. Use when writing, reviewing, or refactoring code that mixes UI with business logic, business logic with data access, presentation with formatting, or cross-cutting concerns (auth, logging, validation) with core logic.
SOLID — Enforces the SOLID principle of object-oriented design (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) for maintainable and scalable code.
Guidelines and protocols for Technical Leaders to manage and oversee technical projects effectively while adhering to the core mandate of being the central orchestration layer for all engineering work.
Code Reviewer — Protocols and standards for performing thorough, structured code reviews. Covers the reviewer's core mandate, step-by-step review protocol, and all review lenses: security (secret scanning), code quality (SOLID, DRY, KISS), architecture (Separation of Concerns, Atomic Design), and testing (AAA pattern). Use when reviewing pull requests, merge requests, or any code changes across any language or framework.
Atomic Design Pattern — Enforces the Atomic Design methodology for UI components: Atoms, Molecules, Organisms, Templates, and Pages.
DRY (Don't Repeat Yourself) — Enforces the DRY principle by eliminating code duplication through abstraction, shared utilities, and single sources of truth. Use when writing, reviewing, or refactoring code that contains repeated logic, duplicated constants, copy-pasted blocks, or redundant data definitions in any language.
Standardized skill to request missing or ambiguous input from the user using native tools when available.
Scans a Node.js project (JavaScript or TypeScript) to build a compact knowledge graph of file dependencies and exported symbols, storing it in the project's agent folder (.claude, .github, or .cursor) for use by GitHub Copilot, Claude Code, or any AI agent.
Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.
AAA (Arrange-Act-Assert) — Enforces the Arrange-Act-Assert pattern for writing clear, structured, and maintainable tests. Use when writing, reviewing, or refactoring any unit or integration tests that are hard to read, mix setup with assertions, have unclear intent, or lack a consistent structure. Applies to any language and any testing framework (Jest, PyTest, JUnit, RSpec, Go testing, etc.).
Comprehensive web accessibility standards based on WCAG 2.2 AA, with anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Guidelines and protocols for AI engineers to execute tasks effectively while adhering to the core mandate of not modifying frontend or backend systems, infrastructure, or deployment processes.
Bug-Fix Plan Template — Structured plan template for debugging and fixing bugs, focused on diagnosis, impact analysis, and task breakdown without requiring a feature doc.
Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.
Guidelines and protocols for codebase analyst agents to execute their analysis effectively while adhering to the core mandate of not modifying frontend or backend systems, infrastructure, or deployment processes.
Code Reviewer — Protocols and standards for performing thorough, structured code reviews. Covers the reviewer's core mandate, step-by-step review protocol, and all review lenses: security (secret scanning), code quality (SOLID, DRY, KISS), architecture (Separation of Concerns, Atomic Design), and testing (AAA pattern). Use when reviewing pull requests, merge requests, or any code changes across any language or framework.
Guidelines and protocols for desktop app developers to execute tasks effectively while adhering to the core mandate of handling both frontend and backend aspects of desktop applications without modifying unrelated systems or infrastructure.
Find an skill from awesome-copilot repository that matches a specific need or workflow.
Guidelines and protocols for QA engineers to execute tasks effectively while adhering to the core mandate of not modifying frontend or backend systems, infrastructure, or deployment processes.
KISS (Keep It Simple, Stupid) — Enforces the KISS principle by favoring simple, readable, and obvious solutions over clever or over-engineered ones. Use when writing, reviewing, or refactoring code that is unnecessarily complex, over-abstracted, or hard to understand at a glance.
Separation of Concerns (SoC) — Enforces the Separation of Concerns principle by ensuring each module, layer, and component addresses exactly one well-defined concern. Use when writing, reviewing, or refactoring code that mixes UI with business logic, business logic with data access, presentation with formatting, or cross-cutting concerns (auth, logging, validation) with core logic.
SOLID — Enforces the SOLID principle of object-oriented design (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) for maintainable and scalable code.
Universal SQL performance optimization assistant for comprehensive query tuning, indexing strategies, and database performance analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Provides execution plan analysis, pagination optimization, batch operations, and performance monitoring guidance.
Guidelines and protocols for Technical Leaders to manage and oversee technical projects effectively while adhering to the core mandate of being the central orchestration layer for all engineering work.