All authors
Claude Skills by snoodleboot-io
github.com/snoodleboot-io317 skills0 installs461 views
- Mermaid Erd CreationComprehensive guide for creating entity relationship diagrams using Mermaid syntaxVotes: 0GitHub stars: 2
- Message Queue SelectionMessaging systems fall into three fundamental shapes, and most bad choices comeVotes: 0GitHub stars: 2
- Microservices Communication PatternsEvery synchronous call does two things beyond transferring data: it adds theVotes: 0GitHub stars: 2
- Ml DeploymentA model in production is never just weights.Votes: 0GitHub stars: 2
- Mlops Pipeline DesignSoftware CI assumes a git sha plus a lockfile determines the build.Votes: 0GitHub stars: 2
- Model EvaluationEvery metric encodes an opinion about which mistake hurts.Votes: 0GitHub stars: 2
- Model Interpretability\"Make it interpretable\" is four different requests.Votes: 0GitHub stars: 2
- Model MonitoringThe layers trade timeliness against definitiveness.Votes: 0GitHub stars: 2
- Model Performance DebuggingRun this before anything else.Votes: 0GitHub stars: 2
- Multi Cloud Strategy\"Multi-cloud\" is a loose word that hides four distinct architectures withVotes: 0GitHub stars: 2
- Multiagent OrchestrationRun a genuinely-parallel multiagent implementation with detailed guidance - plan, gate on environment, spawn subagents concurrently, aggregate, and debug/retryVotes: 0GitHub stars: 2
- Mutation TestingLine coverage answers \"did this line execute during the test run\".Votes: 0GitHub stars: 2
- Nosql Database SelectionRelational modelling lets you defer query design: normalize the entities, andVotes: 0GitHub stars: 2
- Object Storage PatternsAlmost every object-storage mistake comes from carrying filesystem instincts intoVotes: 0GitHub stars: 2
- Performance OptimizationThe instruction to profile before optimizing survives because intuition aboutVotes: 0GitHub stars: 2
- Post Implementation ChecklistComprehensive checklist for documenting follow-up work and testing needs after implementationVotes: 0GitHub stars: 2
- Problem DecompositionA stakeholder asks to make search faster.Votes: 0GitHub stars: 2
- Prometheus Query Patternsrate(http_requests_total[5m])Votes: 0GitHub stars: 2
- Python Typing And AsyncType hints are checked by a separate tool (`mypy`, `pyright`), never by CPythonVotes: 0GitHub stars: 2
- Quality Assurance\"Quality\" is unmanageable until it is a set of numbers with agreed definitions.Votes: 0GitHub stars: 2
- Responsive Design PatternsBoth directions produce working layouts, but very different amounts of CSS.Votes: 0GitHub stars: 2
- Root Cause Five Whys1.Votes: 0GitHub stars: 2
- Serverless ArchitectureServerless is a billing-and-scaling model, not a badge of modernity.Votes: 0GitHub stars: 2
- Slo Sli Definition**SLO (Service Level Objective):** What we promise (99.9%)Votes: 0GitHub stars: 2
- Slowly Changing Dimensions**When:** Not important (contact info)Votes: 0GitHub stars: 2
- Sql OptimizationAlways start with EXPLAIN ANALYZE to understand execution:Votes: 0GitHub stars: 2
- State Management ArchitectureThe single highest-leverage decision is recognizing that most of what teams callVotes: 0GitHub stars: 2
- Team CollaborationOwnership models are usually inherited rather than chosen, and the inherited oneVotes: 0GitHub stars: 2
- Technical CommunicationBefore writing anything, answer three questions: who reads this, what do theyVotes: 0GitHub stars: 2
- Technical Debt ManagementDebt that exists only in engineers' heads cannot be prioritised, funded, orVotes: 0GitHub stars: 2
- Technical Decision MakingThe single most useful question before analysing anything is: *what does it costVotes: 0GitHub stars: 2
- Test Aaa StructureApply Arrange-Act-Assert pattern for clear, maintainable tests with detailed guidanceVotes: 0GitHub stars: 2
- Test Coverage CategoriesComprehensive systematic approach to achieving complete test coverage through structured category-based testingVotes: 0GitHub stars: 2
- Test Data StrategiesThese three are not interchangeable, and picking the wrong one is the root of aVotes: 0GitHub stars: 2
- Test Mocking RulesComprehensive guidelines for when and how to use mocks, stubs, and fakes in testsVotes: 0GitHub stars: 2
- Testing StrategiesThree shapes get argued about as if one were correct.Votes: 0GitHub stars: 2
- Threat ModelingEvery methodology — STRIDE, PASTA, LINDDUN, attack trees — is a technique forVotes: 0GitHub stars: 2
- Time Series PreprocessingAlmost every downstream bug traces back to an index that was assumed regular andVotes: 0GitHub stars: 2
- MinimalFind rare, unexpected observations in data where labels are scarce or absent, and evaluate the result in a way that survives extreme class imbalance.Votes: 0GitHub stars: 2
- Verbose"Anomaly" covers three distinct problems, and a detector built for one is close to useless on the others.Votes: 0GitHub stars: 2
- MinimalConcrete configuration that shrinks an API's attack surface at the edge and in the runtime — transport, CORS, limits, headers, and egress.Votes: 0GitHub stars: 2
- VerboseTLS is either configured deliberately or inherited from a distro default written years ago. Pin the protocol floor and let 1.3 negotiate its own suites.Votes: 0GitHub stars: 2
- MinimalIdentify and close the failure modes specific to APIs — where the caller is a program, every endpoint is directly reachable, and the UI enforces nothing.Votes: 0GitHub stars: 2
- VerboseAn API has no UI to hide things behind. Every identifier a client has ever seen is an identifier it can replay against every endpoint. The dominant API vulnerability class — broken object-level authorization — is not a missing authentication check; the attacker is fully authenticated as themselves.Votes: 0GitHub stars: 2
- MinimalEvolve an API without breaking clients you do not control, and retire old shapes on a schedule instead of by surprise.Votes: 0GitHub stars: 2
- VerboseVersioning exists because you cannot deploy your clients. Once a third party — or your own mobile app sitting in an app store review queue — depends on a response shape, that shape is a contract, and the only safe assumption is that some caller depends on every observable detail of it.Votes: 0GitHub stars: 2
- MinimalRecord the structure of a system and the reasoning behind it, so that the next engineer can change it without re-deriving every decision from scratch.Votes: 0GitHub stars: 2
- VerboseAn ADR records one decision at the moment it is made, with the information that was actually available. Its value is not the decision — that is visible in the code — but the *forces*: what was considered, what was rejected, and what the choice costs. Six months later the code shows what; only the ADR shows why.Votes: 0GitHub stars: 2
- MinimalDesign authentication that proves who a user is, without leaking credentials or sessions.Votes: 0GitHub stars: 2
- VerboseAuthentication starts with never holding the secret you are checking. Store a verifier — a slow, salted hash — not the password.Votes: 0GitHub stars: 2