How to get Maximum from DeepSeek v4?

1> Use Codex 5.5 as brain and Deepseek v4 as muscle. Codex plans the work, DeepSeek produces the work, and Codex reviews and finalizes the work.

2> Write specs: start every project with a Codex plan
Using Deepseek v4 without specs is a crime! Codex should define the job clearly. Write PRDs, attach schemas, rule files, provide strict output formats.

3> Force DeepSeek to stay grounded
DeepSeek’s biggest weakness is that it can invent details that sound believable (classic hallucination). To prevent this, always tell it that every factual claim must come from the provided source.

4> Give DeepSeek a clear output box
DeepSeek performs much better when the output format is strict. Give it a JSON schema, a table format, exact field names, examples of good output, examples of bad output, and a checklist it must pass.

5> Use <Thinking mode> only for hard problems
When you provide specs with strict workflow to follow you don't need reasoning mode, that slows it down. The rule is: use cheap mode for volume and thinking mode for difficulty.

6> Batch similar tasks together
DeepSeek works best when one batch contains one kind of task. With batching it's cheaper and more organized but make sure you have quality guardrails to evaluate the outputs. 

7> Use Codex to build quality checks
For repeatable work, Codex should create validators. These checks should confirm that JSON parses correctly, fields are not empty, placeholders are removed, duplicates are detected, etc. 

8> Never let DeepSeek guess critical values
DeepSeek can invent emails, phone numbers, file paths, user IDs, database IDs, event IDs, API names, version numbers, prices, dates, citations, etc (hallucinations).

9> For long context, ask for an index first
When giving DeepSeek a huge document, repo, or log file, do not immediately ask for the final answer. First ask it to create a map of the material: key sections, important details, source locations etc.

10> Use its weakness for creativity
DeepSeek’s tendency to create plausible details is dangerous for factual work, but useful for creative work. Use it for brainstorming, naming, scenarios, UI copy options, test ideas, edge cases, and synthetic examples.

> Final Principle
DeepSeek V4 gives the most value when you treat it as a powerful worker, not an unquestioned authority.

- Let DeepSeek generate aggressively.
- Make Codex verify carefully.
- Keep what passes the validator.
- Repair or discard the rest.