principles
Core software design principles from 'A Philosophy of Software Design'. Use when asking about decomposition, deep modules, information hiding, complexity management, or John Ousterhout's design principles.
Discover databases architecture patterns skills, compare source repositories and read the instructions for each workflow.
Core software design principles from 'A Philosophy of Software Design'. Use when asking about decomposition, deep modules, information hiding, complexity management, or John Ousterhout's design principles.
Reviews API designs for simplicity and error handling. Use when designing APIs, evaluating interface complexity, or eliminating error conditions.
Reviews modules for depth vs shallowness. Use when designing APIs, reviewing class interfaces, or evaluating abstraction value.
This skill should be used when the user asks to "write specifications", "specify an abstraction", "create contract tests", "property-based testing", "design by contract", "specification tests", or discusses how...
Use when calling APEX MCP tools (apex_patterns_lookup, apex_patterns_overview, apex_task_create, apex_reflect, etc.) for pattern intelligence, task tracking, or submitting reflections. Reference guide for all 1...
Common architectural patterns and design best practices. Use when designing system architecture, choosing design patterns, or creating technical designs.
ADR management and decision logging. Use when documenting architectural decisions, tracking technical choices, or creating decision records.
Templates and patterns for requirements documents. Use when creating specifications, validating spec structure, or managing requirements documentation.
OpenAPI diff tools, schema comparison, and migration guide templates for detecting breaking changes in APIs, databases, and contracts. Use when analyzing API changes, comparing OpenAPI specs, detecting breaking...
Error rate monitoring, SLO detection, and notification webhooks for automated rollback triggers. Use when setting up automated deployment rollback, monitoring error rates, configuring SLO thresholds, implementi...
Architecture design templates, mermaid diagrams, documentation patterns, and validation tools. Use when designing system architecture, creating architecture documentation, generating mermaid diagrams, documenti...
Breaks down specs into complexity-stratified tasks. Use when organizing tasks, assigning work to agents, or when user mentions task layering, task stratification, or parallel task execution.
REST/GraphQL/tRPC API pattern library with validation, error handling, and documentation. Use when creating backend APIs.
Documentation synchronization using Mem0 for tracking relationships between specs, architecture, ADRs, and roadmap
Expert customer success covering onboarding, adoption, retention, expansion, health scoring, and customer advocacy.
Expert DevOps engineering covering CI/CD pipelines, infrastructure as code, container orchestration, cloud platforms, and site reliability.
Expert cloud architecture covering AWS, GCP, Azure, multi-cloud strategy, cost optimization, and cloud-native design.
Expert analytics engineering covering data modeling, dbt development, data transformation, and semantic layer management.
Expert product design covering UI/UX design, design systems, prototyping, user research, and design thinking.
Expert delivery management covering continuous delivery, release management, deployment coordination, and service operations.
Expert full-stack development covering frontend frameworks, backend services, databases, APIs, and deployment for modern web applications.
Expert software architecture covering system design, distributed systems, microservices, scalability patterns, and technical decision-making.
Expert backend development covering API design, database architecture, microservices, message queues, caching, and system scalability.
Expert solutions architecture covering technical requirements, solution design, integration planning, and enterprise architecture alignment.
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.