Most prompts are written once, in a chat box, for one job. A reusable one has a few extra parts, and they have names. Here they are, six terms, with one prompt from the PromptAlo community library as the running example: Backup and Restore Policy for a Two-Person Web Studio Hosting Small Business Sites.
Solves line
The first line: who the prompt is for and what goes wrong without it.
Solves: Agencies of a few people whose backups grew piecemeal, so nobody is sure a site could be restored quickly after a failure or hack.
If you can't write this line, the prompt probably isn't ready to keep yet.
Variable
A bracketed field you fill in on each run. Everything around it stays fixed.
Fill in these variables: [HOSTING_SETUP], [CURRENT_BACKUPS], [CLIENT_PROMISES], [TEAM_ROLES], [CONSTRAINTS]
[CLIENT_PROMISES] is the interesting one here: the prompt checks it against [CURRENT_BACKUPS] and summarises the gaps between them.
Marker
A placeholder the answer is allowed to leave instead of guessing. This prompt uses [CONFIRM], and ties it to a real risk:
Do not promise recovery times that the setup cannot support; mark them [CONFIRM].
Adapt line
Where else the prompt works, and what to change.
How to adapt: Works for any small team responsible for other people's systems, such as an IT support firm or a managed app host. Swap the asset types.
Quality checklist
The boxes the answer checks before it is done, for example "Restore tests have owners" and "No unsupported timings".
Tags
Short labels for finding the prompt again. This one carries "backups, DevOps, agency hosting". In PromptAlo, saving a prompt also gets it an AI-written title and AI metadata tags, so a first save is labelled without extra typing. Before a prompt is shared publicly to the community library, AI Quality Review (Pro) runs PII checks.
Which of these six does your most-used prompt still lack?
This post was written with AI assistance and edited by the PromptAlo team.
Top comments (0)