Code quality assurance strategies. Parent skill for quality-related skills: security (security review) and debug (systematic debugging).
Cross-validate code, architecture or design decisions using a second model. Use for critical decisions, complex refactoring, security reviews.
Guide for building, configuring, and deploying microfrontends on Vercel. Use this skill when the user mentions microfrontends, multi-zones, splitting an app across teams, independent deployments, cross-app routing, incremental migration, composing multiple frontends under one domain, microfrontends.json, @vercel/microfrontends, the microfrontends local proxy, or path-based routing between Vercel projects. Also use when the user asks about shared layouts across projects, navigation between microfrontends, fallback environments, asset prefixes, or feature flag controlled routing.
RESTful API design patterns and best practices. Use when creating endpoints, designing APIs, or implementing routes.
```
Code exploration strategies for understanding unfamiliar codebases. Use when exploring unknown code, debugging, or analyzing architecture.
Architecture design skill: ADR records, system design checklists, scalability assessment, architecture patterns. Use for complex system design and architecture decisions.
Backend development patterns for services, error handling, logging, caching. Use when building backend services, APIs, or microservices.
Testing strategies and methodologies including TDD and E2E testing. Use when writing tests, implementing TDD workflow, or setting up E2E test infrastructure.
Session lifecycle management. Parent skill for session-related skills: learning (pattern extraction) and compact (context compression).
DevOps patterns: containerization, CI/CD, deployment strategies, monitoring. Use when containerizing apps, setting up pipelines, or deploying services.
Database design, query optimization, migrations, and indexing. Use when designing schemas, writing queries, or managing migrations.
Strategic compaction skill: suggests context compression at logical breakpoints. Use to suggest compaction at logical intervals during development sessions.
Git version control best practices: branching, commits, merging, conflict resolution, PR workflows. Use when managing branches, creating commits, merging code, or resolving conflicts.
Systematic debugging methods, log analysis, and performance diagnostics. Use when debugging issues, analyzing errors, or troubleshooting incidents.
Frontend patterns: component design, state management, performance, accessibility. Use when building web frontends, components, or client-side apps.
Extracts reusable patterns from sessions. Use at session end to capture debugging insights and project-specific knowledge.
End-to-end Solana development playbook (Jan 2026). Prefer Solana Foundation framework-kit (@solana/client + @solana/react-hooks) for React/Next.js UI. Prefer @solana/kit for all new client/RPC/transaction code. When legacy dependencies require web3.js, isolate it behind @solana/web3-compat (or @solana/web3.js as a true legacy fallback). Covers wallet-standard-first connection (incl. ConnectorKit), Anchor/Pinocchio programs, Codama-based client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists.
**Version**: 0.1.0-preview | **Last Updated**: 2025-11-15 | **Framework Version**: 0.1.0-preview
Run Microsoft's eval-recipes benchmarks to validate amplihack improvements against baseline agents.