Latest Agent Skills
25788 skills
snoodleboot-io State Management Architecture
The single highest-leverage decision is recognizing that most of what teams call
2
snoodleboot-io Post Implementation Checklist
Comprehensive checklist for documenting follow-up work and testing needs after implementation
2
snoodleboot-io Documentation Best Practices
Almost all bad documentation is well-intentioned writing in which two or more
2
snoodleboot-io CSS Performance Optimization
Every visual change enters the pipeline at one of four stages, and the stage
2
snoodleboot-io Container Security Hardening
A container image is an attack surface you chose.
2
snoodleboot-io Anomaly Detection Techniques
"Anomaly" covers three distinct problems, and a detector built for one is close to
2
snoodleboot-io Model Performance Debugging
Run this before anything else.
2
snoodleboot-io Hyperparameter Optimization
The search algorithm matters far less than the budget and the space you give it,
2
snoodleboot-io Feature Importance Analysis
"Feature importance" is ambiguous.
2
snoodleboot-io Cross Validation Strategies
Cross-validation only estimates generalization if the split mimics the gap between
2
snoodleboot-io Slowly Changing Dimensions
**When:** Not important (contact info)
2
snoodleboot-io Responsive Design Patterns
Both directions produce working layouts, but very different amounts of CSS.
2
snoodleboot-io Managed Database Selection
The most expensive database mistakes are made before a single row is written, by
2
snoodleboot-io Incremental Implementation
Comprehensive guide for implementing code incrementally following established patterns, conventions, and quality standards
2
snoodleboot-io Incident Timeline Creation
**Server Logs:**
2
snoodleboot-io Distributed Caching Design
The default, because it fails open: when the cache is unavailable, reads still
2
snoodleboot-io Disaster Recovery Planning
Disaster recovery has exactly two quantitative inputs, and every architectural
2
snoodleboot-io Architecture Documentation
An ADR records one decision at the moment it is made, with the information that
2
snoodleboot-io Time Series Preprocessing
Almost every downstream bug traces back to an index that was assumed regular and
2
snoodleboot-io Technical Decision Making
The single most useful question before analysing anything is: *what does it cost
2
snoodleboot-io Technical Debt Management
Debt that exists only in engineers' heads cannot be prioritised, funded, or
2
snoodleboot-io Prometheus Query Patterns
rate(http_requests_total[5m])
2
snoodleboot-io Imbalanced Classification
Imbalance is not itself a problem — it is a symptom that the default loss and the
2
snoodleboot-io Data Validation Pipelines
A validation *boundary* is any point where data crosses from a system you do not
2
snoodleboot-io Batch Vs Realtime Scoring
The choice is not about scale or sophistication.
2
snoodleboot-io Verbose
API Security (Verbose)
2
snoodleboot-io Minimal
API Security (Minimal)
2
snoodleboot-io Test Coverage Categories
Comprehensive systematic approach to achieving complete test coverage through structured category-based testing
2
snoodleboot-io Performance Optimization
The instruction to profile before optimizing survives because intuition about
2
snoodleboot-io Nosql Database Selection
Relational modelling lets you defer query design: normalize the entities, and
2
snoodleboot-io Multiagent Orchestration
Run a genuinely-parallel multiagent implementation with detailed guidance - plan, gate on environment, spawn subagents concurrently, aggregate, and debug/retry
2
snoodleboot-io Grafana Dashboard Design
**Level 1: Executive Dashboard**
2
snoodleboot-io Dimensionality Reduction
Reduction is a trade, not an improvement.
2
snoodleboot-io Component Design Systems
A design system has three token layers, and conflating them is what makes systems
2
snoodleboot-io Cloud Provider Tradeoffs
Compute, object storage, block storage, a managed relational database, a message
2
snoodleboot-io Cloud Migration Strategy
There is no such thing as "the migration." An estate is a collection of
2
snoodleboot-io Technical Communication
Before writing anything, answer three questions: who reads this, what do they
2
snoodleboot-io Serverless Architecture
Serverless is a billing-and-scaling model, not a badge of modernity.
2
snoodleboot-io Python Typing And Async
Type hints are checked by a separate tool (`mypy`, `pyright`), never by CPython
2
snoodleboot-io Object Storage Patterns
Almost every object-storage mistake comes from carrying filesystem instincts into
2
snoodleboot-io Message Queue Selection
Messaging systems fall into three fundamental shapes, and most bad choices come
2
snoodleboot-io Cloud Networking Design
A VPC is a private IP space you own inside a region.
2
snoodleboot-io Cloud Cost Optimization
Almost every cloud estate is over-provisioned.
2
snoodleboot-io API Versioning Strategy
Versioning exists because you cannot deploy your clients.
2
snoodleboot-io Model Interpretability
"Make it interpretable" is four different requests.
2
snoodleboot-io Flaky Test Remediation
A flaky test is one that produces different results on unchanged code and an
2
snoodleboot-io Continuous Improvement
The purpose of a postmortem is to change the system, and that only works if people
2
snoodleboot-io Autoscaling Strategies
Every autoscaling decision is driven by one of three trigger types, and mature
2
snoodleboot-io Problem Decomposition
A stakeholder asks to make search faster.
2
snoodleboot-io Mlops Pipeline Design
Software CI assumes a git sha plus a lockfile determines the build.
2
snoodleboot-io Edge And Cdn Delivery
A CDN is a cache that obeys your origin's instructions.
2
snoodleboot-io Debugging Methodology
Debugging is the scientific method under time pressure.
2
snoodleboot-io Compliance Automation
The annual compliance scramble exists because controls are tested once, by
2
snoodleboot-io Code Review Practices
The single highest-leverage convention in code review is prefixing every comment
2
snoodleboot-io Test Data Strategies
These three are not interchangeable, and picking the wrong one is the root of a
2
snoodleboot-io Root Cause Five Whys
1.
2
snoodleboot-io Multi Cloud Strategy
"Multi-cloud" is a loose word that hides four distinct architectures with
2
snoodleboot-io Mermaid Erd Creation
Comprehensive guide for creating entity relationship diagrams using Mermaid syntax
2
snoodleboot-io Idempotency Patterns
**Pattern:**
2
snoodleboot-io Feature Store Design
The pitch is often "a central place to store features," which undersells it into
2