Loading...
Loading...
Found 5 Skills
When facing architectural decisions, technology choices, or strategic trade-offs, present options as a structured comparison and require explicit trade-off acknowledgment before proceeding. Triggers on words like "should we", "which approach", "what's the best way", or when Claude is about to recommend one approach over alternatives. Never present a single recommendation without showing viable alternatives first.
Evaluate options for a specific design decision node and recommend one with explicit trade-offs. Use when the design already exposes a concrete choice such as architecture style, state management approach, auth model, storage pattern, sync strategy, multi-agent coordination model, language or runtime, UI framework, data-layer library, or tooling selection. Trigger when the user needs structured comparison and recommendation for a bounded design decision. Do not use for broad design discovery, full-system decomposition, or final readiness review.
Lead complex software implementation, architecture decisions, and reliable delivery across any modern technology stack. Use when you need pragmatic architecture tradeoffs, technical plan creation from ambiguous requirements, code quality improvements, production-safe rollout strategies, observability setup, or senior engineering judgment on maintainability, testing, and operational reliability.
Frontend architecture expert. Use when planning component architecture, state management strategies, performance optimization, or technology selection decisions.
Research a technical or product question before building — APIs, libraries, prior art in-repo, external docs, tradeoffs, and a recommendation. Use when the user says "research it", asks what to use, compares options, wants an RFC-style brief, or needs evidence before implementation. Read-only; spikes and dependency adds are a separate, asked-for step. Hand off to fix-it / recon issue / issues create when ready to plan or track.