All authors
Claude Skills by snoodleboot-io
github.com/snoodleboot-io317 skills0 installs461 views
- Anomaly Detection Techniques\"Anomaly\" covers three distinct problems, and a detector built for one is close toVotes: 0GitHub stars: 2
- Api SecurityAn API has no UI to hide things behind.Votes: 0GitHub stars: 2
- Api Versioning StrategyVersioning exists because you cannot deploy your clients.Votes: 0GitHub stars: 2
- Architecture DocumentationAn ADR records one decision at the moment it is made, with the information thatVotes: 0GitHub stars: 2
- Autoscaling StrategiesEvery autoscaling decision is driven by one of three trigger types, and matureVotes: 0GitHub stars: 2
- Batch Vs Realtime ScoringThe choice is not about scale or sophistication.Votes: 0GitHub stars: 2
- Cloud Cost OptimizationAlmost every cloud estate is over-provisioned.Votes: 0GitHub stars: 2
- Cloud Iam DesignLeast privilege is easy to state and hard to hold: grant each identity only theVotes: 0GitHub stars: 2
- Cloud Migration StrategyThere is no such thing as \"the migration.\" An estate is a collection ofVotes: 0GitHub stars: 2
- Cloud Networking DesignA VPC is a private IP space you own inside a region.Votes: 0GitHub stars: 2
- Cloud Provider TradeoffsCompute, object storage, block storage, a managed relational database, a messageVotes: 0GitHub stars: 2
- Code Review PracticesThe single highest-leverage convention in code review is prefixing every commentVotes: 0GitHub stars: 2
- Compliance AutomationThe annual compliance scramble exists because controls are tested once, byVotes: 0GitHub stars: 2
- Component Design SystemsA design system has three token layers, and conflating them is what makes systemsVotes: 0GitHub stars: 2
- Container Security HardeningA container image is an attack surface you chose.Votes: 0GitHub stars: 2
- Continuous ImprovementThe purpose of a postmortem is to change the system, and that only works if peopleVotes: 0GitHub stars: 2
- Cross Validation StrategiesCross-validation only estimates generalization if the split mimics the gap betweenVotes: 0GitHub stars: 2
- Css Performance OptimizationEvery visual change enters the pipeline at one of four stages, and the stageVotes: 0GitHub stars: 2
- Data Model DiscoveryComprehensive process for discovering and validating data model requirements before designVotes: 0GitHub stars: 2
- Data Partitioning**Monthly Partitions:**Votes: 0GitHub stars: 2
- Data Validation PipelinesA validation *boundary* is any point where data crosses from a system you do notVotes: 0GitHub stars: 2
- Data Versioning ReproducibilityA git SHA pins the transformation.Votes: 0GitHub stars: 2
- Debugging MethodologyDebugging is the scientific method under time pressure.Votes: 0GitHub stars: 2
- Deployment Rollback StrategiesThe relevant axis is not \"how do we deploy\" but \"how fast and how cheaply can weVotes: 0GitHub stars: 2
- Dimensional Modeling**Structure:**Votes: 0GitHub stars: 2
- Dimensionality ReductionReduction is a trade, not an improvement.Votes: 0GitHub stars: 2
- Disaster Recovery PlanningDisaster recovery has exactly two quantitative inputs, and every architecturalVotes: 0GitHub stars: 2
- Distributed Caching DesignThe default, because it fails open: when the cache is unavailable, reads stillVotes: 0GitHub stars: 2
- Distributed Tracing InstrumentationUser RequestVotes: 0GitHub stars: 2
- Documentation Best PracticesAlmost all bad documentation is well-intentioned writing in which two or moreVotes: 0GitHub stars: 2
- Edge And Cdn DeliveryA CDN is a cache that obeys your origin's instructions.Votes: 0GitHub stars: 2
- Ensemble MethodsExpected error decomposes into bias, variance, and irreducible noise.Votes: 0GitHub stars: 2
- Feature EngineeringCardinality and model family jointly determine the encoding.Votes: 0GitHub stars: 2
- Feature Importance Analysis\"Feature importance\" is ambiguous.Votes: 0GitHub stars: 2
- Feature PlanningPlan before implementing - understand scope and approach with detailed guidanceVotes: 0GitHub stars: 2
- Feature Store DesignThe pitch is often \"a central place to store features,\" which undersells it intoVotes: 0GitHub stars: 2
- Flaky Test RemediationA flaky test is one that produces different results on unchanged code and anVotes: 0GitHub stars: 2
- Grafana Dashboard Design**Level 1: Executive Dashboard**Votes: 0GitHub stars: 2
- Hyperparameter OptimizationThe search algorithm matters far less than the budget and the space you give it,Votes: 0GitHub stars: 2
- Iac Best PracticesState is the map between your code and real resources.Votes: 0GitHub stars: 2
- Idempotency Patterns**Pattern:**Votes: 0GitHub stars: 2
- Imbalanced ClassificationImbalance is not itself a problem — it is a symptom that the default loss and theVotes: 0GitHub stars: 2
- Incident AutomationA runbook written in a wiki decays silently: the dashboard is renamed, theVotes: 0GitHub stars: 2
- Incident Timeline Creation**Server Logs:**Votes: 0GitHub stars: 2
- Incremental ImplementationComprehensive guide for implementing code incrementally following established patterns, conventions, and quality standardsVotes: 0GitHub stars: 2
- Infrastructure Drift DetectionDrift is the divergence between declared infrastructure and live infrastructure.Votes: 0GitHub stars: 2
- Key ManagementThe central pattern.Votes: 0GitHub stars: 2
- Kubernetes Resource ManagementTwo numbers with two different audiences.Votes: 0GitHub stars: 2
- Load TestingMost teams run one test — expected peak for ten minutes — and believe they haveVotes: 0GitHub stars: 2
- Managed Database SelectionThe most expensive database mistakes are made before a single row is written, byVotes: 0GitHub stars: 2