vercel
Vercel deployment platform documentation - use for deploying Next.js apps, serverless functions, edge middleware, and CI/CD workflows
Discover devops cicd skills, compare source repositories and read the instructions for each workflow.
Vercel deployment platform documentation - use for deploying Next.js apps, serverless functions, edge middleware, and CI/CD workflows
Execution workflow preferences including no dev servers, read-only information gathering, real data over mocks, and proper error handling over fallbacks. Use when executing code, running servers, testing, or ha...
Procedures and examples for writing and executing automated tests for software. Use this skill when verifying code correctness with unit, integration, or end-to-end tests.
Systematic checklist execution (CLI-based) (project)
Prepare releases with semantic versioning, changelog generation, git tags, GitHub releases, and deployment bundle creation.
Follow truth-first development with focused feature work, accurate spec maintenance, clean version control, environment-based configuration, and infrastructure-as-code deployments. Use this skill when managing...
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation...
Archives completed changes and merges specification deltas into living documentation. Use when changes are deployed, ready to archive, or specs need updating after implementation. Triggers include "archive chan...
Standard Operating Procedure for /preview phase. Covers manual UI/UX testing, user flow validation, and pre-deployment verification on local dev server.
Senior CAPA Officer specialist for managing Corrective and Preventive Actions within Quality Management Systems. Provides CAPA process management, root cause analysis, effectiveness verification, and continuous...
Required workflow for AEM EDS development - linting, testing, preview validation, and PRs with demo links. Use when developing blocks or features for AEM Edge Delivery Services projects, before doing anything e...
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
Practice radical candor by delivering only verified, tested code with data-backed decisions, immediate problem flagging, and honest status communication. Use this skill when making claims about code behavior, r...
Vercel deployment workflow for CA Lobby React app with Clerk auth and BigQuery backend. Use when deploying CA Lobby, troubleshooting Vercel, or user says "deploy". Ensures proper configuration and verification.
Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates
Guide for creating releases following GitFlow, version bumping, changelog updates, and CI/CD pipeline
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches superpowers:code-reviewer subagent to review implementation against plan or requirements...
Enforces policy rules for skill and agent manifests
Debug and troubleshoot GitHub Actions CI/CD workflows for the SOMA project
Two-phase workflow for technical specifications - WRITING phase creates and commits specs then stops; IMPLEMENTATION phase follows specs, updates status, and commits all changes. Different agents handle each ph...
Standard Operating Procedure for /optimize phase. Covers performance benchmarking, accessibility audit, security review, and code quality checks.
Will utilise buildkite read only mcp server to solve specific buildkite issues encountered
Permanent vs temporary test organization and immutable contract philosophy. Use when creating, modifying, or reviewing tests.
Run comprehensive project health checks including code quality, documentation, git status, and project structure
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.