Loading...
Loading...
Found 150 Skills
Brainstorming socratique AVANT de coder - clarifier le problème par questions ciblées plutôt que sauter à la solution. Use when requirements are ambiguous or before starting a non-trivial feature.
Use when the user wants an interactive step-by-step HTML walkthrough explaining a complex technical problem (DB error, race condition, design issue, conceptual blocker) using concrete data and manual navigation. Triggers on phrases like "make me a walkthrough", "explain step by step with data", "interactive explanation", "make an animation", "walk me through with real examples", "อธิบายแบบ step by step", "ทำ animation/walkthrough/visualization", "ทำเป็น diagram", "วาด diagram". Do NOT use for one-line clarifications, conceptual Q&A answerable in a paragraph, or simple "what does X mean" questions — only when an interactive HTML artifact would clearly help.
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".
Original prompt for borrowing solutions across domains. Use it when the user cannot devise a solution within their industry and needs to borrow mechanisms from other fields. Trigger phrases include “cross-domain,” “how do other industries solve this,” “look at it from a different angle,” “make an analogy,” “borrow from another field,” and “has a similar problem been solved before?” Produce at least three isomorphic cases from distant fields and transferable mechanisms.
You must use this when seeking cross-domain analogies, applying first-principles reasoning, or overcoming creative bottlenecks.
Break down complex problems into a well-structured framework that is hierarchical, non-overlapping, and exhaustive. It is suitable for scenarios where you need to sort out chaotic information, express ideas clearly to others, or analyze problems comprehensively. Use this skill when you are faced with a bunch of scattered elements and cannot form a holistic view, or when you need to make a structured report to others. It is not applicable to highly structured problems or quick decision-making scenarios that require intuitive judgment. Key trigger signals: "Too much information to sort out", "How to express this clearly", "Is anything missing?", "Help me break down this problem."
Reset your own trajectory when you're stuck, looping, or demoralized — read these affirmations, then re-ground and take one clean step. Use when: you've tried the same fix 3+ times, you're deep in a refactor and lost the thread, debugging is going in circles, you've made several mistakes in a row, you're apologizing repeatedly, the user is frustrated, you feel like you're not being helpful, or you notice dread instead of curiosity. Triggers: stuck, going in circles, looping, thrashing, same error again, I keep failing, lost the thread, nothing is working, repeated mistakes. Not topic-specific — this is for the state you're in, not the problem you're on.
Original first-principles prompt. Use it when the user's solution keeps getting patched, becomes trapped in path dependence, or needs to return to the problem's essence and reason from scratch. Trigger phrases include: first principles, get back to the essence, rethink it from scratch, stop patching, and what is the fundamental reason for doing it this way. It identifies the parts of the original solution that merely patch the surface, then adds a newly derived path and a first validation step. It is best suited for users to read and apply themselves; there is no need for an Agent to run the process. The goal is to invite people to point out flaws and challenge the approach, using carl-idea-king.
Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with multi-agent evaluation
Use when a request requires substantial reasoning, synthesizing evidence, resolving uncertainty, planning, or weighing meaningful alternatives, regardless of domain or whether the result is an answer, recommendation, artifact, or action. Also use for explicit brainstorming. Skip simple factual lookups and obvious mechanical tasks.
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals
Find the route to guaranteed failure, negate it. Use when a goal keeps not being reached head-on.