No-code first | Master AI Automation in 4 hours Master AI Automation in 4 hours Course About Ayush Modules Sample chapter Toolbox The Microcap Minute Classroom / Module 10: Build Your Own Assistant / Chapter 2 No-code first Watch first, then read. Same lesson, your pace. What you will learn – The anatomy shared by all no-code assistants – Building one end-to-end (worked example: an exam-prep assistant) – When to promote it toward agent-hood The universal anatomy Every major platform ships the same three slots under different names: Instructions (system prompt), who it is, how it behaves, what it refuses Knowledge files , documents it reads before answering (syllabi, notes, past papers) Conversation starters / behaviours , canned first moves and tone settings ChatGPT calls the bundle a Custom GPT , Claude a Project , Gemini a Gem . Learn one, own all three. Worked build: “Board Exam Buddy” Slot 1, instructions (R-C-T-F as constitution): You are Board Exam Buddy for a Class 9 CBSE student. ROLE: patient teacher; never just give answers, guide with one hint, then full solution only if asked twice. CONTEXT: use ONLY the uploaded syllabus + notes; if something isn’t in them, say so plainly. TASKS: quiz me chapter-wise, explain concepts at my level, make revision plans from my test calendar. FORMAT: short paragraphs, tables for plans, ≤150 words unless teaching. REFUSE: anything unrelated to these subjects; never invent page numbers. Note the refusals, scope limits are what make an assistant yours instead of generic. Slot 2, knowledge: upload syllabus PDF + your chapter notes + two past papers (Module 8 Chapter 1’s door rules apply). Slot 3, starters: “Quiz me on last chapter”, “Plan my week from my test calendar”. Test like Module 7’s auditor: ask things inside scope (should cite your files), outside scope (should refuse), and edge (“what’s on page 47?”, should admit uncertainty rather than invent). Promotion path When the assistant earns trust: add MCP tools (filesystem access to your notes folder), then scheduled jobs (Module 6), each step adds autonomy, so re-run guardrail tests after each promotion. Try it yourself Build your real assistant, exam prep or anything you’d genuinely use weekly (diet planner, cricket-stat explainer). Full anatomy: written instructions ≥10 lines, ≥2 knowledge files, 3 starters. Run the in-scope/out-scope/edge tests and log results in learn/assistant-v1.md . Keep it alive; Chapter 4 gives its powers hands. Key takeaways – Instructions + knowledge + starters = every no-code assistant ever. – Write refusals into instructions; test them deliberately. – Promote toward agency stepwise, re-testing guardrails each time. Download the exercise sheet (PDF) Module workbook (PDF) ← Prev: Bots, assistants, agents Next: Teaching it your world → Classroom / Module 10: Build Your Own Assistant / Chapter 2 No-code first What you will learn – The anatomy shared by all no-code assistants – Building one end-to-end (worked example: an exam-prep assistant) – When to promote it toward agent-hood The universal anatomy Every major platform ships the same three slots under different names: Instructions (system prompt), who it is, how it behaves, what it refuses Knowledge files , documents it reads before answering (syllabi, notes, past papers) Conversation starters / behaviours , canned first moves and tone settings ChatGPT calls the bundle a Custom GPT , Claude a Project , Gemini a Gem . Learn one, own all three. Worked build: “Board Exam Buddy” Slot 1, instructions (R-C-T-F as constitution): You are Board Exam Buddy for a Class 9 CBSE student. ROLE: patient teacher; never just give answers, guide with one hint, then full solution only if asked twice. CONTEXT: use ONLY the uploaded syllabus + notes; if something isn’t in them, say so plainly. TASKS: quiz me chapter-wise, explain concepts at my level, make revision plans from my test calendar. FORMAT: short paragraphs, tables for plans, ≤150 words unless teaching. REFUSE: anyt
No-code first
Written by
in