Prompt template
A prompt template is a reusable prompt with placeholders for the parts that change — the file, the framework, the requirement — so a structure that works can be applied to many tasks without being rewritten each time.
Templates matter because prompt quality is mostly structural. A prompt that states scope, constraints, and verification works across tasks; only the specifics differ. Capturing that structure once removes the chance of forgetting the verification step at four in the afternoon.
The failure mode is over-templating. A template so generic it fits every task carries no useful constraints, and filling it in becomes a ritual rather than thinking.
What this means in practice
Every prompt in this library is a template in this sense: the structure is fixed, the customizer fills in the parts that vary. The point is to start from a shape that already includes the things people forget.
Prompts for the tools this applies to
Related terms
- Meta-prompting
Meta-prompting is using a model to write or improve a prompt rather than to do the task directly.
- System prompt
A system prompt is the instruction set given to a model before any user message, defining its role, constraints, and behaviour for the whole conversation.
- Spec-driven development
Spec-driven development means writing a precise specification before generating any code, then using that spec as the prompt.