Agent Skills for Engineering

Reviews changes since a fixed point along Standards and Spec axes using parallel sub-agents, with a Fowler code-smell baseline.

by mattpocock/skills

• Requirements
• Implementation

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

by addyosmani/agent-skills

• Requirements
• Implementation

Breaks work into ordered, verifiable tasks with acceptance criteria, dependency graphs, vertical slicing, and checkpoints.

by addyosmani/agent-skills

• Requirements
• Implementation
• Quality & testing

Delivers changes incrementally in thin, verifiable slices. Use when implementing any feature or change that touches more than one file, or when picking up the next task from a plan. Use when rolling a change out behind a feature flag, when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

by addyosmani/agent-skills

• Requirements
• Implementation

Establishes a project's quality bar as a written CONSTRAINTS.md contract with thresholds and watches diffs for weakened checks like suppressions or skipped tests.

by addyosmani/agent-skills

• Requirements

Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

by addyosmani/agent-skills

• Requirements
• Implementation
• Architecture

>- Interactively discovers requirements and designs holistic, multi-product system architectures, solution blueprints, and deployment recommendations for complex workloads on Google Cloud. Use when designing end-to-end cloud solutions, selecting and integrating Google Cloud services, generating architecture diagrams, or conducting requirements discovery for new cloud workloads or migrations. Don't use for single-product tasks (use product-specific skills), initial onboarding or authentication (use google-cloud-recipe-*), Well-Architected Framework reviews or audits (use google-cloud-waf-*), or workloads covered by specialized solution skills.

by google/skills

• Requirements

>- Transform the agent into a Cloud Solution Architect following Azure Architecture Center best practices. Use when designing cloud architectures, reviewing system designs, selecting architecture styles, applying cloud design patterns, making technology choices, or conducting Well-Architected Framework reviews.

by microsoft/skills

• Requirements
• Maintenance & operations

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

by obra/superpowers

• Requirements
• Implementation

>- Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting deployment failures. Boundaries: - Only use for GCP-specific cloud infrastructure. - Only use for Terraform coding within the ADC context.

by google/skills

• Requirements
• Implementation
• Quality & testing

Optimizes application performance across frontend, backend, queries, and databases with a measure-identify-fix-verify-guard workflow and Core Web Vitals targets.

by addyosmani/agent-skills

• Requirements

Generates high-quality Product Requirements Documents with executive summaries, user stories, technical specifications, and risk analysis.

by github/awesome-copilot

• Requirements
• Implementation

Creates Dockerfiles, CI/CD pipelines, Kubernetes manifests, and Terraform/Pulumi templates, covering deployment automation, GitOps, and incident response.

by jeffallan/claude-skills

• Requirements
• Implementation
• Quality & testing

Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

by addyosmani/agent-skills

• Requirements
• Implementation

Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.

by microsoft/azure-skills

• Requirements

Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.

by openai/skills

• Requirements
• Implementation

React and Next.js performance optimization guidelines with 70 rules across 8 categories, prioritized by impact for writing, reviewing, and refactoring code.

by vercel-labs/agent-skills

Plans large multi-session work as a shared map of decision tickets on the issue tracker, resolving them one at a time until the route is clear.

by mattpocock/skills

• Requirements

Creates polished, validated architecture, workflow, sequence, data-flow, and lifecycle diagrams as standalone HTML with inline SVG and export options.

by tt-a1i/archify

• Requirements
• Architecture

Extracts what the user actually wants through one-question-at-a-time interviews with hypotheses and confidence numbers before any plan or code exists.

by addyosmani/agent-skills

• Requirements
• Quality & testing

Updates an existing implementation plan file with new or changed requirements, producing machine-readable, deterministic phases and tasks.

by github/awesome-copilot

• Requirements
• Implementation
• Maintenance & operations

Creates feature-level PRDs from an Epic, covering goals, personas, user stories, requirements, acceptance criteria, and out-of-scope items.

