Compare practical implementation approaches to the same engineering goal. Use when the user has one target outcome but multiple technical paths, such as incremental refactor vs rewrite, frontend-heavy vs backend-heavy implementation, service split vs monolith extension, wrapper library vs direct integration, or…
Improve technical and product decision-making with grounded analysis. Use when the user or Claude is deciding between approaches, asking "should I use X or Y?", evaluating a refactor, choosing frontend vs backend responsibilities, judging whether architecture is overkill, assessing a library or dependency choice, or…
Identify missing information, hidden assumptions, and uncertainty that make a technical decision unreliable. Use when the current recommendation may be under-informed, when a decision could flip based on unknown constraints, scale, ownership, security, rollout, or operational details, or when Claude is about to act on…
Compare technical options across the factors that actually matter in context. Use when Claude or the user needs a concrete tradeoff analysis between two or more approaches, such as library choice, architecture choice, refactor vs leave it, frontend vs backend ownership, build vs buy, short-term speed vs long-term…