Loading...
Loading...
Found 47 Skills
Walk through decisions using a 3-part framework (first-principles, cost/benefit, second-order effects). Use when choosing between options, evaluating trade-offs, or making high-stakes decisions.
MUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs. Complements clickhouse-best-practices with decision frameworks and explicit provenance labels.
/em -challenge — Pre-Mortem Plan Analysis
Help users prioritize product roadmaps and backlogs. Use when someone is deciding what to build next, sequencing features, allocating resources across projects, handling stakeholder requests, or struggling with too many competing priorities.
Investment Analysis: Generate an in-depth investment analysis report. We do not conduct traditional investment analysis—the core judgment is whether the project is an "Order-Creating Machine". Activate this when the user says "investment report", "investment analysis", "analyze this project", "write an investment report", "investment report", "invest analysis", or provides entrepreneur conversation records for investment evaluation. Also activate when the user pastes or references meeting notes, pitch decks, or founder interviews and requests analysis.
Explore candidate solutions before committing. Use when you have a problem statement and need to evaluate approaches - band-aid, optimize, reframe, or redesign.
Multidisciplinary decision-making using mental models from psychology, economics, mathematics, and science to identify high-conviction opportunities and avoid cognitive biases. Keywords: latticework, lollapalooza, circle of competence, inversion, moats. NOT for single-discipline analysis, high-frequency trading, or speculative diversification.
Use when one agent is implementing code and another agent must review the resulting changes, compare the summary against the actual files, decide whether to fix now or move on, and write the next tightly scoped prompt with context handoff guidance.
Designs software architecture and selects appropriate patterns for projects. Use when designing systems, choosing architecture patterns, structuring projects, making technical decisions, or when asked about microservices, monoliths, or architectural approaches.
Decision framework for architectural patterns including DI, SOA, Repository, Domain Events, Circuit Breaker, and Anti-Corruption Layer. Use when designing systems, choosing patterns, or reviewing architecture.
Use when making design decisions, reviewing UI for HIG compliance, choosing colors/backgrounds/typography, or defending design choices - quick decision frameworks and checklists for Apple Human Interface Guidelines
Use when debates are trapped in false dichotomies, polarized positions need charitable interpretation, tradeoffs are obscured by binary framing, synthesis beyond 'pick one side' is needed, or when users mention steelman arguments, thesis-antithesis-synthesis, Hegelian dialectic, third way solutions, or resolving seemingly opposed principles.