Loading...
Loading...
Found 96 Skills
TRIZ systematic innovation methodology with AI-enhanced prompts. Use when: (1) Technical contradiction - improve A but B worsens, (2) Physical contradiction - need opposite properties, (3) Cross-industry solutions via FOS/MOS, (4) Technology evolution prediction, (5) Complex engineering problems. Triggers: "TRIZ", "contradiction", "inventive", "trade-off", "improve without worsening", "ข้อขัดแย้งทางเทคนิค", "innovation breakthrough"
Adopt multiple expert personas sequentially for complex problem analysis from diverse perspectives. Single-agent only — do NOT spawn sub-agents.
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly. Use this skill whenever a user says "help me think through X", "challenge my thinking", "what am I missing", "apply mental models to this", "play devil's advocate", "stress test this idea", "poke holes in my plan", "help me decide between X and Y", "what are the second-order effects", "I'm stuck on a decision", names any specific model (SWOT, first principles, inversion, pre-mortem, etc.), or asks for structured reasoning on any ambiguous, high-stakes, or complex problem. Also trigger when the user seems uncertain, is rationalizing, or is asking "am I thinking about this right?" Even casual phrases like "what do you think about..." on non-trivial topics should trigger this skill.
Install and use the 毛选.skill cognitive framework for Claude Code — applies Mao Zedong's strategic mental models (contradiction analysis, protracted war, rural encirclement, united front) to help analyze problems, devise strategies, and cut through complexity.
Reasons through problems using six cognitive modes. Applies causal (execute goals), abductive (explain observations), inductive (find patterns), analogical (transfer from similar), dialectical (resolve tensions), and counterfactual (evaluate alternatives) thinking. Use when planning, diagnosing, finding patterns, evaluating trade-offs, or exploring what-ifs. Triggers on "why did", "what if", "how should", "analyze this", "figure out".
Apply first-principles thinking to break down complex problems into fundamental truths and rebuild solutions from the ground up. Use when solving strategic decisions, breaking through blockers, or challenging assumptions. Triggers on first principles, Elon Musk methodology, fundamental truths, strip assumptions, physics of the problem, rebuild from scratch.
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.
Apply a latticework of mental models from multiple disciplines to improve decision quality. Use this skill when the user needs to think more clearly, avoid cognitive blind spots, apply cross-disciplinary reasoning, or evaluate a complex decision from multiple angles — even if they say 'how should I think about this', 'what am I missing', 'give me a different perspective', or 'what frameworks apply here'.
Use logic tree approach to identify root causes of business problems. Use when diagnosing performance issues, process failures, or customer behavior patterns.
Root-cause-driven solution decision framework for the hardest problems across any domain. This is the nuclear option — it consumes significant tokens through exhaustive multi-branch root cause analysis, MECE solution enumeration, and domain-adaptive external validation. Use ONLY for genuinely difficult problems: recurring failures that resist repeated fix attempts, complex systemic issues with no clear solution path, decisions where multiple approaches exist and the wrong choice has high cost, problems with multiple interacting causes spanning components or teams. Trigger when: the user says 'what's the best way to fix X', 'why does this keep happening', 'how should we approach this', 'find the root cause', 'what are my options for fixing X', 'analyze this problem systematically', 'evaluate our options for X', 'what's the right approach and why', or expresses frustration that previous solutions didn't stick. Do NOT use for: problems where the answer is already obvious or requires no analysis, straightforward issues with clear solutions, or routine investigation. If the problem can be solved in 5 minutes of investigation, this skill is overkill.
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals
When a user is stuck, frustrated, or describing a problem vaguely, do NOT immediately suggest solutions. First, force structured problem articulation through targeted questions: What did you expect? What happened instead? What have you tried? Only after the problem is clearly defined, propose solutions.