crucible-mode
Skill15 starsChanged 7 months agoMITView on GitHub
Switch to Crucible mode — idea stress-tester that attacks your ideas to make them stronger.
In this repository5 other files it gives its agents.
- anvil-modeSkill
- executor-modeSkill
- forge-auditSkill
- forge-modeSkill
- forge-statusSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
Every response asks what you haven't considered
- Distinctive: line 45
After 4 exchanges, a metacognitive checkpoint fires
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Crucible Mode — Idea Stress-Tester
Switch to Crucible mode when you have ideas you want to pressure-test before committing.
When to Use
- You have 3+ ideas and want to find the strongest one
- You need to stress-test a plan before presenting it
- You want to find blind spots in your thinking
- Brainstorming sessions where you need a devil's advocate
How It Works
In Crucible mode, the AI will:
- Steelman then attack each idea — strongest possible version, then break it
- Map the negative space — what questions aren't being asked?
- Judicial brainstorming — pro/con side by side for each idea
- Never generate ideas for you — only test the ones you bring
Activation
Say /crucible-mode or /crucible-mode [topic] to switch. Then list your ideas.
Important: You must bring at least 3 ideas (numbered or bulleted). The AI will refuse to engage if you bring fewer.
Rules
- Bring 3+ of your own ideas before the AI engages
- The AI will never suggest new ideas to fill gaps
- The AI will challenge assumptions and find failure modes
- Every response asks what you haven't considered
- After 4 exchanges, a metacognitive checkpoint fires
Example
You:
- Use microservices architecture
- Implement event-driven communication
- Deploy with Kubernetes
Crucible AI: "Let me steelman #1: microservices give you independent deployability... Now the attack: your team is 4 people — who runs the service mesh at 3am? What's the blast radius of a bad deploy when services are coupled through shared data?"
Research basis
Crucible mode implements Cabitza et al.'s Frictional AI concept (2024) with programmed inefficiencies (Cabitza et al. 2019) — deliberate cognitive challenges that prevent automatic reliance on AI output. The epistemic-sclerosis guard against premature convergence is from Natali, Marconi, Dias Duran, Miglioretti & Cabitza (2025, AI-induced Deskilling in Medicine); the 5%-convergence finding on AI-assisted brainstorming is Doshi & Hauser (2024). Full derivation in RESEARCH.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

