Workshops: Agentic Coding for Roles & Industries
Coding Agents for UX/UI Designers: From Design to Working Prototype
Designers no longer have to stop at clickable mock-ups. With coding agents, UX and UI designers can build working prototypes with real states, content and components, and test them with users. This beginner-friendly workshop shows the path from design to running code, and how to hand it over so developers actually want to build on it.
Who is this workshop for?
- UX and UI designers with little or no coding experience
- Product designers working closely with development teams
- UX researchers who need realistic prototypes for usability tests
- Design system and DesignOps teams
- Design leads rethinking how design and engineering work together
What you will take away
- Turn a screen design into a responsive, working prototype with a coding agent, step by step.
- Use existing components and design tokens instead of letting the agent invent new styles.
- Build realistic states into prototypes: loading, empty, error, long text and different screen sizes.
- Check accessibility basics such as contrast, focus order and labels directly in code.
- Hand over prototypes in a form developers can review, reuse or consciously discard.
Agenda
Module 1
Coding agents for designers
- What Claude Code, Cursor or OpenAI Codex do, and how they differ from app builders such as v0, Lovable or Bolt
- Terminal and editor basics without fear
- Setting up a safe prototype project
Module 2
From design to code
- Describing layout, hierarchy and behaviour so an agent understands them
- Working from screenshots and design files, including Figma's MCP server where your setup allows it
- Exercise: build a screen from your own design
Module 3
Real components, real states
- Using the team's component library and design tokens
- Loading, empty and error states with realistic sample data
- Responsive behaviour and micro-interactions
Module 4
Quality you can see
- Comparing the result with the design and fixing deviations
- Accessibility checks: contrast, keyboard, screen reader labels
- Letting the agent explain the code it wrote
Module 5
Working with developers
- Prototype, spike or production code: agreeing on the purpose up front
- Branches, pull requests and small design fixes in the real codebase
- A handover checklist both sides can live with
Why design engineering now
The gap between a static design and a working interface costs time: details get lost in handover, edge cases surface late and user tests run on prototypes that behave nothing like the product. Coding agents shrink that gap. Designers can explore interactions in real code and show developers exactly what they mean.
That does not turn designers into developers. It gives them a new medium for exploration and a shared language with engineering.
Clear boundaries with engineering
Agent-built prototypes are easy to produce and easy to misjudge. We clarify what belongs in a prototype and how to avoid the classic misunderstanding that a convincing demo is almost finished.
- Prototypes run on sample data, never on customer data
- No secrets or production credentials in prototype projects
- Changes to product code only via pull requests with developer review
- Production readiness is decided by the engineering team
Bring your own designs
Participants work on their own screens and flows; if designs are confidential, we use a sandbox project. Remote or on-site, in German or English, with neooutput AI Code Engineers and AI Trainers who know both sides of the handover.
Frequently asked questions
Do I need to know how to code?
No. We start with terminal and editor basics. Curiosity and a willingness to read some code are enough: the agent writes most of it, and we show you how to follow what it did.
Why not just use an AI app builder?
App builders such as v0, Lovable or Bolt are great for quick standalone ideas, and we show where they fit. To prototype inside your team's real codebase with its components, a coding agent like Claude Code or Cursor is usually the better tool.
Will developers rebuild everything anyway?
Sometimes, and that is fine if it was agreed. Often, though, components, states and interaction details can be reused directly. The handover rules from the workshop make that decision explicit.
Workshop
Get in touch
Want your designers to show working ideas instead of describing them?
Tell us roughly how many people will join and pick dates that work – we will get back to you within 24 hours with a proposal for content, format and schedule.
Prefer to talk first?
15 minutes, free and without obligation – with our AI Trainers and AI Code Engineers.
Book a call for free (opens in new tab) +49 761 519 751 50 (24/7)Request a training / workshop
Workshop: Coding Agents for UX/UI Designers: From Design to Working Prototype · 1 day
More workshops
- Workshops: Agentic Coding for Roles & IndustriesAgentic Coding for Startup Engineering Teams: Fast, Not Fragile
- Workshops: Agentic Coding for Roles & IndustriesRolling Out Coding Agents Org-Wide: Workshop for Platform & DevEx
- Workshops: Agentic Coding for Roles & IndustriesMeasuring the Impact of Agentic Coding: DORA & SPACE Workshop
- Workshops: Agentic Coding for Roles & IndustriesAgentic Coding in Banks & Insurers: Workshop under DORA and BaFin
- Workshops: Agentic Coding for Roles & IndustriesAgentic Coding for Medical Device Software: IEC 62304 & MDR Workshop
- Workshops: Agentic Coding by Tech StackElectron & Tauri Desktop Apps with AI Coding Agents: Workshop
