Skip to main content
Workshop

AI for Designers & Non-Developers

Claude Code in practice – from idea to prototype without writing a line of code yourself.

March 2, 2026 Adeprimo
AI Claude Code Design

Agenda

2 hours – from fundamentals to practical demos

13:00
10 min

Intro & Icebreaker

Who are we? Why should designers care about AI? The CLI monster – don't be afraid of the terminal!

13:10
40 min

Fundamentals

Terminal, Claude Code, IDE, Git, Figma integration, Markdown

LLMsTokensContext EngineeringMCP ServersSkillsAgents
13:50
10 min

Break

Stretch, coffee & open discussion

14:00
50 min

Practical Workshop

Live demos – from voice prompting to designing in Figma via the terminal.

14:50
10 min

Closing & Discussion

How can I use this in my role? Next steps, accounts, teaser for the "Getting Things Done" series.

Workflow & Pro Tips

From the Claude Code team and Boris Cherney – the creator of Claude Code

1

Explore

Understand the codebase and problem

2

Plan

Let Claude suggest a plan

3

Implement

Build with Claude Code

4

Commit

Save and version

Boris Cherney's setup

The creator of Claude Code runs 5 Claude instances in parallel in the terminal, numbered for easy navigation. Plus 5–10 "background Claudes" on claude.ai. He alternates between exploring, planning, and implementing.

& – Hand off local sessions to the web
Use multiple copies of repos locally or git worktrees for parallel work

Ghostty CLI

The Claude Code team likes Ghostty as terminal. Color-code tabs to distinguish different worktrees.

Voice Dictation (STT)

You speak 2–3x faster than you type. Voice dictation gives better prompts and therefore better results.

Context is everything

The right context is the most important thing for good results. The fuller the context window, the worse the results. Clear often with /clear.

Be specific

  • -Reference files with @
  • -Give URL to spec/info you want in your context
  • -Use /permissions to approve common domains and MCP tools

Use subagents

Subagents save context – they do things and report back their findings. Perfect for exploring, designing or analyzing without filling the context window.

Let Claude see its results

Use browser MCP, Skills or screenshots so Claude can review its own work and iterate toward better results.

Quick Guide

The cheat sheet – take it home after the workshop

Start Claude Code

claude# Start in current folder
claude "Describe task"# Start with a prompt

Terminal Basics

pwd# Where am I?
ls# What's here?
cd folder-name# Enter a folder
cd ..# Go up one level
mkdir new-folder# Create a new folder
open .# Open folder in Finder

Common Commands

/helpShow help
/clearClear conversation
/initCreate CLAUDE.md
/modelSwitch model
/contextShow context usage
/mcpManage MCP servers
/compactCompress conversation
Shift+TabToggle auto-accept
Shift+Tab x2Plan mode
EscStop Claude
Esc x2Undo / rewind

Good Prompts

Prototype

"Create a responsive landing page for a coffee roastery with a hero, three USP cards and a CTA button."

Review

"Review the accessibility of this page according to WCAG 2.2 AA. Give the top 5 issues."

Personas

"Create 3 personas for a booking app. Include needs, pain points and a user journey."

Tips

  • Be specific – "Blue header, white background, green CTA" instead of "make a nice page"
  • Iterate – Say "change the button to red" instead of starting over
  • CLAUDE.md – Write your preferences, Claude remembers them next time
  • Skills – Create custom /commands for tasks you do often

Book workshop

Claude Code in practice – from idea to prototype without writing a line of code yourself.

Book workshop