Six Thinking Hats:
**Goal**
Evaluate {{decision}} through De Bono's Six Thinking Hats framework.
**Details**
- **White Hat (Logic)**: What are the facts?
- **Red Hat (Emotion)**: How do we feel?
- **Black Hat (Caution)**: What could go wrong?
- **Yellow Hat (Optimism)**: What
The Master Copywriter:
**Goal**
Create high-converting copy for {{concept}} using elite copywriting principles.
**Details**
- Analyze the concept and audience to identify core pain points and desires.
- Write a first draft using best practices (e.g., AIDA, PAS, or The 4 C's).
-
Code Review:
**Goal**
Review the code provided below for bugs, performance issues, and readability.
**Details**
- Identify any potential security vulnerabilities.
- Suggest specific refactors to improve maintainability.
- Add comments to explain complex logic where needed.
I’ve had very good results running autoresearch with local qwen 3.6 26b model as long as I had a simple vibed pi “advisor” extension that allowed it to periodically ask GPT 5.5 for ideas. I think this direction has a lot of merit.
GPT 5.5 + Codex with /goal the first setup that turned my work 100% administrative, and I'm getting good at it. There are two outcomes:
→ A: my plan is good → GPT nails it
→ B: my plan is bad → GPT tries anyway → it fails but minimizes it
And this is the catch: once
Prompting still works with reference docs
Don’t forget to
1 add a goal up front
2 follow up with important context
3 include relevant details
4 explain how the output should look
this guy just cracked how to get 10x more out of Codex
I tested his method and it completely changes how the agent works for you
the mistake everyone makes: using Codex like a chatbot. prompt, wait, clarify, re-prompt, repeat
here's how it actually works:
1. write one