Prompt Composer

State exactly what you want and what success looks like. Be specific about what you want the output to accomplish.

Reference any files, documents, or background material you're uploading. Tell Claude to read them completely before responding. Move long background knowledge out of the prompt and into files — this frees the prompt for instructions only.

Provide a concrete example of excellent output — or describe one in detail. Define the tone, structure, and patterns you want replicated. Don't say "something like this"; show Claude exactly what good looks like.

Specify the output format, length, and scope. Also describe what the output should not be — avoiding the wrong direction is as useful as pointing toward the right one.

List any hard rules, non-negotiables, or default behaviors you need overridden. This is different from context files — these are inline guardrails that apply specifically to this task: audience considerations, legal/compliance limits, style mandates, or things Claude should always or never do here.

Instruct Claude to ask questions before producing output. This surfaces assumptions, catches ambiguities, and results in far better first drafts. Good prompting now starts with a dialogue — not a monologue.

Ask Claude to restate the approach in its own words before starting. This is distinct from asking questions — it's a verification step that catches misunderstandings and builds shared alignment. Nothing should be executed until both sides agree on the plan.