メニュー
このリポジトリの skills
SkillsMP は sethdford/claude-skills から 383 件の skill を収集しています。skill を開くとソースと詳細を確認できます。
sethdford/claude-skills収集済み skill 383 件中 40 件を表示しています。
Plan container orchestration, load balancing, high availability, and scaling. Design deployment topologies for production systems. Use when architecting deployment infrastructure or modernizing deployment practices.
原文の言語: 英語
Define recovery objectives (RTO/RPO), backup strategies, failover procedures, and testing protocols. Use when planning disaster recovery or establishing continuity practices.
原文の言語: 英語
Codify infrastructure with Terraform, CloudFormation, or Pulumi. Design IaC architecture, versioning, testing, and drift detection. Use when automating infrastructure or establishing IaC practices.
原文の言語: 英語
Distribute globally across multiple regions for low latency, compliance, and resilience. Plan data replication, failover, and latency optimization. Use when designing global systems.
原文の言語: 英語
Design VPCs, subnets, security groups, load balancing, and DNS architecture. Plan for segmentation, DDoS protection, and failover. Use when architecting network infrastructure.
原文の言語: 英語
Optimize infrastructure and operational costs without sacrificing performance or reliability. Use when managing cloud budgets or improving unit economics.
原文の言語: 英語
Assess and design for maintainability. Evaluate code complexity, coupling, and testability. Use when evaluating codebase health or designing for long-term evolution.
原文の言語: 英語
Design observability (metrics, logs, traces) for understanding system behavior in production. Use when debugging distributed systems or building monitoring.
原文の言語: 英語
Model system performance, predict latency under load, identify bottlenecks. Use when optimizing performance or capacity planning.
原文の言語: 英語
Design systems that fail gracefully and recover automatically. Use when defining SLAs, designing for fault tolerance, or improving uptime.
原文の言語: 英語
Analyze and predict system scalability. Model growth, identify bottlenecks, project infrastructure costs. Use when planning for growth or investigating performance limits.
原文の言語: 英語
Design security architecture covering authentication, authorization, data protection, and threat models. Use when building security-critical systems.
原文の言語: 英語
Analyze architectural trade-offs systematically using decision matrices. Use when comparing design options or justifying architectural choices to stakeholders.
原文の言語: 英語
Design API gateways that route, authenticate, rate-limit, and aggregate backend services. Use when building client-facing APIs or managing service boundaries.
原文の言語: 英語
Design multi-layer caching strategies (client, edge, service, database) for performance. Use when optimizing latency or reducing database load.
原文の言語: 英語
Separate command (write) and query (read) models for complex domains. Use when read/write patterns diverge significantly or when audit/consistency requirements demand immutability.
原文の言語: 英語
Design partitioning and sharding strategies for data at scale. Use when single database hits throughput or storage limits.
原文の言語: 英語
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.
原文の言語: 英語
Design systems that communicate through events instead of direct service calls. Use when building loosely-coupled, scalable, and resilient architectures.
原文の言語: 英語
Apply proven microservices patterns including saga, circuit breaker, bulkhead, and eventual consistency. Use when designing service-to-service communication and handling distributed failures.
原文の言語: 英語
Evaluate whether to keep, refactor, or break apart a monolithic system. Use when facing scaling or team velocity challenges with monoliths.
原文の言語: 英語
Implement service mesh patterns for observability, resilience, and traffic management. Use when managing complex microservices communication at scale.
原文の言語: 英語
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.
原文の言語: 英語
OpenAPI/Swagger, schema-driven documentation, examples, and interactive API docs.
原文の言語: 英語
HTTP status codes, error response formats, recovery guidance, and client error handling.
原文の言語: 英語
Contract testing, API mocking, integration testing, and end-to-end API testing.
原文の言語: 英語
Backward compatibility, deprecation policies, versioning schemes (URL, header, media type).
原文の言語: 英語
GraphQL type systems, queries, mutations, subscriptions, and schema design patterns.
原文の言語: 英語
Protocol buffers, service definitions, streaming RPC, and performance-oriented API design.
原文の言語: 英語
Rate limiting strategies (token bucket, sliding window, quota), DOS protection, and fair usage.
原文の言語: 英語
REST API design with semantic HTTP methods, status codes, and resource modeling. Use when designing new APIs or reviewing existing API designs.
原文の言語: 英語
Systematic code review checklist for readability, maintainability, and correctness. Use when reviewing pull requests or assessing existing code.
原文の言語: 英語
Measuring and reducing cyclomatic complexity and cognitive complexity to improve maintainability.
原文の言語: 英語
Identify code smells like long methods, duplication, low cohesion, and high coupling. Use when assessing code health.
原文の言語: 英語
Designing loosely coupled code through dependency injection, reducing testability barriers and hidden dependencies.
原文の言語: 英語
Strategies for handling errors: exceptions, error types, recovery strategies, and error propagation.
原文の言語: 英語
Designing pure functions with single purpose, minimal parameters, clear side effects, and high cohesion.
原文の言語: 英語
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
原文の言語: 英語
Choosing meaningful, pronounceable names that reveal intent for functions, variables, classes, and modules.
原文の言語: 英語
Proven refactoring patterns (Extract Method, Replace Temp, Introduce Parameter Object) to improve code structure safely. Use when improving existing code while keeping behavior unchanged.
原文の言語: 英語