← Back
Coming soon
Course / Foundations · selected

Agentic Design Systems: Foundations

A 7-week live course for designers who want their system to ship real code. You'll build tokens, components, and an agent crew that builds, tests, and deploys, while you hold every gate. Zero code experience needed on day 1.

live . 8 weeks· limited seats
Join the waitlistthe full live build ↗
Active cohorts· 01

Pick the intake that fits your calendar.

Same course, same price ladder. Each cohort has its own dates, time, and seats. Full ones take a waitlist, not a payment.

Batch 1coming soon
starts Aug 8, 2026 Every Weekend · 9:00 - 10:30 AM (MMT)
Join the waitlist
The problem· 02

AI has no memory of your decisions.

Every prompt starts from zero. The corner radius you fought for, the contrast pair that passed the audit, the spacing scale your product breathes in: the AI knows none of it. So it guesses. It averages the internet and hands you everyone's product. Which is no one's.

Ask it to design your screen in Figma and it comes back looking finished. Open the layers and there is nothing underneath. No components, no tokens, no rules. Nothing is connected to anything, so nothing can change. Thirty seconds to generate. Weeks to ship. Shipped wrong.

There is a worse version, and it's the popular one: skip design entirely and let AI go straight to code. Now your product's decisions live in files only the AI has read. You want to change a button, you have to ask. You want to know why the blue changed, you have to ask. It is your product, and you are a visitor in it.

A design system turns the file into shared memory. Your decisions live in Figma as tokens, components, and rules, written where both of you can read them. And the loop runs both ways. You retune a token in Figma, and the agent carries it into shipped code. The agent builds a screen in code, and it lands back on your canvas as instances of your components, where you can inspect it, correct it, approve it.

Figma stays the source of truth. Not because it is sacred, but because it is the one place where everything is visible, reachable, and yours. The AI does the labor. You keep the file.

That gap is what this course closes.

Course syllabus· 03

Week by week

Week 01

The ground

  • Day 1 · What a system is. You inherit a real, messy product file and hunt its inconsistencies. Rules that repeat, and why 14 button styles happened to a talented team.
  • Day 2 · Meet the third reader. Designers read your file, developers read your file, and now AI reads your file. How it reads, what it needs, and your first look at AI-written code.
Week 02

The whole machine

show the sessions
  • Day 1 · The full design system ecosystem, from UI kit to component library to the real thing, plus the layer stack that connects Figma to shipped code. You connect your first tools live in class.
  • Day 2 · Onboard your dream team. The pitch that wins adoption: value statement, reading the room, honest proof.
Week 03

Inventory and tokens

show the sessions
  • Day 1 · Interface inventory, design system roadmap, and how to run the build as a project.
  • Day 2 · Design tokens from zero: tiers, aliasing, naming, light and dark. Then you build your system's inventory base in Airtable. Keep that base. It comes back later, and it grows into something bigger than a catalog.
Week 04

Tokens shipped, components built

show the sessions
  • Day 1 · Token implementation, the full pipeline: Figma to JSON to Style Dictionary to Git to Storybook. You watch a color change travel from a Figma variable into live CSS.
  • Day 2 · Components, the brick before the wall. The 5 property types, composable subcomponents, and the AI-readable checklist: naming, tokens, states, documentation. Your components carry their own behavior, so you never teach AI the same interaction twice.
Week 05

From node to crew

show the sessions
  • Day 1 · Node to code. Claude Code reads your Figma component through MCP and builds it, driven by a skill you configure.
  • Day 2 · One agent to a crew. The agent loop, workflows vs agents, orchestrator and workers, and the human gate that keeps you in charge.
Week 06

Mission control and release

show the sessions
  • Day 1 · Run your system from a board. Your Airtable base becomes a control plane: an 11-state component lifecycle, a 4-agent crew (manager, engineer, tester, devops), and 3 gates only you can open.
  • Day 2 · Releasing a design system. Test it 5 ways, audit it with AI through 4 lenses, document it, version it, and publish a real docs site.
Week 07

Apply the system everywhere

show the sessions
  • Day 1 · Design like a pro on your own system. The 4 mistakes that quietly break systems, flow design with prototype linking, frame naming AI can parse, and setting up a real project repo with agents and preflight checks.
  • Day 2 · The crew ships the flow. A flow-identifier agent maps your screens, a parity checker guards your system's boundaries, the crew builds, tests, and you preview, approve, and merge. Then you grade your agents. We close with your capstone brief.
Week 8 · Capstone + certificate

Ship a system, ship a flow.

