Use-Case Collections
Curated for actual software outcomes, not generic browsing. Each collection gives you an intro, who it is for, and a quality-ranked shortlist of top rules to copy into your workflow.
API Hardening
Lock down public/internal APIs before scale
Backend/API teams, platform engineers, and founders preparing for security reviews or enterprise customers.
Top 96 curated rules →
Incident Debugging
Find root cause fast and recover safely
On-call engineers, SRE-minded product teams, and anyone handling production incidents.
Top 88 curated rules →
Startup MVP Shipping
Ship quickly without creating unfixable debt
Founders, early startup teams, and solo builders moving from prototype to paying users.
Top 84 curated rules →
Enterprise Code Review
Raise consistency and quality across large teams
Tech leads, staff+ engineers, and review owners in multi-team codebases.
Top 92 curated rules →
Legacy Modernization
Refactor safely while shipping
Teams inheriting older systems and needing modernization without freeze-risk.
Top 78 curated rules →
Data Platform Reliability
Make pipelines and storage reliable at scale
Data/platform engineers, backend teams with heavy DB workloads, and analytics infrastructure owners.
Top 86 curated rules →
AI Agent Platform
Production patterns for agentic systems
Teams building AI copilots, assistants, or autonomous coding/workflow agents.
Top 104 curated rules →
Frontend Performance + UX
Fast interfaces that still feel polished
Frontend teams building React/Next/Vue apps where speed and UX both matter.
Top 94 curated rules →
Mobile Production Readiness
From prototype app to resilient release
iOS/Android teams preparing production launches and reducing crash/latency risk.
Top 80 curated rules →
DevEx + CI/CD Quality Gates
Keep velocity high with reliable automation
Developer productivity teams and product squads that want faster, safer merges.
Top 90 curated rules →
Secure Auth + Payments
Reduce risk in the highest-stakes flows
Teams handling user identity, billing, fintech, or regulated transaction workflows.
Top 82 curated rules →
Testing Quality Gates
Prevent regressions before they reach users
Any team tightening release quality, especially as codebase size and contributor count increase.
Top 98 curated rules →