Role + goal + definition of done: Do not just say “help me build an app.” Spell out the role, one concrete goal, and a numbered “Done means” definition.
Lock down constraints first: State the tech stack, audience, tone, facts that must not be fabricated, and the scope-expansion or destructive operations that require questions first.
Request structured output: Specify a table, file tree, fields, patch checklist, or step plan so you do not get a long block of prose that cannot be used directly.
Set reasoning effort before generating: Use low/medium for simple rewrites and high/xhigh for complex coding and multi-source research. Change only one variable at a time in subsequent iterations.
You are a research analyst. Goal: produce a decision memo on [TOPIC] for [AUDIENCE]. Done means: (1) 5 key findings with sources labeled, (2) one recommendation, (3) three open risks. Constraints: do not invent statistics; flag missing data as questions. Return exactly those three sections — no intro essay.You are a senior TypeScript engineer. Goal: propose a minimal fix for [BUG OR FEATURE] in this codebase description: [PASTE]. Done means: (1) root-cause hypothesis, (2) files to touch, (3) step plan under 8 steps. Constraints: no new dependencies unless essential; ask before expanding scope. After the plan, list two self-checks you would run before coding.You are a product engineer. Goal: turn this idea into a working first-version plan: [PRODUCT IDEA]. Done means: (1) user flows for the core loop, (2) screen list, (3) component map, (4) one sample UI copy block for the primary screen. Constraints: web app, mobile-first, no payments in v1. Prefer a substantial first structure over a thin outline. Stop after the four deliverables.After completing the first round, iterate on one variable from “scope, constraints, format, reasoning level.” For long tasks, append “Verify assumptions, then continue. List what you tested.” and require the model to list what it verified.
Grok 4.6