DeepSeek Prompting: Technical & Reasoning Workflows

Reasoning-ready structure

State the problem, known facts, unknowns, constraints and required output. Ask for a concise explanation of the method and a final answer that can be checked. For troubleshooting, require tests before conclusions.

Coding prompt

Review this code for correctness and maintainability.
1. State what the code appears to do.
2. Identify bugs separately from style issues.
3. For each bug, give a minimal reproducible example.
4. Propose the smallest safe fix.
5. Add tests that would fail before the fix and pass after it.
Do not invent dependencies that are not shown.

Network troubleshooting prompt

A server has link lights but cannot reach its default gateway.
Do not assume the root cause.
Separate Layer 1, Layer 2 and Layer 3 hypotheses.
For each hypothesis give: test, command/tool, expected result, failure signal and next action.
Stop before destructive changes.

Verification habit

Use AI to generate hypotheses and checks, not to replace evidence. Validate commands before running them, protect credentials and sensitive data, and confirm current product behavior in authoritative documentation.