by github/awesome-copilot

• Requirements

Operating model for agentic engineering with eval-first execution, task decomposition, cost-aware model routing, and review focus for AI-generated code.

by affaan-m/ecc

• Implementation

Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.

by openai/skills

Needs (stated): Node.js

Provides structured incident response runbook templates with severity levels, triage, mitigation, escalation paths, and recovery procedures.

by wshobson/agents

• Quality & testing
• Maintenance & operations

Engineering operating model for teams where AI agents generate much of the implementation, covering process shifts, architecture requirements, and review focus.

by affaan-m/ecc

• Requirements
• Implementation

Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

by addyosmani/agent-skills

• Requirements
• Implementation

Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.

by openai/skills

• Implementation
• Quality & testing

Needs (stated): Node.js

> Review and create distinctive, production-grade frontend interfaces with high design quality and design system compliance. Evaluates using three pillars: frictionless insight-to-action, quality craft, and trustworthy building. USE FOR: PR reviews, design reviews, accessibility audits, design system compliance checks, creative frontend design, UI code review, component reviews, responsive design checks, theme testing, and creating memorable UI. DO NOT USE FOR: Backend API reviews, database schema reviews, infrastructure or DevOps work, pure business logic without UI, or non-frontend code.

by microsoft/skills

• Requirements
• Implementation
• Quality & testing

Linting best practices and golangci-lint configuration for Go projects, covering running linters, .golangci.yml, nolint directives, and interpreting output.

by samber/cc-skills-golang

• Implementation
• Quality & testing

Applies modern web development best practices for security, compatibility, and code quality based on Lighthouse best-practices audits.

by addyosmani/web-quality-skills

• Quality & testing

Performs comprehensive SQL code review across databases, focusing on injection prevention, access control, performance, and anti-pattern detection.

by github/awesome-copilot

• Quality & testing
• Maintenance & operations

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

by vercel-labs/agent-skills

PostgreSQL-specific code review covering JSONB, arrays, custom types, schema design, function optimization, and Row Level Security.

by github/awesome-copilot

Plan, create, and configure production-ready Azure Kubernetes Service (AKS) clusters. Covers Day-0 checklist, SKU selection (Automatic vs Standard), networking options (private API server, Azure CNI Overlay, egress configuration), security, and operations (autoscaling, upgrade strategy, cost analysis). WHEN: create AKS environment, provision AKS, enable AKS observability, design AKS networking, choose AKS SKU, secure AKS, optimize AKS, AKS spot nodes, AKS cluster-autoscaler, rightsize AKS pod, pod rightsizing, over-provisioned AKS pod, pod resource requests and limits, Vertical Pod Autoscaler, VPA recommendations.

by microsoft/azure-skills

• Requirements
• Maintenance & operations

Needs (stated): Node.js

Review a Penpot design against its implemented code (a source component or Storybook story) and emit a structured DRIFT report. Use when an engineer needs to confirm the build matches the design: extract HTML/CSS from a selection, map its tokens/structure/states to the code component, diff them, and list what each side is missing with severity and a reconciliation. Degrades gracefully to a design-system-token check when no code source is supplied. Triggers: 'design to code review', 'does my code match the design', 'design code parity', 'compare Penpot to my component', 'check this against Storybook', 'extract HTML/CSS from this selection', 'find design drift', 'design implementation diff'.

by penpot/penpot-ai-kit

• Implementation

Configures a repo for engineering skills by setting up its issue tracker, triage label vocabulary, and domain doc layout.

by mattpocock/skills

• Requirements
• Architecture

Reviews Archify issues, PRs, or code through value, cost, and impact to support evidence-based maintenance decisions.

by tt-a1i/archify

• Requirements
• Implementation
• Quality & testing

Audits agent configuration, instruction drift, hooks/MCP, and AI maintainability, producing a prioritized health report with evidence and actions.

by tw93/waza

• Implementation
• Quality & testing

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

