Prompting
Setting constraints
Set the length, format, tone and limits of the answer, and say what the model must not do.
Constraints frame the answer: expected length, structure (list, table, email), tone, language, allowed sources and the things to avoid. They turn an open request into a specification the result can be checked against.
A prompt without constraints gets an answer of arbitrary shape: too long, off-brand or impossible to paste into the tool that needs it. Explicit constraints keep answers consistent from one request to the next, which matters as soon as a team shares its prompts.
Good constraints are measurable (“three bullet points, under 80 words”), few enough not to contradict each other, and say what to do when information is missing, for instance ask a question rather than invent an answer.
In the reports of your games, every answer linked to this skill counts: the skill is shown as acquired from 80% of correct answers, and in progress from 50%.
Games that train this skill
Play them for free, without an account, then adapt them for your teams.
