Constraints

Explicit, testable limits on the answer — length, tone, scope, allowed sources, forbidden claims, tech stack — that keep it useful.

Last updated: November 9, 2026 · Markdown version

← Back to glossary

How to apply it in prompts

Use this concept to reduce ambiguity and improve consistency. If you need strict formatting, combine it with a JSON guide and a per-model template.

Related terms:Negative prompting Evaluation

Strict JSON Models Packs

What it means

Definition: a constraint is a rule the answer must satisfy. Typical kinds are length (<= 120 words), tone (formal, no jargon), scope (only the attached document), format and forbidden content (no guarantees, no invented figures).
Why it matters: without limits, a model fills the gaps with the most generic answer. Constraints turn 'write something good' into something you can check.
How to apply it: make each one specific and testable ('<= 35 characters' beats 'short'), state it positively when you can ('use only the provided data'), and keep the list short enough to be followed.
Common mistake: piling on rules that conflict with each other. If a constraint can't be checked, rewrite it until it can, or drop it.

Copy-paste example

Write 5 ad headlines for [product], audience [audience], main benefit [benefit].
Constraints:
- <= 35 characters each.
- No guarantees, no superlatives, no "best" claims.
- One concrete detail per headline.
Return a numbered list and nothing else.

Opens the analyzer with the prompt prefilled.

Open in Promptea

FAQ

How many constraints is too many?

When the model starts dropping some, or two of them conflict. Keep the few that change the result and cut the rest.

How does Promptea use constraints?

Constraints is one of the six dimensions of the 0–100 score: it looks for explicit limits such as tone, length, deadline, region or rules the answer must respect.