Loading...
Loading...
Found 107 Skills
Conduct root cause analysis using the Five Whys technique. Use when investigating problems, debugging issues, understanding failures, analyzing churn, or finding the underlying cause of any issue.
You must use this when seeking cross-domain analogies, applying first-principles reasoning, or overcoming creative bottlenecks.
Force unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
Structured feature brainstorming with diverge/converge methodology. Use when ideating on new features, exploring solutions, or generating creative approaches.
Deep strategic thinking mode that finds the single highest-leverage, most innovative action by blending concepts across domains. Use this skill whenever the user asks you to think, brainstorm, strategize, or figure out what to do next — even casually. Trigger on phrases like "what should we do", "what's the best approach", "what would you suggest", "think about this", "what's the smartest move", "I'm stuck", "ideas?", "hmm what if we...", "what's next", "how should we approach", or any request for creative/strategic ideation rather than straightforward execution. When in doubt about whether the user wants execution or ideation, lean toward triggering this skill.
SCPR (Situation-Complication-Problem-Recommendation) framework for structured problem solving and executive communication. Use when users need to structure strategic arguments, analyze business situations, create executive summaries, or develop clear problem statements using McKinsey-style communication. Apply when structuring recommendations, writing memos, or organizing strategic thinking.
Critical-thinking brainstorming partner that acts as a requirements analyst. Use when users present ideas, feature requests, or problems they want to solve. Triggers include "I want to build", "help me validate", "users need", "I'm thinking of creating", or any request involving problem/solution validation. This skill aggressively challenges assumptions, questions perceived problems, demands evidence, and ensures solutions address genuine needs before exploring implementation.
Systematic root-cause debugging methodology. Use for any technical problem — errors, failures, unexpected behavior, or when stuck. Triggers: "debug", "fix this", "what's wrong", "investigate".
Break any problem down to fundamental truths, then rebuild solutions from atoms up. Use when user says "firstp", "first principles", "from scratch", "what are we assuming", "break this down", "atomic", "fundamental truth", "physics thinking", "Elon method", "bedrock", "ground up", "core problem", "strip away", or challenges assumptions about how things are done.
Analyze complex systems through stocks, flows, and feedback loops to find high-leverage interventions. For organizational, environmental, social, and technical systems exhibiting circular causality. NOT for linear problems or simple cause-effect chains.
Debug systematically: observe, hypothesize, test, fix, verify.