쉐도잉 연습: Full Claude Guide: Beginner to Pro in Under 15 Minutes - 영상으로 영어 말하기 배우기

I've spent over 1,000 hours inside Claude, and I use it every single day to build tools, run workflows, and even launch million-dollar companies.

And look, you might feel super productive using Claude right now, but what if I told you you're barely scratching the surface?

In this video, I'm going to walk you through every level of Claude user, from the amateur, all the way to the one who builds fully autonomous systems that run without lifting a finger.

Let's start with level one, the amateur.

See, the amateur treats Claude like a fancy Google search.

One question in and a response back and then they close the tab.

There's no memory, there's no projects, Claude has no idea what you're working on and you're using maybe 5% of what Claude can do.

It's like having access to a NASA supercomputer and calculating 2 plus 2.

So if you're in this level, here are two pro tips to help you level up.

Number one, make Claude interview you first.

For example, you can tell Claude, before you answer, ask me any questions

that you need to perform this task properly

and watch it ask you the questions that provide the context that it needs to give you the best answer.

The second thing is you got to make Claude check its own work.

Watch it catch its own mistakes, which is annoying because you think it would do it in the first place, but it will give you a better output.

You can use this every day by just saying check your work.

Now, before we go to the next level, we have to stop working from scratch every time.

So how do you make Claude have persistent memory?

Level two, the regular.

The regular treats Claude like a workspace.

They don't just chat with it.

They use projects, which is featured within Claude, for their role.

They use it per initiative.

They use it per client.

They're using it per workflow.

And what's cool is Claude finally remembers who they are every time they come back so the work gets better.

And this is how you set them up the right way.

So number one, on the left side, you will see create a new project.

Click that.

And then name the project the role you work in.

And in this example, just say marketing.

Okay, that's your role.

Second, we need to build a master prompt for your role.

So every time you chat with it, it knows who you are and what you're trying to accomplish.

Now, the cool part is you can ask Claude, type this in, interview me to build a master prompt for my role as a marketer.

Watch Claude ask you questions, you answer it, and then you get a file.

That is your master prompt.

And what a master prompt is, is a file of instructions that tells the AI everything about you how you like to work, what your team looks like,

what tools you use, everything about your role, so that every time it gives you an answer, it can use that information to guide its output.

The third is we got to add the files.

So now that we have the master prompt, let's go back into the project, add that as a project file, then any other documents you have within your company, maybe it's sample data, maybe it's examples,

maybe it's files, maybe it's processes, put that in the files directory with your master prompt.

Now you have a customized space that has memory, that has context, and has your specific workflow for how you like to work.

So for example, every time I sit down to create a YouTube video, I have a project folder to help me ideate and give me outlines and strategies.

In my files, I gave it everything that it would need.

I gave it my voice document, my branding document, my examples of previous scripts that I like.

It has everything that it needs to create outlines based on how I've done them in the past.

And then I just direct it.

And then I hit enter and Claude gives me the outlines.

Here's a pro tip.

If you wanna take projects to another level, do this.

Ask the AI to interview you to create a system prompt for a specific workflow

that you're trying to create with your chats.

The master prompt is like your ingredients.

That is everything about you, your context, et cetera.

The system prompt is the recipe.

It's the instructions.

It's the process.

So you probably already have a process.

You just never documented it.

So the AI can interview you so you get that as the output.

So once you get that, just copy and paste the system prompt into your custom instructions and watch this thing run like a machine.

That way you have the same quality, the same format every frigging time you use that project.

And look, if you want to go even deeper

and how to incorporate cloud or any AI into every department within your business, I have my AI company OS,

the exact playbook I use to integrate AI into all my businesses and I'm giving away for free.

If you want to just DM me YouTube OS on Instagram and I'll send it over.

So now your projects turn Claude into a workspace like a desk with a process and the whole thing's automated.

But what about everything else?

Think emails, calendars, work you have to do in the browser.

Level three, the integrator.

The integrator plugs Claude into the tools where work actually lives.

We use Gmail, calendar, Drive, Slack, Notion, the integrator connects it to Claude.

So they stop bouncing around from all these different tools and tabs.

Why would I have to go copy and paste an email into Claude

when I can just tell Claude to go get the email?

The cool part now is that you can build an act inside Claude.

The integrator doesn't leave the tool.

They do the work in the tool and then they send the information

that the tool created to wherever it has to go.

So here's how you operate at the integrator level.

Number one, we use connectors, okay?

So go through and connect your Gmail, your Drive, your Slack, your Notion, all the systems that you have, it has an ability for you to connect those data systems

so that it'll search those places next time you're chatting with it.

Two, build visualizations.

This is my favorite feature in Claude is that I can get it to visualize things.

