ears-authoring
EARS requirement pattern authoring. Use when writing requirements using EARS patterns (Ubiquitous, State-Driven, Event-Driven, Unwanted, Optional, Complex). Provides pattern templates, validation, and examples.
gherkin-author
Interactive Gherkin scenario authoring. Guides through Given/When/Then construction with BDD best practices.
gherkin-authoring
Gherkin acceptance criteria authoring. Use when writing Given/When/Then scenarios, feature files, or BDD-style specifications. Provides syntax reference, best practices, and Reqnroll integration guidance.
gherkin-convert
Convert specifications to/from Gherkin/BDD format.
implement
Guide implementation of specification tasks. Phase 4 of Spec Kit workflow.
kiro-integration
AWS Kiro specification patterns and synchronization. Use when working with Kiro IDE, syncing requirements.md/design.md/tasks.md files, or configuring steering files for AI agent context.
kiro-sync
Synchronize specifications with AWS Kiro format (requirements.md, design.md, tasks.md).
openapi-authoring
Author and validate OpenAPI 3.1 specifications for REST API design, following API-first and contract-first development practices
plan
Generate an implementation plan from a specification. Phase 2 of Spec Kit workflow.
refine
Refine specification with AI-assisted improvements.
requirements-quality
Requirements quality assessment and improvement. Use when evaluating requirements against INVEST criteria, improving clarity, detecting ambiguity, or ensuring completeness. Provides quality checklists, refinement patterns, and MoSCoW prioritization guidance.
spec-management
Central authority for specification-driven development. Use when working with requirements, specifications, acceptance criteria, or any spec-driven workflow. Provides navigation to specialized skills and delegates to docs-management for official documentation.
speckit-run
Execute the complete GitHub Spec Kit 5-phase workflow from constitution to implementation.
speckit-workflow
GitHub Spec Kit 5-phase workflow. Use when following the Constitution → Specify → Plan → Tasks → Implement cycle. Provides phase guidance, file templates, and workflow orchestration.
status
Display specification status dashboard showing workflow progress, quality scores, and pending items.
userstory-author
Author Agile-style user stories with linked acceptance criteria.
validate
Validate specification against schema and quality rules.
api-design-fundamentals
Use when designing APIs, choosing between REST/GraphQL/gRPC, or understanding API design best practices. Covers protocol selection, resource modeling, and API patterns.
api-review
Review API design for best practices, consistency, and common issues
api-versioning
Use when planning API versioning strategy, handling breaking changes, or managing API deprecation. Covers URL, header, and query parameter versioning approaches.
cdn-architecture
Use when designing content delivery networks, caching strategies, or global content distribution. Covers CDN architecture, cache hierarchies, origin shielding, cache invalidation, and edge optimization.
chaos-engineering-fundamentals
Use when implementing chaos engineering, designing fault injection experiments, or building resilience testing practices. Covers chaos principles and experiment design.
chaos-plan
Design chaos engineering experiments for a system - identifies failure modes, creates experiment hypotheses, and generates GameDay plans
data-architecture
Use when designing data platforms, choosing between data lakes/lakehouses/warehouses, or implementing data mesh patterns. Covers modern data architecture approaches.
data-flow
Design data pipeline architecture for a given data flow scenario
design-interview-methodology
4-step framework for system design interviews. Use when preparing for technical interviews, practicing whiteboard design, or structuring architectural discussions. Covers requirements gathering, high-level design, deep dives, and wrap-up.
distributed-tracing
Use when implementing distributed tracing, understanding trace propagation, or debugging cross-service issues. Covers OpenTelemetry, span context, and trace correlation.
edge-computing
Use when designing edge computing architectures, serverless at edge, or distributed compute strategies. Covers edge functions, compute placement decisions, Cloudflare Workers, Lambda@Edge, and edge-native patterns.
edge-strategy
Design CDN and edge deployment strategy for global distribution - optimizes latency, plans caching architecture, and recommends edge compute placement
estimation-techniques
Back-of-envelope calculations for system design. Use when estimating QPS, storage, bandwidth, or latency for capacity planning. Includes latency numbers every programmer should know and common estimation patterns.
etl-elt-patterns
Use when designing data pipelines, choosing between ETL and ELT approaches, or implementing data transformation patterns. Covers modern data pipeline architecture.
explain
Explain a systems design concept
gameday-planning
Use when planning GameDay exercises, designing failure scenarios, or conducting chaos drills. Covers GameDay preparation, execution, and follow-up.
golden-paths
Use when designing standardized development workflows, paved roads, or opinionated defaults. Covers golden path patterns, template design, developer workflow optimization, and guardrails.
idempotency-patterns
Use when designing idempotent APIs, handling retries safely, or preventing duplicate operations. Covers idempotency keys, at-most-once semantics, and duplicate prevention.
improve-expertise
Run self-improve on an expert's mental model to sync with codebase. Use periodically to keep expertise files accurate.
incident-response
Use when designing incident management processes, creating runbooks, or establishing on-call practices. Covers incident lifecycle, communication, and postmortems.
instrumentation-planning
Plan instrumentation strategy before implementation, covering what to instrument, naming conventions, cardinality management, and instrumentation budget
internal-developer-platform
Use when designing Internal Developer Platforms (IDPs), building platform teams, or improving developer experience. Covers platform engineering principles, Backstage, portal design, and platform team structures.
latency-budget
Calculate and allocate latency budgets for a system - breaks down end-to-end latency into component budgets with optimization recommendations
latency-optimization
Use when optimizing end-to-end latency, reducing response times, or improving performance for latency-sensitive applications. Covers latency budgets, geographic routing, protocol optimization, and latency measurement techniques.
llm-serving-patterns
LLM inference infrastructure, serving frameworks (vLLM, TGI, TensorRT-LLM), quantization techniques, batching strategies, and streaming response patterns. Use when designing LLM serving infrastructure, optimizing inference latency, or scaling LLM deployments.
ml-inference-optimization
ML inference latency optimization, model compression, distillation, caching strategies, and edge deployment patterns. Use when optimizing inference performance, reducing model size, or deploying ML at the edge.
ml-pipeline
Design an ML system for a problem
ml-system-design
End-to-end ML system design for production. Use when designing ML pipelines, feature stores, model training infrastructure, or serving systems. Covers the complete lifecycle from data ingestion to model deployment and monitoring.
mock-interview
Run an interactive system design mock interview - simulates a real interview with problem statement, follow-ups, and structured feedback
mtls-service-mesh
Use when implementing service-to-service security, mTLS, or service mesh patterns. Covers mutual TLS, Istio, Linkerd, certificate management, and service mesh security configurations.
multi-region-deployment
Use when designing globally distributed systems, multi-region architectures, or disaster recovery strategies. Covers region selection, active-active vs active-passive, data replication, and failover patterns.
observability-patterns
Use when implementing observability strategy, correlating signals, or designing monitoring systems. Covers the three pillars (logs, metrics, traces) and their integration.
optimize-llm
Get LLM optimization recommendations for serving latency, inference costs, and throughput improvements
Page 7 of 10 · 484 results