AC 202: Build Your Personal AI Operating System
Turn your coursework into a structured AI knowledge base and run your first real project through it, with no coding background needed. For students and early-career professionals tired of re-explaining the same instructions every week.
3 chapters, 8 lessons
14-day refund on the yearly plan. Real pricing on the plans page, no surprises.
8
lessons, yours to run
Easy to pick up, built to get you the next job
No coding background needed, and you write code with Claude as you go.
Every section below turns into something a hiring manager recognises, not just notes.
Build a knowledge base that an AI tool can actually navigate
- You'll migrate one full course's worth of real notes into a structured, searchable folder using a consistent naming standard, no guesswork, no prior technical skill required, just a clear 12-point checklist and file-by-f
- You'll create an index file that gives you and any AI tool an instant map of the whole course's shape, so 'it's somewhere in here' stops being an acceptable answer.
- You'll walk away with a portfolio example you can describe in an interview: 'I took an unstructured pile of notes and made them searchable. Here's exactly how I did it.'
Build reusable skills so you stop re-explaining yourself
- You'll write your first SKILL.md: a saved, reusable instruction set for a task you repeat every week, so the AI tool already knows how you want it done.
- You'll test that skill on real content and fix gaps with one targeted addition per miss, not by rewriting everything from scratch.
- This is a capability a hiring manager recognises immediately: you built a repeatable process, documented it, and proved it works across more than one input.
Package your five most repeated prompts into slash commands
- You'll convert five prompts you've been retyping word-for-word into one-keypress slash commands stored in your repo, the fastest and most immediately visible part of the whole system.
- You'll adapt a library of 12 common student workflows to your own real courses, because a command tuned to your actual work is sharper than a generic one.
- No coding background assumed: each command is a plain markdown file with a name and an instruction, nothing more.
Run a real project through the system end to end
- You'll take an actual project from intake and scoping all the way through to a finished deliverable, using the knowledge base, skills, and slash commands you built in the earlier sections.
- You'll produce a working demo of your personal AI operating system in action, the kind of concrete portfolio proof that sets you apart when every other applicant just says they 'use AI'.
Finish this course and you can do all of this, no prior background required:
- You'll be able to build and maintain a structured knowledge base that an AI tool can navigate reliably, a skill any employer running knowledge-heavy work will pay for.
- You'll be able to write a reusable SKILL.md for any recurring task, test it on real content, and iterate on it without starting from scratch each time.
- You'll be able to package repeated prompts into slash commands, cutting the time spent on routine AI interactions and making your workflow immediately visible and demonstrable to a teammate or manager
- You'll be able to take a project from vague brief to finished deliverable using a personal AI system you built yourself, which is the concrete portfolio evidence most applicants cannot provide.
- You'll be able to describe, step by step, how you turned an unstructured pile of files into a searchable, AI-ready knowledge base, which is a specific, credible answer to the interview question 'give
8 lessons, 3 chapters
Built from real implementation work
Every agent, skill file, and dataset is drawn from 25+ years and 50+ Oracle ERP implementations across pharma, manufacturing, semiconductor, and distribution.
Kept current with the stack
Claude Code, skills, and MCP move fast. Your licence includes every system update for as long as you're subscribed, so what you build keeps working as the tools change.
A personal AI operating system fixes a problem you've probably hit. You take notes all term, but when you ask an AI tool to pull them together, the answer comes back thin. The information is there. It's scattered across files named 'notes', 'notes2' and 'week thing', and neither you nor the tool can find it quickly. You re-explain the same instructions every session because there's nowhere to save them. And when a role or internship asks for AI experience, you have no system, no artefacts and no working demo to show. Knowing AI tools exist is different from having built something with them, and employers can tell.
What you'll be able to do, module by module
Every module leaves you able to build and run something real. Here is the syllabus, in the order you work through it.
Curriculum
3 chapters · 8 lessons
Section 1: Your Knowledge Base
You can migrate a full course's worth of notes into a consistently structured, searchable knowledge base and describe exactly how you did it, using the weekNN-topic-name.md naming standard, a course index file, and a 12-point completion checklist.
Chapter 1.1: Structure Before Intelligence3 items
- L1: Why Context Hygiene Decides Output Quality🔒
- L2: Workbook: Build Your Coursework Knowledge Base🔒
- Quiz: Context HygieneQuiz
Section 2: Skills and Slash Commands
You can build a reusable SKILL.md for any recurring task, test it across genuinely different inputs, fix gaps with targeted additions rather than rewrites, and package your five most repeated prompts into one-keypress slash commands stored in your repo.
Chapter 2.1: Build Once, Use 50 Times4 items
- L3: Workbook: Your First SKILL.md🔒
- L4: Workbook: Package 5 Slash Commands🔒
- L5: Case Study: The Study Guide Skill Across 4 Subjects🔒
- Quiz: Skills and CommandsQuiz
Section 3: Run a Real Project
You can run a real project from intake and scope definition all the way through to a finished deliverable using your knowledge base, skills, and slash commands working together as a single personal AI operating system.
Chapter 3.1: End to End on the System4 items
- L6: Workbook: Project Intake and Planning🔒
- L7: Workbook: Research, Draft, Review, Deliver🔒
- L8: Workbook: Measure the Difference🔒
- Course Final: Personal OSQuiz
In an interview you can open your repo, show a structured knowledge base, trigger a slash command, and walk through how you ran a real project through a system you built yourself. That level of detail is what a hiring manager remembers after a day of interviews.
From subscribing to running your first artifact
Subscribe and open the course workbook
From day one you're working inside a real repo with a real folder structure. There's a free preview lesson so you can see exactly what the pace and format feel like before you commit.
Build your knowledge base and harness lesson by lesson
Each workbook lesson gives you a specific, checklist-driven task: migrate a real course's notes, write your first SKILL.md, package five slash commands. No abstract theory, no assumed coding knowledge. You follow the steps, you check your work against the checklist, you move on with something real committed to your repo.
Run a live project through the whole system
In Section 3 you take an actual project from intake through delivery using every piece you've built. By the end you have a working personal AI operating system and a portfolio demo you can show in any interview or on any application.
From scattered lecture notes to a tested study guide skill
The problem: notes everywhere, tool output thin
You ask an AI tool to help you revise inventory models from the past six weeks. It returns a vague summary because your notes are spread across files named 'notes,' 'notes2,' and 'week thing.' The material is there. The tool cannot find it reliably, and if you're honest, neither can you quickly.
Step 1: Migrate and structure the notes
You create a dedicated folder inside your repo's notes directory, rename every file to the weekNN-topic-name.md pattern, and add an index.md listing every week and its topic. You check your work against the 12-point checklist. The tool can now scan file names alone and find week03-inventory-models.md in seconds.
Step 2: Build the study guide skill
You write a SKILL.md inside skills/study-guide specifying exactly how you want a study guide produced: key terms with one-line definitions, five to ten practice questions, a short summary paragraph. You test it on week03-inventory-models.md and review the output critically against your own format.
Step 3: Fix the gap, reuse across subjects
The skill generalises well to your marketing notes but misses discipline-specific formatting for your statistics module. Instead of rewriting the whole skill, you add one targeted instruction for quantitative content. The same skill now works cleanly across both subjects.
Step 4: Package the prompt as a slash command
You save the trigger instruction to .claude/commands/study-guide.md. Next revision session you type /study-guide, point it at any week's notes file, and the correctly formatted output runs without you typing a single additional instruction.
The toolkit you'll build and run in this program
You leave with working assets, not notes.
Real things you can demo in an interview.
A fully structured knowledge base for one real course, organised to the weekNN-topic-name.md standard and checked against a 12-point completion checklist.
A working SKILL.md file for a recurring weekly task, tested across multiple subjects and refined with targeted fixes.
Five slash command files inside .claude/commands, each replacing a prompt you used to retype by hand.
A completed end-to-end project run through your personal AI operating system, documented and ready to use as a portfolio piece.
A course index.md that maps every week and topic at a glance, for you and for any AI tool working inside your repo.
You'll get the most from this if
Students who take notes every week but get unreliable, thin output from AI tools because their files are scattered and inconsistently named.
Early-career professionals who want to show interviewers a working AI system they built themselves.
Anyone who has completed AC 201 and wants to turn their memory file and folder structure into a full, tested personal AI operating system.
People with no coding background who want a clear, checklist-driven path to building something they can demonstrate.
Yearly plan: 14-day keep-the-system guarantee
14-day refund on the yearly plan. Finish the first two modules, and if you haven't run your first live pipeline, take a full refund.
Straight answers before you subscribe
What is a personal AI operating system?
In this course it's your coursework organised as a structured knowledge base, with reusable skills and slash commands built on top of it, all kept in a repo. You save your instructions once instead of re-explaining them every session. You then test the system by running one real project through it from start to finish.
Do I need any coding or technical background to do this course?
None at all. Every lesson is workbook-style with step-by-step instructions and a checklist that defines what 'done' looks like. The files you create are plain markdown, which is text with a few formatting conventions. If you can rename a file and create a folder, you can complete every exercise in this course.
Will this work with my current setup?
The course is built around Claude Code and the repo structure introduced in AC 201. If you're coming from AC 201 you already have the foundation. There's a free preview lesson you can open before buying to check that the environment and pace suit how you work.
What if it's not right for me? Is there a refund?
Refunds depend on the plan. The yearly plan has a 14-day full refund. In India every plan is a one-time pass that isn't refunded, but it never renews without you, and you can try a free lesson before you buy. The refunds page has the full policy.
How does the course stay current as AI tools update?
The curriculum is updated when tools change in ways that affect the hands-on lessons. Where a step might vary by tool version, the lessons tell you to check Claude Code's own current documentation rather than assume the syntax shown is final. Mentor review and daily live sessions are part of the program, so you're not debugging changes alone.
Can I use what I build here in real work or share it with a team?
Yes. Everything you build belongs to you: your knowledge base, your skills, your slash commands and your project artefacts. You can use it in coursework, in a job, or show it as portfolio proof in an application. The course is designed around producing things you can demonstrate to a hiring manager or a curious teammate.