After the course, you build a small design system from zero on a fresh fictional brief (you pick 1 of 3), then push one full user flow through it: designed, agent-built, tested, gated, merged.

Submit it in Google Classroom and demo it live in a scheduled review: open the board, open the repo, click through the flow. We review every submission by hand, and you earn the TPS certificate for Agentic Design Systems: Foundations on a pass.

What you'll walk away with· 04

By the end of 8 weeks, you can:

Audit any messy product file and turn it into an inventory, a roadmap, and a plan leadership will fund.

Build a 3-tier token architecture with theming modes, wired from Figma all the way into shipped CSS.

Design components that AI reuses instead of reinvents: named, tokenized, documented, with their interactions built in.

Run your system from a live dashboard where AI agents build, test, and deploy components, and nothing moves past your 3 human gates without you.

Ship a full user flow from Figma to working, animated code through your own agent crew, then merge it yourself.

Grade your agents monthly and decide who gets promoted. Yes, really.

And underneath all of it, one skill that outlasts every tool: you'll know how to stay the disciplined input, because AI scales whatever you feed it. Garbage in, garbage scaled.

How the course works· 05

You learn by doing the job, in class.

Live, twice a week

90+ minutes a day. Every session ends with one or more hands-on activity with real time pressure. You learn by doing the job, in class, with me in the room.

You build one thing, all the way through

Every week's exercise carries into the next. The messy file you audit at the start becomes your tokens, then your components, then the system your agent crew runs, until you watch the whole thing live in a browser, built by your own hands.

Zero code on day 1, real code by the end

Every technical concept gets built from the ground up in designer language first.

Tools are set up before class, together

Pre-work guides walk you through every install. If something breaks, we fix it in office hours, never alone at midnight.

What's included· 06

What comes with your seat

contents · 5 items
14 live sessions (7 weeks × 2), plus recordings (Week 8 is project presentation by you)
The full practice project files, week 1 through 7
All prompt files, skills, and agent configs used in class
Capstone review and certificate on pass
Mentorship for certified students
Fit· 07

Both answers save you money.

This course fits you if

You're a UX or product designer with solid design judgment. You know a good interface when you build one.

You've watched AI tools generate messy, inconsistent UI and thought “there has to be a way to control this.”

You want to be the person in your org who runs the design system, and the agents that maintain it.

You've never written production code. That's fine. That's the plan.

Skip this course if

You want a Figma basics class. I'll assume you already use Figma better than most of your leadership.

You want to become a software engineer. You'll read code and direct agents that write it, but engineering is a different course entirely.

You can't attend live. The activities run on real files with real time pressure, and recordings alone won't get you there.

Prerequisites· 08

What you need before day one

Nothing exotic. The one account that costs money is Claude; the Figma plan is free and we help you get it.

Claude Pro plan

An active Claude Pro subscription, for the AI layer and Claude Code.

Figma Education Plan

Free. We help you apply; you provide the Gmail on your Figma account.

8 GB of RAM or more

A computer that can hold Figma and a code editor at once.

Stable internet

Good enough for a live video call, twice a week.

Ambition

You will build a real system, not watch one get built.

Choose your price· 09
Best price
Early bird
Pay before Jul 31, 2026
350,000 MMK
RegularAfter the early bird cutoff400,000 MMK
Group of 2 or moreEnroll and pay together, per seat350,000 MMK
TPS AlumniCompleted a course by The Productive Schedule350,000 MMK

One discount at a time. If two could apply, you get the lower price. They don't stack.

How to pay. Bank transfer: KBZ, CB, or UAB. Mobile wallet: KBZPay, Wave Pay, or UAB Pay. After you pay, upload a screenshot or photo in your application. We verify by hand and hold your seat until it clears.
FAQ· 5 nodes

Asked before you asked.

I can't code at all. Really, at all. Will I survive?
You're the exact student this was built for. Every technical concept starts from zero, in designer language, before it touches a terminal. By week 5 you'll be reading AI-written code and knowing when it's wrong.
Do I need a powerful computer?
A laptop that runs Figma comfortably is enough. The pre-work guide covers every install, and we test your setup before the technical weeks start.
What if I miss a session?
Recordings go up on the portal. But the activities are live for a reason, so treat recordings as backup, and plan to attend.
How much time outside class?
Plan for 2 to 3 hours a week beyond the sessions. Portal quizzes are short; the real time goes into practice.
Is the certificate automatic?
It's earned. You pass the capstone rubric, you get the certificate. That's what makes it worth putting on your profile.
Join waitlist· 06

Registration opens soon.

You are early. Join the waitlist and we will reach out the moment a seat opens or registration begins.

Pick your country, then the number without the leading zero