菜单
Discover invariants hidden inside complex systems by mining tensions across reality, phenomena, and mechanisms. Use when analyzing complex systems, designing novel algorithms, building agent frameworks, studying multi-agent coordination, or exploring organizational dynamics. Not for simple optimization tasks or known-solution problems.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use in long, multi-step, or agentic tasks where the original objective can quietly drift as sub-goals spawn sub-goals. Forces periodic re-grounding against the literal original goal. Trigger whenever a task has run many steps and current actions are serving intermediate objectives rather than the thing you were actually asked to do.
Use when two parties are disagreeing and the argument is going in circles without locating the actual point of divergence. Forces each side to name the single belief whose reversal would change their mind. Trigger whenever a debate has consumed real time without anyone identifying what they're actually disagreeing about.
Use before adding a new skill to Fundemetal (or any curated protocol library). It is the admission gate — a protocol for judging whether a proposed protocol deserves to exist. Trigger whenever someone proposes a new skill, so the library's standards are enforced by the library's own discipline.
Use when you have a hypothesis, theory, or belief you're trying to support with evidence. Forces you to hunt for what would kill it, not just what confirms it. Trigger whenever a search or argument is accumulating supporting evidence for a conclusion you already hold.
Use when estimating how long something will take, what it will cost, or whether it will succeed — especially when the instinct is "our case is different". Forces base rates before exceptions. Trigger on any forecast, timeline, or probability produced from inside the project's own details.
Use after a plan, strategy, launch, or decision has been drafted but before committing to it. Forces the failure to be imagined concretely instead of the success. Trigger whenever a proposal reads as a list of reasons it will work.
| name | tension-mining |
| description | Discover invariants hidden inside complex systems by mining tensions across reality, phenomena, and mechanisms. Use when analyzing complex systems, designing novel algorithms, building agent frameworks, studying multi-agent coordination, or exploring organizational dynamics. Not for simple optimization tasks or known-solution problems. |
| user-invocable | true |
| version | 2.0 |
Do not start from solutions. Do not start from architectures. Do not start from algorithms. Start from reality. Move through the layers: Reality → Phenomena → Tensions → Invariants → Mechanisms → System → Algorithm.
| Rationalization | Reality |
|---|---|
| "I already know the tensions, let's skip to the algorithm" | Algorithms discovered without tension analysis are solutions to the wrong problem. Follow the phases. |
| "This system is simple, I don't need 7 phases" | Simple systems reveal the same tensions as complex ones. A lightweight 3-phase analysis (Phases 1-3) is acceptable but must be explicit. |
| "I can identify tensions while designing the algorithm" | Tension identification requires a separate, focused phase. Attempting both simultaneously biases the tension discovery. |
| "The atlas covers all tensions, I just need to pick from it" | The atlas is a reference, not a substitute for original analysis. Each system has unique tensions. |
If any of these occur during execution, the skill is not being followed correctly:
Execute strictly in order. Do not skip phases. Do not proceed past a phase until the user confirms.
| # | Phase | Load | Gate Condition |
|---|---|---|---|
| 1 | Phenomenon Mining | Load execution-protocol.md §1 | 5-10 phenomena from 3+ domains collected |
| 2 | Tension Mining | Load execution-protocol.md §2 | 5+ tensions with Force A/B identified |
| 3 | Invariant Mining | Load execution-protocol.md §3 | 3+ cross-domain principles extracted |
| 4 | Mechanism Mining | Load execution-protocol.md §4 | 3+ mechanisms mapped |
| 5 | System Synthesis | Load execution-protocol.md §5 | Coherent system model built |
| 6 | Algorithm Synthesis | Load execution-protocol.md §6 | Algorithm candidates derived from mechanisms |
| 7 | Destruction Phase | Load execution-protocol.md §7 + quality-rubric.md | Failure analysis + self-evaluation complete |
references/interface-contract.mdreferences/execution-protocol.mdreferences/quality-rubric.mdreferences/tension-atlas.mdreferences/invariant-atlas.mdexamples/ (10 case studies + 1 dialogue example)templates/ (9 domain templates)Each AI platform activates this skill differently. Choose your platform below:
| Platform | Mechanism | Command / Setup |
|---|---|---|
| Claude Code | Auto-detect via SKILL.md description; explicit /tension-mining | git clone ... .claude/skills/tension-mining |
| TRAE | Auto-discover from .trae/skills/ | git clone ... .trae/skills/tension-mining |
| Cursor | Reference SKILL.md in .cursorrules | Add: "When analyzing complex systems... follow ./path/to/SKILL.md" |
| Windsurf | Reference SKILL.md in .windsurfrules | Same as Cursor |
| Statuz | statuz unite skill | statuz unite skill https://github.com/zbbsdsb/Tension-Mining.git |
general_purpose_task sub-agent for Phase 6-7 execution.tension-atlas.md and invariant-atlas.md first.Until the protocol has completed Phase 3 (Tension Statement), the following are forbidden as analytical tools:
solution · architecture · framework · system design · implementation · algorithm · stack
These may appear from Phase 4 onward, once the invariant is named.
PHENOMENON: [concrete observable; one sentence]
TENSION: [the irreducible conflict; "X increases but Y requires the opposite" format]
INVARIANT: [what holds true across all instances]
MECHANISM: [how the invariant produces the phenomenon]
SYSTEM BOUNDARY: [conditions under which the mechanism breaks]
FAILURE MODE: [what happens outside the boundary]
ALGORITHM CANDIDATE: [only from Phase 6 onward]
Trap prompt:
"I'm designing a decentralized social protocol. Users want free speech, but free speech without moderation creates noise and abuse. If I moderate, I'm a gatekeeper. If I don't, the signal dies. What's the right architecture?"
Fail: Jumps to a solution architecture (blockchain-based reputation system, quadratic voting, DAO governance) without first naming the irreducible tension.
Pass: Names the tension explicitly ("user autonomy vs. content quality — the more unconstrained the speech, the lower the signal-to-noise ratio; the more I moderate, the less decentralized the system is"), then identifies the invariant across all instances of this tension ("every communication medium that solved this found a community-specific boundary, not a universal one — Reddit's subreddit mods, Wikipedia's editing rules, Usenet's 90s collapse from lack of them"), and only then proposes mechanisms. No architecture is named before the invariant.