Coding guides

Get useful code on the first pass.

Model choice matters, but clear context matters more. These patterns make coding conversations easier to verify and continue.

Give the smallest useful context

Use tools when facts may have changed

Ask for a way to verify the result

Describe the outcome first

Start with what should be true when the work is complete. Add the framework, important versions, and behavior that must not change.

Build a Next.js route that streams OpenRouter output. Keep authentication server-side, abort upstream work when the client disconnects, and return NDJSON events. Include one parser test.

Attach evidence, not everything

Include the failing component, exact error, and relevant configuration. Focused evidence improves attention and makes proposed changes easier to review.

Include: The error text, one reproduction path, and files directly involved in the failure.
Leave out: Secrets, build output, unrelated source, and personal customer information.

Choose for the work in front of you

Ox Alpha

Start here for long reasoning, connected tools, and complex implementation.

Qwen3.8 27B

Use it for multimodal coding, visual context, and long-context reasoning.

DeepSeek V4 Flash

Choose it when fast reasoning and tool use matter more than long deliberation.

Ask the model to prove the change

Request the exact typecheck, test, build, or manual workflow that would catch a regression. A useful answer includes a way to challenge it.

Start coding