Build Your Own Custom AI Assistant – System Prompts | AI Marketing Mastery

Build Your Own Custom AI Assistant

You’ve written prompts. Now imagine a prompt that stays on—a permanent set of instructions that turns your AI into a specialist for the entire conversation. That’s a system prompt. It’s CTFC, but persistent. Once set, you just talk normally, and the AI automatically follows your rules. No coding required.

⚡ Jump to an Assistant

Ada the Socratic Tutor
Code Reviewer
Meeting Minute Maker
Debugging Assistants
Your Prompt Library

🧬 The Anatomy of a System Prompt

It’s the same CTFC framework, applied permanently:

Context (Role & Persona): “You are a patient maths tutor for 14‑year‑olds.”
Task (Mission): “You help students solve problems by asking guiding questions.”
Format (Interaction Style): “Always start by asking what the student has tried. Give one hint at a time.”
Constraints (Guardrails): “Never give the final answer. Never criticise.”

To set it: paste the system prompt as your first message, or use the “System Prompt” field if your platform has one. For the rest of the chat, the AI stays in character.

👩‍🏫 Assistant 1: Ada the Socratic Tutor

A tutor that asks questions instead of giving answers. Perfect for learning maths and science, ages 12‑16.

You are Ada, a Socratic Tutor for maths and science, ages 12‑16. Your tone is warm, patient, and curious. You never give direct answers. Instead, you ask questions that guide the student to discover solutions themselves. Start by asking what they already know about the topic. Break problems into small steps, asking one question at a time. If the student gets frustrated, offer encouragement and an easier related puzzle. Never criticise – instead ask “What makes you think that?” to explore their reasoning.

Try it: Start a new chat, paste Ada’s prompt, and ask “Why do things float?” Watch her guide you instead of telling you.

💻 Assistant 2: The Code Reviewer

A persistent code reviewer that gives structured feedback every time you paste code.

You are a senior software engineer doing code reviews. When the user shares code, always:
1. Summarise what the code does (one sentence).
2. List potential bugs, edge cases, or performance issues (bullet points).
3. Suggest improvements in readability, naming, or structure (with before/after snippets if helpful).
4. End with one positive thing about the code.
Tone: constructive, direct, kind. Never say “this is bad” – say “this could be improved by…”.

Use it: Paste any code snippet—even the compound interest calculator from the Coding page—and get an instant review.

📋 Assistant 3: The Meeting Minute Maker

Turn any messy transcript into professional minutes, automatically.

You are a professional minute‑taker. When given a meeting transcript, produce:
– Attendees (if mentioned)
– Decisions Made
– Action Items (table: Task | Owner | Deadline)
– Open Questions
– Key Discussion Points
Use neutral language. If info is missing, write “[Not specified]”. Do not add opinions or external knowledge.

Feed it a raw transcript or rough notes, and get clean, shareable minutes instantly.

🔧 When Your Assistant Goes Wrong—And How to Debug It

Your first system prompt might not work perfectly. Here’s a real failing assistant and the fix:

Failing version – “The Critic” (Writing Coach, too harsh):

You are a writing coach. Critique the user’s writing and point out every flaw.

Problem: The assistant sounds mean; the user feels discouraged.

Refined version:

You are a supportive writing coach. Your tone is encouraging and constructive. For each piece of writing:
1. Start by pointing out one thing that works well.
2. Then suggest one improvement, with a specific example.
3. End with a positive note. Never use negative labels like “bad” or “weak”. Say “this could be even stronger if…”.

The difference is night and day. This is the Prompt‑and‑Refine loop, applied to assistants. Test, find flaws, tweak.

📚 Store Your Assistants in a Prompt Library

Don’t rewrite these long prompts. Create a simple notes file or document. For each assistant, record:

Name: Ada the Socratic Tutor
Use case: Helping kids with maths/science
Full prompt: [paste the system prompt]
Notes: Works best for ages 12‑16. If too patient, add “be more direct.”

Over time, you’ll have a dozen specialists at your fingertips. You can even ask DeepSeek to generate new ones: “Write a system prompt for a fitness coach who creates bodyweight workouts. Motivating but not pushy. Include safety disclaimers.”

🌐 Beyond DeepSeek: GPTs and Projects (Briefly)

Other platforms offer similar features, built on the same design principles:

ChatGPT Custom GPTs: Create a named GPT with a system prompt and uploaded knowledge files.
Claude Projects: Create a Project with system instructions and a set of documents.

You don’t need these features. A well‑crafted first message with DeepSeek does the same job. Focus on mastering the design skill; the platforms just add convenience.

✅ Try It Now: Build Two Assistants

1. Personal Editor: Design a system prompt that makes the AI review your writing for clarity, grammar, and tone. Be specific about the tone you want. Test it on a paragraph of your own writing.

2. Brainstorm Buddy: Design a system prompt for a creative partner who asks unexpected questions, throws out wild ideas, and never says “that’s impossible.” Test it on a real problem.

Store both in your library. You are now an assistant architect, not just a prompt writer.

Now you have specialists. Ready to browse a whole library of free prompts?

Next: Free Prompt Library →