X: Eric Zakariasson's Short Prompts and Strict Verification for Grok 4.6

Core observations

The author compares long and short prompts, as well as wording such as “work very hard.” The conclusion is that the specific wording itself has little impact. Long prompts can add specificity and suit tasks where the user already knows what they want, while Grok 4.6's default taste is good enough that a short prompt plus one clear preference can also produce solid results.

High-leverage sentence identified by the author

After giving the model a short prompt for a Sheets/Excel-style Next.js app, the author added this sentence:

Verify the function and design after implementation, and keep on iterating and verifying until it's production ready.

The author says this sentence led the model to open the app, click through real user paths, inspect nested formulas, and fix the problems it found. For visual tasks that are difficult to judge by whether the code runs, the author used a similar structure: first capture the current screen, list the problems, and then fix only those problems.

Reusable prompt pattern

Build [SPECIFIC GOAL].
After implementation, verify [USER FLOW] and [DESIGN/VISUAL STANDARD].
Keep iterating and verifying until [CLEAR COMPLETION CONDITION].

Another example

The product prompt provided by the author is:

Build a polished Sheets/Excel-style app in Next.js and an AI chat that can analyze the sheet. Use the Cursor SDK for all AI features. Preload a realistic sample workbook so it looks good immediately.

Usage takeaway

With Grok 4.6, instead of repeatedly stacking wording such as “work hard,” state clearly what completion means, and write real execution, browser paths, visual checks, and a repair loop into the acceptance criteria.