I can create graphs, bars, mock-ups, all inside the chat.

And even better, the third is build interactive artifacts.

These are like little mini apps that you can have outputs that are clickable and sliders and buttons,

and it makes learning or visualizing information or interacting with data so much easier.

And here's an advanced move that nobody talks about.

You can actually paste text into chat and tell it to put it inside Composer, which is like a Google Doc inside of chat,

and then you can edit it and play with it so that it gets the output exactly like you want.

My cloud is connected to my Google Drive, to my Slack, to my calendar, to my email.

So I tell it all the time, Hey, look at my calendar.

Tell me what I'm missing.

Look at my email.

Tell me what I need to know.

I'm the CEO of my company.

100

Scan Slack for the last week and give me CEO level understanding of what's going on across the company.

101

These are things that I run almost on a daily basis.

102

So I'm always on top of it.

103

Now, if you want to level up with a pro tip, install Claude in Chrome.

104

I use this all day long.

105

Oftentimes I'll have a chat asking me to do something.

106

I say, write the instructions for me.

107

I copy, I paste it into Claude inside of Chrome within some site

108

and I hit enter and it goes and does my work for me.

109

Now, this is all super cool, but the truth is Claude's just helping you at this level.

110

The next level, that's where Claude actually does the work for us.

111

Level four, the operator.

112

The operator, this is where you stop being the doer and you start becoming the director.

113

I consider this the human in the loop where the operator, you, are now setting up tasks that run on their own.

114

You just review things and you approve it.

115

This is where you stop using Claude and you start deploying it to solve problems for you.

116

And these are three ways any operator can deploy Claude to do work for them.

117

So number one is system prompts.

118

Essentially, you want to have Claude interview you to create these system prompts for any type of output.

119

So I I believe that the future of intellectual property

120

and what makes teams or companies valuable is that they have system prompts defined for the things they create.

121

Level two is skills.

122

You will notice over time, as you keep doing these things, these workflows, you can actually save them as skills.

123

Cloud has a bunch of skills that you can install.

124

They've created hundreds, everything from financial skills and marketing skills, et cetera, but you might have some proprietary things you do inside your company.

125

If so, you wanna create a slash, name it and run it and then make it a skill.

126

My rule is if I'm doing it more than three times a week, I might as well have as a skill.

127

For example, I'm always wondering what's going on within my company.

128

So I created a company status skill that analyzes all the analytics and the metrics and the reports and everybody's updates.

129

And then gives me a cute, concise little update on the company as it is today.

130

So I just type forward slash company status and it does it every time.

131

Third is scheduling co-work tasks.

132

Now, if you haven't heard of co-work, that's an app that runs on your computer and it can literally take over your computer.

133

So you can get it to run a job like migrate from this system to another system hit enter, go have dinner, come back and watch it get done.

134

So what a great operator does is he looks at his system prompts and he looks at his skills and he goes, hey, are these repeatable outputs that I can schedule and co-work to have it done every day?

135

So for example, every night I get a message at eight o'clock

136

that shows me my following day and it looks at my emails

137

and my calendar and lets me know everything I need to do as

138

if I had a chief of staff and I do and she's awesome, but I set it up because I don't need her to do it.

139

Then I know what tomorrow is going to hold.

140

So if I had to make any last minute changes, I can do it.

141

I set it up once and it runs it every night and I never have to think about it.

142

The operator realizes with AI, they direct the work.

143

They don't just do it.

144

Now this is a massive pro tip and it's called chaining your skills.

145

So for example, you might have a copywriting skill that writes in your voice and then you're writing emails, which is also its own skill and it'll use the copywriting skill

146

and those two skills might be called in a completely different skill that's all about automating your inbox

147

And those skills are like separately packaged little genius agents that all chain together to create an outcome.

148

The whole pipeline is chained skills.

149

The operator is now really using AI.

150

So schedules and skills, those automate with your existing tools and connectors.

151

But what if the tool doesn't exist yet?

152

Level five, the builder.

153

Not too long ago, we shut down the company for two days.

154

We held an AI hackathon.

155

We taught everybody how to code.

156

In those two days, everybody on the team became builders.

157

Essentially what you can do is use Claude to write code, build custom apps, dashboards, internal tools, all inside of Claude Code.

158

Now Claude isn't just answering questions anymore or setting up skills.

159

It's literally shipping software.

160

In this level, we're introducing a new level of Claude called Claude Code.

161

And just so you know, if you're in this level already, you're in the 0.04% of the population.

162

Most people don't know this.

163

Inside Claude Code, you can use three categories of building.

164

The first one I called loops.

165

These are reoccurring jobs that do work.

166

They're similar to co-work, but they run inside of a server and they can talk to other agents.

