Quick-reference resources for software engineers
A Claude Code skill that structures ticket intake around assumption clarity. Writes a self-contained ticket MD file, tags every assumption with its source, proves assumptions before writing implementation code, and gates on human review.
View →Time complexity growth rates, practical input limits, and complexity of common algorithms, for fast lookup during algorithm analysis.
View →A ready-to-use markdown template for documenting architecturally significant decisions, including status, context, consequences, and compliance tracking.
View →HTTP method semantics (safe/idempotent) and a categorized status code reference for designing and debugging REST APIs.
View →All 23 Gang of Four design patterns, with intent, problem solved, when to use, and when to avoid, grouped by Creational, Structural, and Behavioral.
View →Nine software architecture styles compared by type, core strength, primary tradeoff, and typical use cases, from layered monoliths to space-based architecture.
View →22 architecture characteristics (operational, structural, cloud-specific, cross-cutting) with definitions, plus how to measure the most commonly prioritized ones.
View →Rolling, Blue-Green, Canary, A/B Testing, and Chaos Engineering deployment strategies compared by downtime, cost, complexity, rollback speed, and best fit.
View →Prompting technique definitions, a task-to-technique selection table, and common pitfalls to avoid.
View →Decision matrix and selection questions for choosing a software development methodology (Waterfall, Scrum, Kanban, XP, Shape Up, Lean, DevOps, and others) by project characteristics.
View →A copy-paste plan file and orchestrator prompt for running parallel AI agents through a batch content-generation pipeline, with model tiering and validation built in.
View →