SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) for object-oriented design.
원문 언어: 영어
메뉴
이 저장소의 skills
SkillsMP는 sethdford/claude-skills에서 383개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
sethdford/claude-skills수집된 skill 383개 중 40개를 표시합니다.
SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) for object-oriented design.
원문 언어: 영어
Pool sizing, connection lifetime, health checks, and resource exhaustion prevention.
원문 언어: 영어
Constraints, triggers, audit trails, referential integrity, and data validation.
원문 언어: 영어
B-tree indexes, composite indexes, covering indexes, UNIQUE indexes, and index trade-offs.
원문 언어: 영어
Safe schema migrations, backward compatibility, zero-downtime deployments, and rollback strategies.
원문 언어: 영어
EXPLAIN PLAN analysis, index selection, join strategies, and slow query debugging.
원문 언어: 영어
Database schema design with normalization, relationships, constraints, and data integrity.
원문 언어: 영어
ACID properties, isolation levels, locks, deadlocks, and transaction design.
원문 언어: 영어
Using bisect/git bisect to isolate failure to exact commit or code path.
원문 언어: 영어
Race conditions, deadlocks, thread analysis, happens-before relationships.
원문 언어: 영어
Parsing logs, correlation analysis, reconstructing timeline of failures.
원문 언어: 영어
Detecting memory leaks through heap dumps, retention analysis, and reference tracing.
원문 언어: 영어
CPU/memory profiling, identifying bottlenecks, flame graphs, hotspot analysis.
원문 언어: 영어
Writing comprehensive postmortems: timeline, root cause, prevention, action items.
원문 언어: 영어
Five Whys, fishbone diagrams, identifying systemic causes not just symptoms.
원문 언어: 영어
Disciplined methodology to isolate bugs through hypothesis-driven testing. Form hypotheses, test them with minimal changes, narrow scope systematically. Use when bugs are unclear or reproduce intermittently.
원문 언어: 영어
SLO-based alerting, threshold tuning, incident escalation, runbooks, and on-call management.
원문 언어: 영어
GitHub Actions, GitLab CI, Jenkins; stages, artifacts, caching, and deployment automation.
원문 언어: 영어
Blue-green, canary, rolling deployments, traffic shifting, and safe release strategies.
원문 언어: 영어
Dockerfile best practices, layer optimization, multi-stage builds, security, and image size reduction.
원문 언어: 영어
Designing feature flags for gradual rollouts, A/B testing, and safe feature releases.
원문 언어: 영어
Terraform, CloudFormation, reproducible infrastructure, version control, and IaC best practices.
원문 언어: 영어
ELK Stack, structured logging, log query patterns, and centralized log management.
원문 언어: 영어
Metrics, logs, traces (observability); choosing what to measure, dashboards, and incident response.
원문 언어: 영어
Systematic code review process, feedback templates, approval criteria, and review best practices.
원문 언어: 영어
Documentation levels and types (README, architecture, API, runbooks), keeping docs current and discoverable.
원문 언어: 영어
Feature branches, commit hygiene, rebasing vs. merging, and collaborative workflows.
원문 언어: 영어
SEV classification, incident command system, communication, and incident response procedures.
원문 언어: 영어
Runbook templates, escalation procedures, playbooks, and incident playbooks.
원문 언어: 영어
Effective pair programming, driver/navigator roles, tools, and collaboration patterns.
원문 언어: 영어
Clear technical documentation, API docs, architecture decision records, and runbooks.
원문 언어: 영어
Big O notation, time/space complexity analysis, and choosing efficient algorithms.
원문 언어: 영어
Actor model, CSP (Communicating Sequential Processes), lock-free patterns, async/await.
원문 언어: 영어
Choosing optimal data structures based on access patterns and performance requirements.
원문 언어: 영어
Gang of Four patterns (Creational, Structural, Behavioral) and when to apply them.
원문 언어: 영어
Higher-order functions, composition, monads, immutability, and functional programming idioms.
원문 언어: 영어
Streams, observables, event-driven reactive systems, backpressure, and reactive programming.
원문 언어: 영어
RAII (Resource Acquisition Is Initialization), cleanup patterns, resource leaks, and lifetime management.
원문 언어: 영어
Finite state machines, event sourcing, CQRS (Command Query Responsibility Segregation), and state modeling.
원문 언어: 영어
Testing multiple components together; contract verification; real I/O (database, HTTP). Use when testing component interactions.
원문 언어: 영어