Assumptions-First Task Planning Skill
A Claude Code skill that structures ticket intake around assumption clarity. Writes a self-contained ticket MD file, proves assumptions before writing implementation code, and gates on human review.
View →Quick-reference resources for software engineers
A Claude Code skill that structures ticket intake around assumption clarity. Writes a self-contained ticket MD file, proves assumptions before writing implementation code, and gates on human review.
View →The ten most critical web application security risks as ranked by OWASP, with impact and mitigation guidance for each.
View →Time complexity growth rates, practical input limits, and complexity of common algorithms — a fast lookup for 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 →The eight original fallacies (Deutsch, 1994) plus three modern additions — false assumptions that break distributed systems in production, with mitigations for each.
View →OWASP's top ten security risks specific to Large Language Model applications, with mitigation strategies for each.
View →Quick lookup for choosing the right data structure or algorithm by need — first choice, alternative, and what to avoid.
View →All 23 Gang of Four design patterns — 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 →The eight standard relationship patterns between bounded contexts in Domain-Driven Design, with when to use each.
View →Rolling, Blue-Green, Canary, A/B Testing, and Chaos Engineering deployment strategies compared by downtime, cost, complexity, rollback speed, and best fit.
View →Nine-dimension comparison of gRPC, REST, GraphQL, and message queues — protocol, coupling, streaming, tooling, and best-fit use case for each.
View →Six recurring API design mistakes — chatty APIs, leaking implementation details, ignoring HTTP semantics, poor error handling, over-versioning, and missing documentation — each with the problem and the fix.
View →API Keys, OAuth 2.0, JWT, and mTLS authentication mechanisms compared by use case, pros, and cons, with common pattern-to-context mappings.
View →URI, Header, Content Negotiation, and Query Parameter versioning strategies compared by example, pros, and cons, with guidance on what triggers a major version bump.
View →Centralized, Federated, Guild-Based, and Hybrid architecture governance models compared by structure, advantages, disadvantages, and best fit.
View →Five common architecture governance anti-patterns — Governance Theater, Bottleneck Governance, Ivory Tower Architecture, Analysis Paralysis, and Inconsistent Enforcement — with warning signs and fixes for each.
View →