← Back
Coming soon · by application
Course / Sprint · screened

Agentic Design Systems: Sprint

Advanced your design system workflows by introducing agentic experience. Systems are more powerful with agents crew properly set up. Stay relif and stay up to date latest agentic workflows.

live . 5 days· starts Aug 17, 2026· limited seats
Join the waitlistadvanced segment only ↗
Apply and earn a free Figma Education Plan.

We are a Figma trusted partner. Join, give us the Gmail on your Figma account, and we help you apply for the free plan.

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 17, 2026 Mon, Tue, Wed, Thu, Fri · 7:30 - 9:30 PM (MMT)
Join the waitlist
The problem· 02

You already built the system. AI still can't run it.

You have tokens. You have components. You have the discipline. That part is not the gap anymore.

The gap is speed. Every month another tool claims it can design or code your product for you, and every month it ships something that looks finished and holds nothing underneath: no real components, no tokens, no rules an agent can actually follow. You already know a system that holds from one that just looks fine. Most AI tools still don't.

Wiring your system into an agentic workflow that runs both ways between Figma and shipped code, is its own discipline. It is not a week of prompting a chatbot.

That's the five days: not learning design systems, bridging the one you already have into the agentic layer, fast enough to matter and safe enough to defend to your team.

Course syllabus· 03

Day by day

Day 01

Agentic foundations + make Figma an AI's home

  • Failure-first hook (class-list pile) → agent vs model vs skill vs MCP (define each) → how MCP reads names + descriptions + tokens → AI-readable checklist (naming, tokens, states, docs) → ecosystem map as a progressive build, cargo+driver on every road
Day 02

Build the system in design + code (one skill, one agent)

show the sessions
  • Walk the pre-built Figma demo 🏝️ (don't build it) → repo setup as step cards (1 action + 1 checkpoint) → tools.md/CLAUDE.md split → token pipeline (Style Dictionary) → node→code → introduce the engineer agent (reads / writes)
Day 03

The crew and the registry (Mission Control)

show the sessions
  • One agent → a crew (manager, engineer, AgentEagle, devops — define each) → registry as control plane, read first every run → two-lane rule (only manager writes Development) → 11-state machine, progressive build, legal moves only → manager verifies process not quality → crew↔registry diagram, cargo+driver
Day 04

Release your system

show the sessions
  • Release path staging→prod → devops agent (writes links, never Development) → three human gates as evaluation checkpoints (judge, don't rubber-stamp) → publish: Storybook evidence + Astro Starlight docs → honesty slide: publishing ≠ adoption
Day 05

Apply the system everywhere

show the sessions
  • Design like a pro inside your own rails → crew ships the flow (you gate) → parity/drift check (shipped vs designed) → decision: extend the system vs compose from existing → live demo format
Project + certificate

Ship a project, earn the certificate.

You close Sprint by shipping the everyday assignments the walk-away list already promises: your system, wired into code, with an agent workflow running through it.

Submit it in Google Classroom. We review every submission by hand, and you get the certificate for Agentic Design Systems: Sprint on a pass.

What you walk away with· 04

Five things you leave with

A design system built on tokens and atomic components, structured so it scales.

The same system wired into code: Claude Code, agents, skills, and automated workflows.

A live web project built from your own system.

A GitHub workflow you can actually hold: branching, staging, and main.

The judgment to tell a system that holds from one that looks fine and breaks.

How the course works· 05

Four days, straight through.

Live, four days straight

Four consecutive days, live online. No week off to lose momentum, no gap between sessions before you apply what you just learned.

You bring the system, we bring the agents

You arrive with tokens and components already built. Every session wires more of the agentic layer into the system you walk in with.

Straight to the advanced material

No foundations detour. Day one assumes you already know what a token is; we start where Foundations ends.

Recorded, so nothing is lost to a clash

Every session is recorded for enrolled students, in case a meeting collides with a live day.

What's included· 06

What comes with your seat

contents · 4 items
5 live sessions (one per day), plus recordings
The practice project files for all 5 days
All prompt files, skills, and agent configs used in class
Everyday assignments review and certificate on submission
Fit· 07

Already building? This is the fast lane.

Fits you if

You already build with tokens, components, and some auto-layout discipline. You want the AI layer added to what you have, not a rebuild from zero.

You're a working designer, or an alumni of The Productive Schedule.

You can clear four consecutive days, fully live, no half-attendance.

Skip this course if

You're new to design systems entirely. Start with Foundations; Sprint assumes you've already built with tokens and components.

You want to learn at your own pace instead of four fixed live days. Core is the self-paced base layer.

You haven't built anything with variants or auto-layout yet. Sprint has no time to teach that from zero.

Eligibility· 08

To be accepted, you show three things

Sprint moves fast because it assumes you already have the base.

Figma skill
What proves it

A Figma file or components you built: auto-layout, variants, and some token use

Foundational knowledge
What proves it

You already work with tokens, components, and atomic structure

Experience
What proves it

An established, working designer. [X]+ years, or a portfolio that shows it

Completed a course by The Productive Schedule? Your certificate is your qualification: upload it in place of the proof, and the alumni price is yours. Early bird stays with first-time students.
Prerequisites· 09

What you need before day one

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 four full live days on video.

Choose your price· 10
Best price
Early Bird
Pay before Jul 31, 2026
200,000 MMK
RegularAfter the early bird cutoff250,000 MMK
Group of 2 or moreEnroll and pay together, per seat200,000 MMK
TPS AlumniCompleted a course by The Productive Schedule200,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. Details arrive with your enrollment invite, after you're accepted. After you pay, upload a screenshot or photo. We verify by hand and confirm your seat.
FAQ· 4 nodes

Asked before you asked.

Do I need to know code?
No. The full course starts from foundations. You will touch code through Claude and agents, guided step by step.
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 do I need before day one?
A Figma Education Plan account. We help you apply if you don't have one.
Is there a certificate after a course ends?
Yes, you will receive a certificate by the end of this class if you submit everyday assignment.
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