Claude Skills by snoodleboot-io

\"Anomaly\" covers three distinct problems, and a detector built for one is close to

An API has no UI to hide things behind.

Versioning exists because you cannot deploy your clients.

An ADR records one decision at the moment it is made, with the information that

Every autoscaling decision is driven by one of three trigger types, and mature

The choice is not about scale or sophistication.

Almost every cloud estate is over-provisioned.

Least privilege is easy to state and hard to hold: grant each identity only the

There is no such thing as \"the migration.\" An estate is a collection of

A VPC is a private IP space you own inside a region.

Compute, object storage, block storage, a managed relational database, a message

The single highest-leverage convention in code review is prefixing every comment

The annual compliance scramble exists because controls are tested once, by

A design system has three token layers, and conflating them is what makes systems

A container image is an attack surface you chose.

The purpose of a postmortem is to change the system, and that only works if people

Cross-validation only estimates generalization if the split mimics the gap between

Every visual change enters the pipeline at one of four stages, and the stage

Comprehensive process for discovering and validating data model requirements before design

**Monthly Partitions:**

A validation *boundary* is any point where data crosses from a system you do not

A git SHA pins the transformation.

Debugging is the scientific method under time pressure.

The relevant axis is not \"how do we deploy\" but \"how fast and how cheaply can we

**Structure:**

Reduction is a trade, not an improvement.

Disaster recovery has exactly two quantitative inputs, and every architectural

The default, because it fails open: when the cache is unavailable, reads still

User Request

Almost all bad documentation is well-intentioned writing in which two or more

A CDN is a cache that obeys your origin's instructions.

Expected error decomposes into bias, variance, and irreducible noise.

Cardinality and model family jointly determine the encoding.

\"Feature importance\" is ambiguous.

Plan before implementing - understand scope and approach with detailed guidance

The pitch is often \"a central place to store features,\" which undersells it into

A flaky test is one that produces different results on unchanged code and an

**Level 1: Executive Dashboard**

The search algorithm matters far less than the budget and the space you give it,

State is the map between your code and real resources.

**Pattern:**

Imbalance is not itself a problem — it is a symptom that the default loss and the

A runbook written in a wiki decays silently: the dashboard is renamed, the

**Server Logs:**

Comprehensive guide for implementing code incrementally following established patterns, conventions, and quality standards

Drift is the divergence between declared infrastructure and live infrastructure.

The central pattern.

Two numbers with two different audiences.

Most teams run one test — expected peak for ten minutes — and believe they have

The most expensive database mistakes are made before a single row is written, by