Same model, same price — what changes the output is how you drive it. Eight habits we use to get more out of any LLM. Steal them.
Dictation runs about 3× the words per minute typing does, and talking drags out the context, caveats, and specifics a model needs. Hold the mic and explain it like you would to a teammate — the detail comes free.
Point the model at a specific skill — front-end design, a marketing framework — and it executes a real discipline instead of a generic answer. No skill for what you need yet? Have it build one, then reuse that expertise forever.
Declare the end-state up front and every step stays aimed at it, instead of drifting message to message. Use the /goal feature where you've got it.
For anything genuinely hard, turn reasoning up to maximum and let the model think before it answers. The extra thinking time pays for itself — you get a right answer on the first pass instead of a fast one you have to redo.
Consumer subscription tiers ship far more usage per dollar than metered API credits. For hands-on daily driving, a flat plan used hard goes further — save the API budget for what truly needs automating.
Give the model eyes on the result — let it run the test, read the error, see the screenshot — and a tight loop to fix what it finds. It closes the gap itself in seconds instead of handing you a draft to debug.
The model works from what's in the window, so hand it the real file, the real error, the real constraints up front. Solid context beats clever phrasing every time.
Confident and correct are different settings, so make the work prove itself — run it, hit the URL, show the output — before "done" counts. The best results arrive with their own evidence.