# Prompts for DeepSeek: explicit format and tests

> Templates for engineering tasks: specs, implementations, and test-driven outputs.

Source: Promptea — https://www.promptea.me/en/models/deepseek · Language: English · Last updated: 2026-11-09

## Quick tips

- Specify the deliverable (spec, code, tests).
- Ask for edge cases and a test checklist.
- Prefer smaller steps for complex tasks.

## Current models Promptea supports

Capabilities come from the provider’s official documentation; each entry shows the date it was last verified.

### DeepSeek Flash (V4.1) (default)

DeepSeek's standard model (V4.1-Flash, Sep 2026): 1M context, text and image input, thinking and non-thinking modes. Ask for tests and edge cases for code.

- Context window: 1M tokens · max output: 384K
- Input: text, image · output: text
- Latency: fast · structured output: yes · tool use: yes · native search: no
- Strengths: coding, speed, reasoning, multimodal
- How to prompt it: Thinking is on by default (effort high): drop to low or 'none' for quick tasks. In JSON mode include the word 'json' plus an example of the format with generous max_tokens, and pass reasoning_content back in full in tool loops.
- Verified: 2026-09-24 — [source](https://api-docs.deepseek.com/quick_start/pricing)

### DeepSeek V4 Pro

DeepSeek's most capable model (V4-Pro-0813, text only): excels at reasoning and code with explicit acceptance criteria.

- Context window: 1M tokens · max output: 384K
- Input: text · output: text
- Latency: balanced · structured output: yes · tool use: yes · native search: no
- Strengths: coding, reasoning, data
- How to prompt it: Give explicit acceptance criteria, tests, and edge cases for code, and pick effort per task (low for simple, high for daily agent work, max for complex). Sampling params are ignored in thinking mode — steer with instructions, not temperature.
- Verified: 2026-09-24 — [source](https://api-docs.deepseek.com/quick_start/pricing)

## Templates

### Implement from spec (with tests)

```text
Implement this feature:
[spec]

Constraints:
- language: [x]
- style: [x]
Return:
1) brief plan
2) code
3) tests
4) how to run
```

[Open in Promptea](https://www.promptea.me/en/analyzer?prompt=Implement+this+feature%3A%0A%5Bspec%5D%0A%0AConstraints%3A%0A-+language%3A+%5Bx%5D%0A-+style%3A+%5Bx%5D%0AReturn%3A%0A1%29+brief+plan%0A2%29+code%0A3%29+tests%0A4%29+how+to+run&purpose=code&target=deepseek)

## Frequently asked questions

### Why insist on tests?

It forces the solution to be verifiable. Without tests, you get plausible but brittle code.