sethdford/claude-skills - 2페이지

deployment-topology

Plan container orchestration, load balancing, high availability, and scaling. Design deployment topologies for production systems. Use when architecting deployment infrastructure or modernizing deployment practices.

원문 언어: 영어

disaster-recovery-plan

Define recovery objectives (RTO/RPO), backup strategies, failover procedures, and testing protocols. Use when planning disaster recovery or establishing continuity practices.

원문 언어: 영어

infrastructure-as-code-patterns

Codify infrastructure with Terraform, CloudFormation, or Pulumi. Design IaC architecture, versioning, testing, and drift detection. Use when automating infrastructure or establishing IaC practices.

원문 언어: 영어

multi-region-design

Distribute globally across multiple regions for low latency, compliance, and resilience. Plan data replication, failover, and latency optimization. Use when designing global systems.

원문 언어: 영어

network-topology

Design VPCs, subnets, security groups, load balancing, and DNS architecture. Plan for segmentation, DDoS protection, and failover. Use when architecting network infrastructure.

원문 언어: 영어

cost-optimization

Optimize infrastructure and operational costs without sacrificing performance or reliability. Use when managing cloud budgets or improving unit economics.

원문 언어: 영어

maintainability-assessment

Assess and design for maintainability. Evaluate code complexity, coupling, and testability. Use when evaluating codebase health or designing for long-term evolution.

원문 언어: 영어

observability-design

Design observability (metrics, logs, traces) for understanding system behavior in production. Use when debugging distributed systems or building monitoring.

원문 언어: 영어

performance-modeling

Model system performance, predict latency under load, identify bottlenecks. Use when optimizing performance or capacity planning.

원문 언어: 영어

reliability-design

Design systems that fail gracefully and recover automatically. Use when defining SLAs, designing for fault tolerance, or improving uptime.

원문 언어: 영어

scalability-analysis

Analyze and predict system scalability. Model growth, identify bottlenecks, project infrastructure costs. Use when planning for growth or investigating performance limits.

원문 언어: 영어

security-architecture

Design security architecture covering authentication, authorization, data protection, and threat models. Use when building security-critical systems.

원문 언어: 영어

trade-off-analysis

Analyze architectural trade-offs systematically using decision matrices. Use when comparing design options or justifying architectural choices to stakeholders.

원문 언어: 영어

api-gateway-design

Design API gateways that route, authenticate, rate-limit, and aggregate backend services. Use when building client-facing APIs or managing service boundaries.

원문 언어: 영어

caching-strategy

Design multi-layer caching strategies (client, edge, service, database) for performance. Use when optimizing latency or reducing database load.

원문 언어: 영어

cqrs-design

Separate command (write) and query (read) models for complex domains. Use when read/write patterns diverge significantly or when audit/consistency requirements demand immutability.

원문 언어: 영어

data-partitioning

Design partitioning and sharding strategies for data at scale. Use when single database hits throughput or storage limits.

원문 언어: 영어

domain-driven-design

Apply DDD principles to model business domains, design aggregates, and establish clear language across teams. Use when modeling complex business logic or integrating domain experts.

원문 언어: 영어

event-driven-architecture

Design systems that communicate through events instead of direct service calls. Use when building loosely-coupled, scalable, and resilient architectures.

원문 언어: 영어

microservices-patterns

Apply proven microservices patterns including saga, circuit breaker, bulkhead, and eventual consistency. Use when designing service-to-service communication and handling distributed failures.

원문 언어: 영어

monolith-assessment

Evaluate whether to keep, refactor, or break apart a monolithic system. Use when facing scaling or team velocity challenges with monoliths.

원문 언어: 영어

service-mesh-patterns

Implement service mesh patterns for observability, resilience, and traffic management. Use when managing complex microservices communication at scale.

원문 언어: 영어

system-decomposition

Break complex systems into bounded contexts with DDD. Map business capabilities to service boundaries, define ubiquitous language, assess cohesion/coupling. Use when refactoring monoliths or designing new architectures.

원문 언어: 영어

api-documentation

OpenAPI/Swagger, schema-driven documentation, examples, and interactive API docs.

원문 언어: 영어

api-error-handling

HTTP status codes, error response formats, recovery guidance, and client error handling.

원문 언어: 영어

api-testing-strategy

Contract testing, API mocking, integration testing, and end-to-end API testing.

원문 언어: 영어

api-versioning-strategy

Backward compatibility, deprecation policies, versioning schemes (URL, header, media type).

원문 언어: 영어

graphql-schema-design

GraphQL type systems, queries, mutations, subscriptions, and schema design patterns.

원문 언어: 영어

grpc-service-design

Protocol buffers, service definitions, streaming RPC, and performance-oriented API design.

원문 언어: 영어

rate-limiting-design

Rate limiting strategies (token bucket, sliding window, quota), DOS protection, and fair usage.

원문 언어: 영어

rest-api-design

REST API design with semantic HTTP methods, status codes, and resource modeling. Use when designing new APIs or reviewing existing API designs.

원문 언어: 영어

clean-code-review

Systematic code review checklist for readability, maintainability, and correctness. Use when reviewing pull requests or assessing existing code.

원문 언어: 영어

code-complexity-analysis

Measuring and reducing cyclomatic complexity and cognitive complexity to improve maintainability.

원문 언어: 영어

code-smell-detector

Identify code smells like long methods, duplication, low cohesion, and high coupling. Use when assessing code health.

원문 언어: 영어

dependency-injection

Designing loosely coupled code through dependency injection, reducing testability barriers and hidden dependencies.

원문 언어: 영어

error-handling-patterns

Strategies for handling errors: exceptions, error types, recovery strategies, and error propagation.

원문 언어: 영어

function-design

Designing pure functions with single purpose, minimal parameters, clear side effects, and high cohesion.

원문 언어: 영어

interface-design

Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.

원문 언어: 영어

naming-conventions

Choosing meaningful, pronounceable names that reveal intent for functions, variables, classes, and modules.

원문 언어: 영어

refactoring-catalog

Proven refactoring patterns (Extract Method, Replace Temp, Introduce Parameter Object) to improve code structure safely. Use when improving existing code while keeping behavior unchanged.

원문 언어: 영어