HomeVideos

Anthropic just launched /design for Claude Code (it's awesome)

Now Playing

Anthropic just launched /design for Claude Code (it's awesome)

Transcript

224 segments

0:00

So, on topic just launched an official

0:01

{slash} design skill for Cloud Code. And

0:03

what it basically does is it brings

0:05

Cloud Design's really popular artboard

0:07

workflow into Cloud Code. And you can

0:09

use this now wherever you're using Cloud

0:11

Code, if you're using the terminal or if

0:13

you're using the VS Code extension like

0:15

I do. If you update it and type in

0:16

{slash} design, you should now have this

0:18

skill built into your Cloud Code. And

0:21

you can see for this session I used that

0:22

to make a Robo Nugget's landing page.

0:24

And what it did for us is give us this

0:25

link, which if you head to that, what we

0:27

now have is this editable artifact which

0:30

if we zoom that in so we can see. And it

0:31

created this whole landing page for us

0:33

with a dark and light mode. And

0:35

everything here from the copy to the

0:36

choice of fonts and all the design that

0:39

you are seeing is built from just one

0:41

prompt. And I'll talk more later about

0:43

how I'm able to achieve a design like

0:44

this that doesn't look like it's vibe

0:46

coded at all. But for now, just to show

0:48

you some features of this new {slash}

0:49

design skill, if I go back to canvas,

0:52

the great thing about this artifact that

0:53

Cloud Code made for us is that we can

0:55

freely edit it depending on the designs

0:57

that we want. So, for example, you can

0:59

change the accent colors straight from

1:01

this page. You can adjust the spacing

1:03

between the elements and even the scale

1:05

of the fonts. And of course, you have

1:07

this sidebar at the right, which you

1:09

might be more familiar with if you're

1:10

using Figma. And you can edit that as

1:12

well. So, you can change the fonts, you

1:14

can change the weight of the fonts, and

1:16

so on and so forth. And then of course,

1:17

you can change the text of this as well

1:19

if you wish, which is just a much better

1:21

experience, especially if you are trying

1:23

to just polish a website to get it to

1:25

production. And since this is a Cloud

1:27

artifact, you can actually share this to

1:29

peers or clients as well. So, you can

1:31

see right now only I have access to it,

1:33

but this is quite similar to let's say

1:34

if you're sharing a Google Doc and you

1:36

want anyone with the link to be able to

1:37

access it, then you can just toggle it

1:39

through here and you'll be able to share

1:40

it to whoever needs to review this work.

1:42

But of course, one clear benefit to this

1:44

is that this whole artifact is connected

1:45

to your Cloud Code. So, if you want to

1:47

leave comments on this canvas, you can

1:49

do so just through this button and you

1:50

can just type it in here. Or from that

1:52

same session where you created this, you

1:53

can also just chat with it to apply some

1:56

bigger changes to that artifact that

1:57

you're creating, we'll do in a bit. But,

1:59

there's an obvious question here, right?

2:00

Which is that how is this different from

2:02

Claude design? Well, if you notice this

2:04

whole landing page, I was able to create

2:06

it with only one prompt. So, despite me

2:08

only sending this really simple prompt,

2:10

it was able to capture all our designs,

2:12

all the details here, as well as the

2:14

numbers are also all correct. And the

2:16

reason why that is is because I'm using

2:18

Claude Code, which is connected to my

2:20

entire operating system and context. And

2:22

I teach about this a lot in our

2:23

community and in this channel multiple

2:25

times as well. But, whenever you send a

2:27

prompt to Claude Code, the reality is

2:29

Claude Code actually doesn't work from

2:30

just that one prompt, because it also

2:32

works on your workspace context. And to

2:34

make it simple, the way that I teach

2:36

context and context engineering is just

2:38

through the arms framework. So, if

2:40

you're using Claude Code to its fullest

2:41

potential, then you'll be able to

2:43

connect it to your applications, you'll

2:44

be able to set up your routines. And

2:46

very importantly, the reason why that

2:47

prompt was able to make a pretty good

2:49

landing page from just one prompt is

2:51

because my context has memory connected

2:53

to it, which includes design systems,

2:55

brand books, and business details, as

2:57

well as my own skills. And so, that's

2:59

the big difference of using /design in

3:01

Claude Code versus Claude design.

3:03

Because say if I'm in Claude design and

3:04

I'll ask it to make a Robo Nuggets

3:06

landing page in here, what it's

3:07

essentially going to do first is

3:09

probably ask me some questions, because

3:11

it doesn't really know what Robo Nuggets

3:12

is. It has no memory of my business

3:15

outside of this conversation. So, you

3:17

can see Claude design is asking me what

3:18

Robo Nuggets is, what the visual

3:20

direction is, and you can go through

3:21

this and just answer it so that you can

3:23

give it a bit more guidance. Or, you can

3:25

also just have it decide for you, which

3:26

for the sake of this demo, that's what

3:28

I'll do. And of course, as you would

3:29

expect, what it returned to us is just

3:32

the default fonts that it would use,

3:34

some default colors like this black and

3:36

blue color palette, and all the details

3:37

here are also incorrect. And so, that's

3:39

the difference, because if you send a

3:41

prompt to Claude design, it actually

3:42

can't access any of the context and the

3:45

memory that you've built up. And for the

3:46

most part, each chat session that you

3:48

have with it is self-contained. So, you

3:50

can upload files to it, you can also

3:52

load design systems to it. But, because

3:53

it doesn't really have a memory system,

3:55

most of the time you will need to rework

3:57

that for every project that you do. And

3:59

so, that's a big contrast versus Claude

4:01

Code. And just here I have my second

4:03

brain illustrated for me to be able to

4:06

show it visually. And you can see here

4:08

that this whole workspace, it has

4:09

something like 60,000 files already. And

4:12

what this essentially is is just a

4:14

folder in my machine, which if you're

4:15

using File Explorer, this is how it

4:17

would look. And this has all of those

4:19

memory and all of those skills that I

4:21

was talking about, as well as contacts

4:23

on the applications as well as routines

4:24

that I am running. And by the way, if

4:25

you need a starter pack on setting up

4:27

your own context and your agentic

4:29

operating system, what I did is just

4:30

publish this nine-page guide, which you

4:32

can either read to or just give it to

4:34

your Claude Code to get you started. And

4:36

that's just available down in the pin

4:37

comment below if you need it. And so, to

4:38

give another example of the benefit of

4:40

using Claude Code {slash} design, what

4:42

we can actually do is use {slash} design

4:44

with our own skills. If I send this

4:46

prompt where I'm invoking this skill

4:48

called {slash} generate, which I talked

4:50

about in a previous lesson and I'll just

4:52

link it in this video as well. And

4:53

that's just a skill that connects to all

4:55

of the AI video and image models so that

4:57

I can freely use them on a pay-as-you-go

4:59

basis instead of subscribing to

5:01

something like Hexfield. But, I'm just

5:02

asking Claude Code here to generate a

5:04

relevant video for the site and place it

5:06

as the background. And if I send that

5:08

over, and once that's done, you can see

5:10

here that it generated this dot matrix

5:12

video of a robot. And let's just go

5:14

ahead and actually maximize that so you

5:17

can see. And it was able to generate

5:18

that with the skill that I have in my

5:20

Claude Code context, place it in the

5:22

background as I directed. And so, it's

5:24

just much more flexible because in

5:25

Claude design, even if you check skills

5:27

here in their drop-down, it actually

5:29

doesn't let you create new skills in

5:32

here. And the only ones they have here

5:33

are the default ones that Anthropic

5:35

ships. And so, if you want a bit more

5:36

flexibility, and if you want to use your

5:38

native skills in Claude Code, then using

5:40

{slash} design in Claude Code instead of

5:42

going for Claude design may be for you.

5:45

And finally, as a last example, if you

5:47

want to actually deploy this website,

5:48

meaning publish it on the internet, if

5:50

you try to do that from within Cloud

5:51

Design, so I'm saying here to push this

5:53

to Vercel, which is a well-known

5:55

platform that hosts websites for you for

5:57

free, it's now telling me to do it

5:59

myself, basically. But if I do that in

6:01

Cloud Code, and I'll ask to deploy this

6:02

site to Vercel, you see that it did just

6:05

that, and it's now live in this URL. So,

6:07

it's much more seamless, and really much

6:09

more flexible if you're just using Cloud

6:10

Code. And obviously, because it's Cloud

6:12

Code, you're also just not limited to

6:13

just designing websites. In fact, you

6:15

can probably do all of the templates

6:17

that Cloud Design has here. This one,

6:19

for instance, is a 3D object made with

6:21

that /design skill. You can design email

6:23

templates like this, mockups for mobile

6:25

app designs. And so, pretty much, if

6:27

you're designing something and want to

6:28

use Cloud Code because of the rich

6:30

context that you've built up, it's

6:31

probably a good idea to try out this

6:33

/design skill, especially with all those

6:35

features that I talked about. I hope

6:36

that was useful, and as always, thanks

6:37

for watching until the end, because that

6:39

helps the channel a lot, and I'll see

6:40

you all next time. Cheers.

6:46

>> [music]

Interactive Summary

This video introduces the new '/design' skill for Claude Code, explaining how it enables the creation of editable, high-quality design artifacts directly within the developer's environment. The speaker contrasts this with standard Claude Design by highlighting the power of 'context' and 'memory'—allowing Claude Code to leverage existing brand guidelines, business details, and custom skills to create personalized, accurate designs in one prompt. Furthermore, the video demonstrates the flexibility of Claude Code in integrating custom skills (like AI image/video generation) and seamless deployment directly to platforms like Vercel.

Suggested questions

3 ready-made prompts