I've read a few post on Reddit that claim codex uses less tokens and better results with the latest models particularly noting the token usage with opus 47

You can review the general policies by hitting the three dots on a post where it says "report to admins" and there is a list of bulleted list of community guidelines just don't submit yourself

@David Herrera I guess we're all susceptible to Click Bait, no matter how smart we are. I've been Busted. Here's my response: This is community-compiled prompting advice styled as an "internal Anthropic leak" for virality. It draws on real best practices (some of which Anthropic employees might use or endorse informally), but it is not a direct, authenticated release from Anthropic. Similar "leaked system prompts" or "internal frameworks" for Claude pop up periodically in places like Reddit's r/ClaudeAI, Skool, and X.

@P Patel here's the method I've been using ProjectName/ ├── 00_ZeroFluffLibrary/ # Master templates (one-time setup) │ ├── Prompt1_ContextBrief.md │ ├── Prompt2_ForceReasoning.md │ ├── Prompt3_HonestyOverride.md │ ├── ... │ └── Prompt10_PreMortem.md │ ├── 01_Context/ # Always run first │ ├── CONTEXT.md # Your background, goal, constraints, what you've tried │ └── input.md # Raw idea/question/plan │ ├── 02_Reasoning/ # Chain-of-thought + assumptions │ ├── stage_contract.md # "Apply Prompt 2 here" │ └── output_reasoning.md # AI response (step-by-step, assumptions, confidence) │ ├── 03_Honesty_RedTeam/ # Brutal honesty + devil's advocate │ ├── stage_contract.md # "Apply Prompt 3 + Prompt 5" │ └── output_critique.md │ ├── 04_Scope_Assumptions/ # Lock scope + audit assumptions │ ├── stage_contract.md │ └── output_audit.md │ ├── 05_Synthesis_Output/ # Final polished response in locked format │ ├── stage_contract.md # "Apply Prompt 7 + integrate previous outputs" │ └── final_output.md │ ├── 06_PreMortem_Review/ # Optional but powerful │ └── post_mortem.md │ └── Archive/ # Timestamped runs for iteration

Hey Nick, Great question — and congrats on the first proposal! Flip the script: we’re no longer selling services. We’re providing value. Price based on the potential savings or impact you deliver, not hours or market rates. Old web dev world: client needs a feature → sell a WordPress plugin + install time = invoice. With AI: I build the exact custom feature they need. It saves them dozens of hours a month, cuts third-party costs, and beats the competition. That’s way more valuable than a $79 plugin, so I price on the real value to them — not my time. Same logic applies to websites, automations, or anything else. AI lets you deliver outsized results fast, so your pricing should reflect that. Jackie’s system is basically doing this at scale. Once you switch to “value delivered” instead of “hours logged,” quotes get way easier (and feel fairer to clients). Would love to hear how your proposal lands — keep us posted!

@Jackie Groleau Nice work!

Without a solid foundation, the results will always be marginal. The prompt is that foundation—everything else is built on top of it. Don’t get me wrong: we’ve since added a contextual layer that works with prompts, and even moved beyond that to a harness layer that weaves context and prompts together. But when you really break it down, every skill is ultimately a set of refined prompts. The same is true for orchestration—it all rests on that same prompt-based foundation. So yes, I respectfully disagree. Prompts aren’t just one piece of the puzzle; they remain the core foundation, and they always will.

@Alex Nartey six of each, half dozen of the other...most importantly today is to describe the final output and who's doing the work. All the rest is supporting information and implementation