Building reusable setups

The pattern that fails

Someone learns to write a good prompt, gets a good result, and then types it again from memory a week later, badly. Two weeks on they've stopped. Nothing was wrong with the technique — it just had nowhere to live.

What a setup holds

• Who you are, what the business does, and who the audience usually is.
• Your examples — the past documents that define the voice and structure.
• The standing rules: what's never mentioned, what's always included, how long, what tone.
• The boundary: what this setup must refuse to do.

In Claude this is a Project. In ChatGPT it's custom instructions or a saved setup. The mechanics differ, the content is the same, and the content is the valuable part — it ports to whatever replaces both.

The three or four worth building

Nobody needs twenty. Most businesses have three or four documents that account for the bulk of the writing, and they're usually boring: the client update, the quote, the report, the chasing email. Build those, properly, with real examples in them.

Keeping them honest

Setups drift. The examples age, a rule changes, someone edits it and doesn't tell anyone. Two habits fix it: one named owner per setup, and a quick read every quarter against a recent real document.

What this module covers

The difference between a good afternoon and a change that's still there in a month. A setup holds your context, your examples and your house rules, so getting your format stops depending on whoever happens to be typing.

• What belongs in a setup and what belongs in the individual request.
• Building one from a good past output rather than from a description.
• Sharing it across a team so quality doesn't depend on the keenest person.
• Writing down what to change when the template changes — the step that stops a setup being stranded with the person who built it.
• Where the checking step lives, and who owns it.

What someone can do afterwards

Produces your monthly report, your standard letter or your tender section from a handful of inputs, in your voice, without rebuilding the instruction each time — and can fix the setup themselves when the format moves.

Where it sits in the order

Last of the practical modules, and the one that decides whether the session was worth the afternoon. A workshop that ends here produces a change you can point at three weeks later.