Skip to content
New: How I passed the Claude Certified Developer exam with 926/1000. Read the story →
A glowing glass cube turning scattered particles into ordered blocks

Stop chatting.
Start compiling.

The Superuser AI Prompting Guide. Field-tested patterns for getting reliable, structured output from Claude and other LLMs, written by a Claude Certified Developer.
100production system prompts
11free guide modules
926out of 1000 on the Claude developer exam
2ndedition, updated for Claude

How I passed the Claude Certified Developer exam with 926/1000

What actually mattered, why most practice exams are too easy, how the trick questions work, and a free simulator prompt you can copy.

Read the story →

I pointed Claude at Upwork: 33 jobs, 1 prototype, 1 proposal

Scouting and scoring freelance work with Upwork’s MCP server, and why I build the demo before I apply.

Read →

Google’s Ads MCP server ships with write tools on

Four of its seven default tools can change your account. How to switch them off and prove it.

Read →

Eleven modules, free to read. Each one turns a common way LLMs fail into a rule you can enforce.

Want the whole toolkit?

The Vault ($10): 100 production system prompts and the full guide as PDFs. The Architect Bundle ($35): everything in the Vault plus a tested Python kit for Claude’s API.

See what’s inside →
How do I get the most out of my LLM for daily tasks?

Move past conversational formatting and treat the model as an isolated compiler. Define strict role boundaries, state what the model must not do, and keep your input data separate from your instructions. You get shorter, more consistent single-turn answers.

How do I stop an LLM from hallucinating in production?

Give the model a defined way to fail. An explicit escape hatch, such as replying INSUFFICIENT_DATA, combined with validation in your code, means the model reports what it doesn’t know instead of inventing it. See Enterprise RAG Guardrails.

How do you guarantee accurate JSON output from a language model?

Don’t rely on the model to write valid JSON on its own. On Claude, structured outputs constrain the reply to your schema, and your code validates it and handles refusals and truncated replies. Module 2 shows the full pattern.

How do I stop an AI agent from getting stuck in a loop?

Build the stop into the loop itself: a dedicated “submit answer” tool as the only way to finish, an iteration cap, a tool-call budget and blocking of repeated identical calls. Module 3 covers the design.

Do temperature and top_p still work on Claude?

Not on Claude’s newer models, which reject non-default values. Reliability now comes from structured outputs, the effort setting, max tokens and validation. Module 6 explains what replaced them.