Build a Reusable AI Assistant for the Task You Do 20 Times a Week
If you use AI for the same kind of task over and over — triaging support emails, rewriting job posts, turning notes into tickets — you’ve probably noticed you keep typing the same setup instructions at the start of every chat. “You’re a support rep for a software company, our tone is friendly but concise, never promise a refund without approval…”
There’s a better way. Almost every major AI tool now lets you save that setup once and reuse it. Let’s build one.
What we’re building
A small, single-purpose assistant that already knows its job before you say a word. You give it the standing rules once; from then on you just paste in the new email, note, or draft and it does the task your way.
Under the hood this is just a system prompt
The standing instructions a model reads before it ever sees your message —
its “job description.” You normally never see it, but the custom-assistant
features let you write your own. It’s the difference between briefing a
temp every single morning and hiring someone who already knows the role.
Step 1: Pick one narrow job
The mistake is building a “general assistant.” Those are useless because they’re vague. Build something narrow enough to describe precisely:
- Good: “Rewrites our raw meeting notes into Jira tickets in our format.”
- Too broad: “Helps with product management.”
Narrow tasks have clear rules. Clear rules make a good assistant.
Step 2: Write the standing instructions
Open the “create a project / custom GPT / gem” feature in your tool and write instructions as if onboarding a new hire for exactly this one task. A reliable structure:
- Role — “You turn my rough meeting notes into well-formed tickets.”
- Rules — the non-negotiables. “Every ticket has a title, an acceptance-criteria list, and a priority. Never invent details I didn’t give you.”
- Format — show the exact output shape you want, with a filled-in example.
- What to do when unsure — “If a note is ambiguous, list your questions at the bottom instead of guessing.”
That last rule matters more than it looks. It’s the main defense against
a hallucination
When a model states something with total confidence that isn’t actually
true — because it’s built to produce a plausible-sounding answer, not to
look something up. Telling it to ask instead of guess when information is
missing is one of the simplest ways to cut this down.
Step 3: Attach reference material it should always have
If the task always needs the same background — your style guide, a glossary, a list of your team members, last quarter’s goals — attach those files or paste them into the instructions. Now they’re baked in. You’ll never re-paste your style guide again.
Some tools call this “knowledge” or let you upload files to the project.
Behind the scenes it’s a lightweight version of retrieval
When the tool automatically pulls relevant chunks from documents you’ve
given it and slips them into the conversation as needed — so it can
reference a 40-page handbook without you pasting the whole thing each time.
Step 4: Test it with three real cases, then fix the instructions
Run three real inputs through it. When it gets something wrong, don’t correct it in the chat — go back and fix the standing instructions, so the fix sticks for every future run. This is the key mindset shift:
You’re not correcting an answer. You’re editing the job description.
A few loops of this and the assistant stops making the same mistakes entirely.
Step 5: Name it well and share it
Give it an obvious name (“Notes → Tickets”) so future-you finds it in two seconds. If your tool supports team sharing, hand it to a colleague — now the whole team does the task the same way, and you’ve quietly standardized a process without writing a policy doc.
The takeaway
Any task you re-explain more than a few times a week is a candidate for this. The upfront cost is fifteen minutes. The payoff is never typing that setup again — and getting more consistent results, because the rules stop depending on whether you remembered to include them today.
Related: Turn a Report You Dread Into a 10-Minute Task — the same “save the recipe” idea, applied to reporting.