by anthropics/skills

Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. WHEN: create architecture diagram, visualize Azure resources, show resource relationships, generate Mermaid diagram, analyze resource group, diagram my resources, architecture visualization, resource topology, map Azure infrastructure.

by microsoft/azure-skills

• Requirements

Search issues, merged pull requests, READMEs, and documentation. Use when the question is how a library or API behaves, what an error means, or whether a bug was fixed; prefer this over a general web page.

by firecrawl/skills

>- Guides agents to interactively discover customer requirements for live, bidirectional multi-agent AI systems that process continuous streams of multimodal data for real-time technical guidance and safety monitoring. Generates a custom Google Cloud solution that uses opinionated best practices and architecture guidance. Use when users need agentic assistance to design and create a multi-product solution in the cloud for live bidirectional multimodal streaming workloads. Don't use for simple text-based chat applications or workloads without real-time streaming requirements.

by google/skills

• Requirements
• Implementation

Browser automation CLI for AI agents, supporting navigation, form filling, screenshots, data extraction, and web app testing via CDP.

by vercel-labs/agent-browser

• Quality & testing

Covers network protocol reverse engineering with packet capture, protocol dissection, and custom protocol documentation using Wireshark, tshark, and Scapy.

by wshobson/agents

Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.

by openai/skills

• Implementation

Needs (stated): MCP server

>- Guides agents to discover requirements and design a governed, secure borderless open data lakehouse with agentic AI integration. Use when designing a multi-product architecture that connects data silos to AI agents, joining data across clouds, or running federated queries across Google Cloud and external data sources, including on-premises or other cloud providers. Don't use for simple single-cloud data warehouses or non-AI workloads.

by google/skills

• Requirements
• Implementation

Needs (stated): Credentials

Encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and invisible details that make software feel right.

by emilkowalski/skills

Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code'. This is the preferred workflow skill whenever the user wants to build or update a full page, screen, or view in Figma from code or a description. Discovers design system components, variables, and styles via search_design_system, imports them, and assembles screens incrementally section-by-section using design system tokens instead of hardcoded values.

by openai/skills

• Implementation

Extract a DESIGN.md design-documentation file from a Penpot file: a portable markdown spec (YAML frontmatter with colors/typography/rounded/spacing/components token maps + prose sections: Overview, Colors, Typography, Layout, Shapes, Components, Do's & Don'ts, Iteration Guide, Known Gaps) in the design-md format, grounded in the file's real tokens, library assets, and sampled component styles — never invented. Read-only on the canvas; writes one local markdown file. Triggers: 'generate DESIGN.md', 'create a design.md', 'document the design system as markdown', 'export design guidelines', 'extract design documentation', 'design system spec file', 'make a style guide file from this design'.

by penpot/penpot-ai-kit

• Requirements

Elite UX/UI and GSAP motion engineering guidance enforcing layout randomization, AIDA page structure, editorial typography, and bento grids.

by leonxlnx/taste-skill

Reviews animation and motion code against a high craft bar with ten non-negotiable standards covering easing, duration, origin, interruptibility, and accessibility.

by emilkowalski/skills

• Quality & testing

antfu-style design conventions, broadened. UnoCSS-first, class-based semantic tokens with dual light/dark for tooling and devtools UIs, plus design-read, anti-slop, and micro-interaction polish for landing pages and product surfaces. Use when building or refactoring any interface with UnoCSS.

by antfu/skills

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

by multica-ai/andrej-karpathy-skills

• Implementation
• Maintenance & operations

Persistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and emits aggregate counts only; --replay may emit bounded nonce-framed excerpts. Optional gated mode can request continuation only when the host supports it and never runs commands declared in Markdown. The skill has no network upload path. Use for research or work needing 5+ tool calls.

by OthmanAdi/planning-with-files

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

by DietrichGebert/ponytail

• Implementation

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

by obra/superpowers

• Implementation

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

by obra/superpowers