Cohort
02
Interface Anatomy
Learn to build a design system from scratch: design to code to Storybook, then AI coding agents and a modern development workflow.
Closed
10 of 150 seats remaining
12 weeks
Duration
Starts
₹15,000
Investment
Cohort
02
Interface Anatomy
Learn to build a design system from scratch: design to code to Storybook, then AI coding agents and a modern development workflow.
Closed
10 of 150 seats remaining
12 weeks
Duration
Starts
₹15,000
Investment
Cohort
02
Interface Anatomy
Learn to build a design system from scratch: design to code to Storybook, then AI coding agents and a modern development workflow.
Closed
10 of 150 seats remaining
12 weeks
Duration
Starts
₹15,000
Investment
Case Study Craft
•
13 Copywriting Frameworks
•
4 Portfolio Case Studies
•
Everyday Resources
•
1:1 Live Sessions
•
24/7 Mentor Guidance
•
Case Study Craft
•
13 Copywriting Frameworks
•
4 Portfolio Case Studies
•
1:1 Live Sessions
•
Everyday Resources
•
Is this curriculum for you?
Do you also think like this?
BEGINNER
“I’ve watched 200 tutorials. I still don’t know where a real product starts.”
You’ll start with one brief, one user and one metric, and finish with a product you’ve shipped. No more tutorial loops.
1 YEAR
“My work looks fine, but I can’t explain a single decision I made.”
You’ll tie every screen to a metric and a business reason, then defend your decisions live in five minutes.
3 YEARS
“I’ve been ‘almost senior’ for 8 months. Nobody tells me what’s missing.”
You’ll learn what seniors are actually hired for: North Star metrics, unit economics, and finding the problem before anyone hands you a brief.
5 YEARS
“AI does in 10 minutes what takes me a day. I don’t know what my value is anymore.”
You’ll own the one thing AI can’t do: decide what’s worth building, and prove it with numbers.
Is this curriculum for you?
Do you also think like this?
BEGINNER
“I’ve watched 200 tutorials. I still don’t know where a real product starts.”
You’ll start with one brief, one user and one metric, and finish with a product you’ve shipped. No more tutorial loops.
1 YEAR
“My work looks fine, but I can’t explain a single decision I made.”
You’ll tie every screen to a metric and a business reason, then defend your decisions live in five minutes.
3 YEARS
“I’ve been ‘almost senior’ for 8 months. Nobody tells me what’s missing.”
You’ll learn what seniors are actually hired for: North Star metrics, unit economics, and finding the problem before anyone hands you a brief.
5 YEARS
“AI does in 10 minutes what takes me a day. I don’t know what my value is anymore.”
You’ll own the one thing AI can’t do: decide what’s worth building, and prove it with numbers.
Is this curriculum for you?
Do you also think like this?
BEGINNER
“I’ve watched 200 tutorials. I still don’t know where a real product starts.”
You’ll start with one brief, one user and one metric, and finish with a product you’ve shipped. No more tutorial loops.
1 YEAR
“My work looks fine, but I can’t explain a single decision I made.”
You’ll tie every screen to a metric and a business reason, then defend your decisions live in five minutes.
3 YEARS
“I’ve been ‘almost senior’ for 8 months. Nobody tells me what’s missing.”
You’ll learn what seniors are actually hired for: North Star metrics, unit economics, and finding the problem before anyone hands you a brief.
5 YEARS
“AI does in 10 minutes what takes me a day. I don’t know what my value is anymore.”
You’ll own the one thing AI can’t do: decide what’s worth building, and prove it with numbers.
Why your work is not speaking
Why isn’t your work
getting you hired?
After reviewing thousands of portfolios and years of hiring, Rajat Patel sees the same four patterns. Strong designers get filtered out before anyone sees how good they really are, and none of the reasons are about design skill.
01
You can’t explain your decisions
The work is solid but when someone asks “why did you do it this way?” you freeze, ramble, or apologise. Companies hire the designer who can defend the work, not just the one who made it look good.
02
You’re making screens, not systems
Every project is a one-off. Nothing is reusable, scalable, or documented. Senior designers think in components, tokens, and rules, not individual frames. That gap is visible in 30 seconds.
03
Your portfolio has no architecture
Projects stacked in random order, no hierarchy, no story. A recruiter spends eight seconds before deciding whether to keep reading. Right now, nothing tells them where to look.
04
You’re still “junior” after years
You’ve been shipping work for 2–3 years and you’re still not levelling up. The issue isn’t output. It’s the layer above it: how you frame problems, structure systems, and communicate at a senior level.
Why your work is not speaking
Why isn’t your work
getting you hired?
After reviewing thousands of portfolios and years of hiring, Rajat Patel sees the same four patterns. Strong designers get filtered out before anyone sees how good they really are, and none of the reasons are about design skill.
01
You can’t explain your decisions
The work is solid but when someone asks “why did you do it this way?” you freeze, ramble, or apologise. Companies hire the designer who can defend the work, not just the one who made it look good.
02
You’re making screens, not systems
Every project is a one-off. Nothing is reusable, scalable, or documented. Senior designers think in components, tokens, and rules, not individual frames. That gap is visible in 30 seconds.
03
Your portfolio has no architecture
Projects stacked in random order, no hierarchy, no story. A recruiter spends eight seconds before deciding whether to keep reading. Right now, nothing tells them where to look.
04
You’re still “junior” after years
You’ve been shipping work for 2–3 years and you’re still not levelling up. The issue isn’t output. It’s the layer above it: how you frame problems, structure systems, and communicate at a senior level.
Why your work is not speaking
Why isn’t your work
getting you hired?
After reviewing thousands of portfolios and years of hiring, Rajat Patel sees the same four patterns. Strong designers get filtered out before anyone sees how good they really are, and none of the reasons are about design skill.
01
You can’t explain your decisions
The work is solid but when someone asks “why did you do it this way?” you freeze, ramble, or apologise. Companies hire the designer who can defend the work, not just the one who made it look good.
02
You’re making screens, not systems
Every project is a one-off. Nothing is reusable, scalable, or documented. Senior designers think in components, tokens, and rules, not individual frames. That gap is visible in 30 seconds.
03
Your portfolio has no architecture
Projects stacked in random order, no hierarchy, no story. A recruiter spends eight seconds before deciding whether to keep reading. Right now, nothing tells them where to look.
04
You’re still “junior” after years
You’ve been shipping work for 2–3 years and you’re still not levelling up. The issue isn’t output. It’s the layer above it: how you frame problems, structure systems, and communicate at a senior level.
What exactly will you learn?
12 weeks
One hireable designer.
Every stage ends with something real: built by you, documented by you, defended by you. You leave with a portfolio that speaks before you do.
Week 01–02
Foundations: design systems as infrastructure
You start with what a design system actually is and why most of them fail. Then you rebuild a real product surface so it holds up on desktop, tablet, and mobile.
Style guide vs component library vs design system
System boundaries: foundations, primitives, components, patterns, templates
Figma file architecture, naming, and documentation
Advanced Auto Layout, grids, spacing, and responsive components
Output: System architecture, capstone direction, and a responsive product shell
Week 03–04
Component systems
You build the foundation layer first, then the components that sit on top of it. The stage ends with a sprint: about 5 complex and 5 to 7 simple components.
Type scales, colour, spacing, radius, elevation, and motion
Figma Variables, collections, and modes
Component anatomy, variants, properties, slots, and instance swapping
States, content extremes, and when not to componentise
Milestone 1: Figma System v1
Week 05–06
System infrastructure: tokens, accessibility, and docs
You turn your foundations into a three-tier token architecture, then make the system something other designers can trust and use.
Primitive, semantic, and component tokens
Dark mode, multi-theme, and multi-brand thinking
WCAG basics: contrast, keyboard, focus, and target size
Documentation, decision notes, and critique that returns PASS / FAIL / CAN’T TELL
Milestone 2: Production-ready Figma system
Week 07–08
Operating a design system
Building the system is half the job. Here you learn how teams run it, grow it, and get people to use it.
Strategy, scope, and maturity
Centralised vs federated teams, and contribution models
Governance, versioning, deprecation, and migration
Adoption metrics, system health, ROI, and audits of mature systems
Live case: Solve an adoption problem in pods and defend your strategy.
Milestone 3: System strategy + audit
Week 09–10
Design engineering
You learn code through the system you already designed, not generic programming. Then you get that system running in code.
HTML, CSS, DOM, and the React mental model
Components, props, state, and TypeScript vocabulary
Git, GitHub, and repository anatomy
Figma Variables → CSS variables → coded components → Storybook → deployment
Milestone 4: Design system running in code
Week 11–12
Agentic product development
You use coding agents to build and ship a real product on your own system. When the product exposes a weak spot, you fix the system instead of patching screens.
Coding agents, repository context, and context engineering
AGENTS.md / CLAUDE.md-style instruction files
Brief → Plan → Agents → Code → Test → Visual QA → Fix → Deploy
Loading, empty, and error states, accessibility, and consistency
Milestone 5: A working product, presented at Demo Day
What exactly will you learn?
12 weeks
One hireable designer.
Every stage ends with something real: built by you, documented by you, defended by you. You leave with a portfolio that speaks before you do.
Week 01–02
Foundations: design systems as infrastructure
You start with what a design system actually is and why most of them fail. Then you rebuild a real product surface so it holds up on desktop, tablet, and mobile.
Style guide vs component library vs design system
System boundaries: foundations, primitives, components, patterns, templates
Figma file architecture, naming, and documentation
Advanced Auto Layout, grids, spacing, and responsive components
Output: System architecture, capstone direction, and a responsive product shell
Week 03–04
Component systems
You build the foundation layer first, then the components that sit on top of it. The stage ends with a sprint: about 5 complex and 5 to 7 simple components.
Type scales, colour, spacing, radius, elevation, and motion
Figma Variables, collections, and modes
Component anatomy, variants, properties, slots, and instance swapping
States, content extremes, and when not to componentise
Milestone 1: Figma System v1
Week 05–06
System infrastructure: tokens, accessibility, and docs
You turn your foundations into a three-tier token architecture, then make the system something other designers can trust and use.
Primitive, semantic, and component tokens
Dark mode, multi-theme, and multi-brand thinking
WCAG basics: contrast, keyboard, focus, and target size
Documentation, decision notes, and critique that returns PASS / FAIL / CAN’T TELL
Milestone 2: Production-ready Figma system
Week 07–08
Operating a design system
Building the system is half the job. Here you learn how teams run it, grow it, and get people to use it.
Strategy, scope, and maturity
Centralised vs federated teams, and contribution models
Governance, versioning, deprecation, and migration
Adoption metrics, system health, ROI, and audits of mature systems
Live case: Solve an adoption problem in pods and defend your strategy.
Milestone 3: System strategy + audit
Week 09–10
Design engineering
You learn code through the system you already designed, not generic programming. Then you get that system running in code.
HTML, CSS, DOM, and the React mental model
Components, props, state, and TypeScript vocabulary
Git, GitHub, and repository anatomy
Figma Variables → CSS variables → coded components → Storybook → deployment
Milestone 4: Design system running in code
Week 11–12
Agentic product development
You use coding agents to build and ship a real product on your own system. When the product exposes a weak spot, you fix the system instead of patching screens.
Coding agents, repository context, and context engineering
AGENTS.md / CLAUDE.md-style instruction files
Brief → Plan → Agents → Code → Test → Visual QA → Fix → Deploy
Loading, empty, and error states, accessibility, and consistency
Milestone 5: A working product, presented at Demo Day
What exactly will you learn?
12 weeks
One hireable designer.
Every stage ends with something real: built by you, documented by you, defended by you. You leave with a portfolio that speaks before you do.
Week 01–02
Foundations: design systems as infrastructure
You start with what a design system actually is and why most of them fail. Then you rebuild a real product surface so it holds up on desktop, tablet, and mobile.
Style guide vs component library vs design system
System boundaries: foundations, primitives, components, patterns, templates
Figma file architecture, naming, and documentation
Advanced Auto Layout, grids, spacing, and responsive components
Output: System architecture, capstone direction, and a responsive product shell
Week 03–04
Component systems
You build the foundation layer first, then the components that sit on top of it. The stage ends with a sprint: about 5 complex and 5 to 7 simple components.
Type scales, colour, spacing, radius, elevation, and motion
Figma Variables, collections, and modes
Component anatomy, variants, properties, slots, and instance swapping
States, content extremes, and when not to componentise
Milestone 1: Figma System v1
Week 05–06
System infrastructure: tokens, accessibility, and docs
You turn your foundations into a three-tier token architecture, then make the system something other designers can trust and use.
Primitive, semantic, and component tokens
Dark mode, multi-theme, and multi-brand thinking
WCAG basics: contrast, keyboard, focus, and target size
Documentation, decision notes, and critique that returns PASS / FAIL / CAN’T TELL
Milestone 2: Production-ready Figma system
Week 07–08
Operating a design system
Building the system is half the job. Here you learn how teams run it, grow it, and get people to use it.
Strategy, scope, and maturity
Centralised vs federated teams, and contribution models
Governance, versioning, deprecation, and migration
Adoption metrics, system health, ROI, and audits of mature systems
Live case: Solve an adoption problem in pods and defend your strategy.
Milestone 3: System strategy + audit
Week 09–10
Design engineering
You learn code through the system you already designed, not generic programming. Then you get that system running in code.
HTML, CSS, DOM, and the React mental model
Components, props, state, and TypeScript vocabulary
Git, GitHub, and repository anatomy
Figma Variables → CSS variables → coded components → Storybook → deployment
Milestone 4: Design system running in code
Week 11–12
Agentic product development
You use coding agents to build and ship a real product on your own system. When the product exposes a weak spot, you fix the system instead of patching screens.
Coding agents, repository context, and context engineering
AGENTS.md / CLAUDE.md-style instruction files
Brief → Plan → Agents → Code → Test → Visual QA → Fix → Deploy
Loading, empty, and error states, accessibility, and consistency
Milestone 5: A working product, presented at Demo Day
What you take home
Every week ends with
a working Figma file.
Each pack is a ready-to-use Figma template, not slides, not PDFs. Files you drop straight into your next project and use immediately.
Week 01–02
Thinking Kit
Tools for reading a problem before touching Figma
Problem Framework Template
System Map Canvas
Decision Log
Week 03–04
Foundations Kit
Build your token and type system from scratch
Token Library Starter
System Map Canvas
Decision Log
Week 05–06
Component Kit
Build accessible components on a three-tier token system
Component Anatomy Guide
Three-Tier Token Map
Accessibility Checklist
Week 07–08
Patterns Library
Reusable patterns and the rules that keep a system healthy as it grows
Pattern Library Template
Contribution & Governance Playbook
System Health Audit
Week 09–10
Code Kit
Take your system from Figma to production code
Variables-to-CSS Mapping Sheet
Component Handoff Spec
Storybook Documentation Template
Week 11–12
Defence Kit
Ship a product on your system, then defend it at Demo Day
Agent Brief Template
Visual QA Checklist
Demo Day Presentation Deck
What you take home
Every week ends with
a working Figma file.
Each pack is a ready-to-use Figma template, not slides, not PDFs. Files you drop straight into your next project and use immediately.
Week 01–02
Thinking Kit
Tools for reading a problem before touching Figma
Problem Framework Template
System Map Canvas
Decision Log
Week 03–04
Foundations Kit
Build your token and type system from scratch
Token Library Starter
System Map Canvas
Decision Log
Week 05–06
Component Kit
Build accessible components on a three-tier token system
Component Anatomy Guide
Three-Tier Token Map
Accessibility Checklist
Week 07–08
Patterns Library
Reusable patterns and the rules that keep a system healthy as it grows
Pattern Library Template
Contribution & Governance Playbook
System Health Audit
Week 09–10
Code Kit
Take your system from Figma to production code
Variables-to-CSS Mapping Sheet
Component Handoff Spec
Storybook Documentation Template
Week 11–12
Defence Kit
Ship a product on your system, then defend it at Demo Day
Agent Brief Template
Visual QA Checklist
Demo Day Presentation Deck
What you take home
Every week ends with
a working Figma file.
Each pack is a ready-to-use Figma template, not slides, not PDFs. Files you drop straight into your next project and use immediately.
Week 01–02
Thinking Kit
Tools for reading a problem before touching Figma
Problem Framework Template
System Map Canvas
Decision Log
Week 03–04
Foundations Kit
Build your token and type system from scratch
Token Library Starter
System Map Canvas
Decision Log
Week 05–06
Component Kit
Build accessible components on a three-tier token system
Component Anatomy Guide
Three-Tier Token Map
Accessibility Checklist
Week 07–08
Patterns Library
Reusable patterns and the rules that keep a system healthy as it grows
Pattern Library Template
Contribution & Governance Playbook
System Health Audit
Week 09–10
Code Kit
Take your system from Figma to production code
Variables-to-CSS Mapping Sheet
Component Handoff Spec
Storybook Documentation Template
Week 11–12
Defence Kit
Ship a product on your system, then defend it at Demo Day
Agent Brief Template
Visual QA Checklist
Demo Day Presentation Deck
Rajat Patel will be
teaching you this course.
Self-taught. No degree. 10 years at PhonePe, Airtel, and Zepto, most recently as Design Manager, sitting on the other side of the table deciding which portfolios moved forward. He’s reviewed thousands of them. Interface Anatomy is everything he wishes those candidates had known.
I’ll show you how to think, not just what to make
I’ll review your work personally, not delegate it
I’ll tell you the truth about your work, not what you want to hear
500+
Designers Trained
4.8
Rated by students
5000+
Students Mentored
Rajat Patel will be
teaching you this course.
Self-taught. No degree. 10 years at PhonePe, Airtel, and Zepto, most recently as Design Manager, sitting on the other side of the table deciding which portfolios moved forward. He’s reviewed thousands of them. Interface Anatomy is everything he wishes those candidates had known.
I’ll show you how to think, not just what to make
I’ll review your work personally, not delegate it
I’ll tell you the truth about your work, not what you want to hear
500+
Designers Trained
4.8
Rated by students
5000+
Students Mentored
Rajat Patel will be
teaching you this course.
Self-taught. No degree. 10 years at PhonePe, Airtel, and Zepto, most recently as Design Manager, sitting on the other side of the table deciding which portfolios moved forward. He’s reviewed thousands of them. Interface Anatomy is everything he wishes those candidates had known.
I’ll show you how to think, not just what to make
I’ll review your work personally, not delegate it
I’ll tell you the truth about your work, not what you want to hear
500+
Designers Trained
4.8
Rated by students
5000+
Students Mentored
One serious cohort. Three ways in.
One serious cohort. Three ways in.
Anatomy Base
Recorded
Systems, Foundations & Component Architecture
Join waitlist for next cohort
Foundation
Anatomy Base
Recorded
Systems, Foundations & Component Architecture
Join waitlist for next cohort
Foundation
Anatomy Pro
07 Weeks
Design, Systemise, Engineer, Ship Complete Transformation.
Join waitlist for next cohort
Popular
Anatomy Pro
07 Weeks
Design, Systemise, Engineer, Ship Complete Transformation.
Join waitlist for next cohort
Popular
Anatomy Elite
12 Weeks
With 90 Days of Personalised Training, Selection, and Placement training
Join waitlist for next cohort
Personalised
Anatomy Elite
12 Weeks
With 90 Days of Personalised Training, Selection, and Placement training
Join waitlist for next cohort
Personalised
Frequently Asked Questions
Is this for beginners or experienced designers?
Both. We start with fundamentals everyone needs, then branch into project work matched to your level, so beginners aren't lost and experienced designers aren't bored.
Can we get a refund for the course we bought?
Students can request a refund within 15 days of the course start date. Refund requests submitted after this 15-day window will not be processed.
I have a full-time job. Can I keep up?
Yes. The curriculum is self-paced with weekly milestones, not fixed class times, so you can work around a 9-to-5 as long as you show up consistently.
Frequently Asked Questions
Is this for beginners or experienced designers?
Both. We start with fundamentals everyone needs, then branch into project work matched to your level, so beginners aren't lost and experienced designers aren't bored.
Can we get a refund for the course we bought?
Students can request a refund within 15 days of the course start date. Refund requests submitted after this 15-day window will not be processed.
I have a full-time job. Can I keep up?
Yes. The curriculum is self-paced with weekly milestones, not fixed class times, so you can work around a 9-to-5 as long as you show up consistently.
Frequently Asked Questions
Is this for beginners or experienced designers?
Both. We start with fundamentals everyone needs, then branch into project work matched to your level, so beginners aren't lost and experienced designers aren't bored.
Can we get a refund for the course we bought?
Students can request a refund within 15 days of the course start date. Refund requests submitted after this 15-day window will not be processed.
I have a full-time job. Can I keep up?
Yes. The curriculum is self-paced with weekly milestones, not fixed class times, so you can work around a 9-to-5 as long as you show up consistently.
Molades
© 2026 Molades. All rights reserved.
Molades
© 2026 Molades. All rights reserved.
Molades
© 2026 Molades. All rights reserved.