167

They can talk to other systems.

168

They can use other APIs and they're way more advanced, but they're loops because they're always running.

169

Number two is tools.

170

These are things you build for one-off situations.

171

So you might build a tool for a project.

172

You might build a tool to help you accomplish something.

173

It's not gonna be something you're gonna do forever and that's why I consider them disposable.

174

The third level is apps.

175

I'm talking real software.

176

Everybody that was involved in that hackathon I talked about built real working production software.

177

For example, I have this incredible person named Betty.

178

She's my house manager.

179

She manages our lives for my wife and I.

180

She built a system that manages all of our workflows, every aspect of my personal life, the cars, the real estate, the investments, the budgets, everything.

181

And she's not a programmer.

182

In the world of AI, English is the new programming language.

183

Now, if you want a pro tip, 100% of the time before I build anything, I use a feature called plan mode.

184

Essentially, you hit forward slash plan, enter, and then you just dump your idea.

185

It hears everything you said, and then it will ask you questions if it needs, and then write a whole completed plan that you approve first before it writes any code.

186

The reason why play mode is so important is because people always complain, oh my gosh, Dan, it costs so much to do all these AI apps now.

187

It's because they didn't play it up front.

188

If you do this, it'll save you a ton of money.

189

And another pro tip plus plus is Cloud Code Remote.

190

And I use this every time I leave my laptop, where in your terminal window where you're writing code, you can say forward slash remote control,

191

and it will connect to your Cloud app on your phone.

192

It keeps writing code.

193

And I did this three or four times while I'm mountain biking on my phone, I'm writing code.

194

And that is how I got this because I took a berm and my front tire washed out.

195

Now we just talked about how you build tools, but what if we could learn how to build team members?

196

Level six, the agent orchestrator.

197

The orchestrator is the agent you design that actually runs something.

198

So now it's a loop that keeps running a department, a process, a workflow, and you're no longer involved

199

because you took all these pieces we just talked about and you plugged it into the Claude agent, now you're the human on the loop, not the human in the loop.

200

Claude stops being just the tool and it now becomes infrastructure.

201

Now there's a million ways to build an agent, but instead of telling you how to build just one, I wanna give you a framework to teach you how to think about building agents.

202

First, you have to start with one main agent.

203

This is your agent.

204

It could be your chief of staff agent.

205

It could be your admin agent.

206

I've got a CEO agent.

207

This is your orchestrator.

208

Mine is called Kai.

209

He doesn't do anything really.

210

He just directs the other agents.

211

I know this is crazy.

212

Next, you have to go and create specialized sub-agents and each sub-agent owns a workflow.

213

Your main agent communicates with the sub-agents and tells them what to do.

214

The third is you connect your telegram to talk to your agent through your phone.

215

Reese is my real estate agent.

216

He finds deals of investments that I can do.

217

And Kai checks in with Reese every day and reports back to me because he does that with all my agents.

218

All done without me having to do anything.

219

The agents think, they decide, they execute within the parameters.

220

See, we're building the machine that runs the machine.

221

Your main agent is that machine.

222

Now, I use my own platform called Apex.

223

You can go check it out at apex.host, but you can use Claude to do this.

224

Actually, behind Apex, we use Claude as the main agent model.

225

Apex just makes it more secure and way easier to interact with it.

226

Now, here's a pro tip.

227

I have a critique agent that my main agent will ask to go

228

and review things like copywriting or research or anything so that it's done right.

229

It creates a list of notes to make it better, gives it back to the agent.

230

It runs it again.

231

So I always get the best output.

232

So now do you see how I'm no longer involved in the work?

233

I'm the human on the loop.

234

My partnership with the AI allows me to do way more than

235

if I was having to sit there and process information through a pipeline.

236

And you can do this too.

237

Most people are just collecting cloud features.

238

They're like, oh, I use that.

239

I'll use this.

240

But they don't actually make it part of their habits.

241

So here's what I need you to do.

242

Choose one of these features and make a commitment to do 30 days in a row of using it.

243

Maybe it's a cloud browser extension, maybe it's advanced and say, okay, every day I'm going to work on an agent.

244

I don't know what it is for you.

245

Leave a comment below and let me know what you're committed to.

246

And remember, if you want my AI company OS playbook, the same one I use in all of my businesses, just DM me YouTube OS on Instagram and I'll send it right over.

247

And if you want to know the six most profitable AI businesses to start, click here and I'll see you on the other side.

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법

쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.

쉐도잉 연습: Full Claude Guide: Beginner to Pro in Under 15 Minutes - 영상으로 영어 말하기 배우기

왜 이 비디오로 말하기 연습을 해야 할까요?

문법 및 표현 분석

일반적인 발음 함정

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법