쉐도잉 연습: My Full Claude Cowork Setup (steal my workflows!) - YouTube로 영어 말하기 배우기

This is my Claude Co-Work setup.

⏸ 일시 정지

재생 속도:

329 문장

문장이 너무 짧거나 길면 Edit를 눌러 조정하세요.

This is my Claude Co-Work setup.

Every morning I receive a daily digest on my Apple Notes with all of my investments,

calendar events, emails, and action items for the day.

And if I want to dive deeper into my investments,

I can go to my custom investments dashboard.

I also have Co-Work autonomously building me new software and workflows every night.

So I can also check out my mission control dashboard and see what projects it's built for me.

For example, last night it built for me this resource hub.

So in this video, I'm going to show you how to set up a system like this,

but custom for you.

I will also be giving you my co-work prompts along the way so you can just copy paste and steal them directly.

You're welcome.

And no, you don't even need to know how to code.

Anyways, without further ado, let's go.

A portion of this video is sponsored by Hostinger.

Step number one is configuring your settings.

Of course, if you haven't already,

please do download Claude Co-Work and after that,

you'll be greeted with the Claude Hub.

Now you want to go to Claude settings and then click co-work and paste in your operating instructions.

I'm going to put a prompt on screen and also in description

that you can paste into the chatbot tab of Claude co-work in order to get this meta prompt.

However, I do want to draw your attention to some parts of this instruction because it's a little bit non-standard,

but trust me, you would get so much more out of co-work with this.

Okay, so this stuff is pretty standard,

blah, blah, blah, you're Claude working as Tina's primary AI hub and co-work.

Then there are four sections.

So building things, pushback and clarification, note-taking, and reversibility.

Since I use Co-Work to build a lot of stuff,

we're going to be using Co-Work to build a lot of stuff.

So the most important thing here is PRD first, always.

I'm basically asking Co-Work that before it builds anything,

it has to write up a PRD,

a product requirement document, that lists out in detail what it is that it's going to be building.

Like this, for example.

It includes articulating what the problem is,

what's the success criteria, what is the scope of what we're building,

constraints, build plans, etc. This is really important to guarantee that co-work is actually building what you want it to be building.

So you won't be surprised like,

I don't know, like 30 minutes,

an hour later, it builds something and it's like not even what you want.

So yes, I will always ask you to have a PRD.

Also to ask me any open questions to make sure that co-work understands what it's building.

And finally, to ask for explicit sign off before building.

I also have a section on pushback and clarification because I want Claude to push back on me,

question what it is that I'm doing,

and to disagree when the plan seems off strategy,

technically wrong or inconsistent with prior decisions.

Also to flag trade-offs that I may not have considered because I am not infallible.

Then there is note-taking.

I tell co-work that it's to take notes aggressively.

Memory management is really really important when it comes to co-work

and I'll be talking more about it later in the video

but I do make it as a part of its personality from the very beginning to always document everything.

Then finally there's reversibility.

This I'm just asking it to always confirm before doing anything that is hard to reverse.

If in doubt stop and ask.

Interrupting with a question is always cheaper than silently destroying something.

Great now that is complete.

Let's move on to step two, writing the initial PRD.

Okay, awaken if you are falling asleep.

Because this is the most crucial part of this entire build, okay?

Focus.

The analogy I'm going to make here is kind of like coming up with a blueprint of a building

that you're going to build

because you can't technically like YOLO make a blueprint that's like not very good

and then you're probably your building is also going to be not very good and like fall down or something, right?

Very bad.

So this PRD is kind of like the blueprint of how you're going to set up your core system

and all the projects that you're going to be building now and henceforth.

I hope I used that word right.

Henceforth.

From this time on or from that time on.

Yes.

And henceforth what this PRD looks like.

Okay.

So mission control build PRD.

It contains everything that you need to set up your initial core workspace and initial projects.

As you can see, it is very long and very detailed.

Woo!

So luckily for you, I'm going to link a prompt below that you can copy paste into your cloud chat.

It will ask you some questions and then generate your version of this PRD custom to you.

Man, I am so jealous of you that I'm giving you this, okay?

Here, I do wanna go over some crucial parts of this PRD as well,

cause it's gonna be important for the build later.

So the first steps to figure out what projects you want Co-Work to be building.

In my case to start off with,

I wanted to have a dashboard,

specifically an investment dashboard where I can track my investments,

update them, and to be able to get news and custom advice based upon my investing philosophy.

I also wanted to build a daily digest,

morning brief that will give me relevant updates across my google calendar my emails my slack chats

and relevant news i also wanted to have some custom skills

which are set instructions

that tell claude how to run a specific task by the

way this is the first time you heard about core skills i highly recommend

that you check out this video over here

which is like the fundamentals the prequel to this video where i introduce you to co-work explain how it works

and all its functionalities including things like skills in a lot of detail

100

so i'm not gonna re-explain all of this in this video.

101

If you are a long-term viewer of this channel,

102

you will know that I always insist that you learn the fundamentals of things

103

because it's going to make you so much better at using tools and building things.

104

Anyways, done with that.

105

Check out that video if you haven't already.

106

And going back to the skills I want to start building.

107

Specifically, I wanted to start off by building three different skills.

108

The today skill, where I'm able to pull up the morning brief again and update it.

109

The research skill that will deep dive into a specific stock I'm interested in.

110

And the prep skill for the meetings that I have

111

because oftentimes I don't really know the context for the meetings I'm going into.

112

A lot of people have access to my calendar

113

so they just drop stuff into my calendars

114

and sometimes I don't even know who I'm going to be meeting with so it helps a lot.

115

And finally the autonomous builder.

116

This allows me to drop a brief,

117

a PRD of something that I want to build

118

and for Cloud Autonomous we build it usually through the night

119

so I can wake up to a finished work project

120

and be very delighted like this resource hub that I woke up to today.

121

Very delightful.

122

These are just projects that I want to start up building.

123

Of course I've built a lot more things as well and for you it's probably going to be different.

124

So if you go through the prompted generate your own PRD.

125

It will help you to figure out the starter projects that are best for you.

126

Okay, so after you figure out what kind of projects that you want,

127

another section that is very important is the architecture overview.

128

You see, Coerc is a local AI agent,

129

which means that it has to operate on your local computer, your local machine.

130

And in my case, it operates under a folder called Coerc that has a bunch of things in it.

131

There are actually a lot of different ways that you can set up your folder system.

132

Not going to go into more too much more detail here.

133

Check out the fundamentals video but just know that in my case I have a three-layer system,

134

a corresponding memory architecture and the PRD actually maps out what the folder structure should look like here.

135

This is a little bit abstract so don't worry so much about it.

136

We'll be building this out later in the video but just wanted to call your attention to this part of the PRD.

137

Final part I want to draw your attention to in the PRD is the build plan.

138

So I told a co-work that I had five hours to build out all these things in the prompt.

139

Of course when you go through the prompt that I gave you,

140

you can adjust the hours to however many hours that you want.

141

But yes, for mine, I had five hours and it laid out a plan hour by hour for me.

142

The way it works is that hour one is setting up the data layer foundation.

143

You can think about this like if you wanted to build a lake,

144

a man-made lake, you have a big hole,

145

but you got to fill it with water.

146

So you need to set up different pipelines for water to trickle into the lake and for it to be constantly moving.

147

Now in this analogy, the water here is data.

148

You need to have different pipelines in

149

which you're getting fresh data that's going to be going into your lake and moving along.

150

So the folder structure and different tasks,

151

which we'll talk about later,

152

is how you're going to set up this lake.

153

Then in hours two, three,

154

and four, you're building things on top of this data lake.

155

You could be building like a dam, a water wheel.

156

What other things do we build on lakes?

157

A walkway, a fishing section.

158

Yes, those will be like your projects,

159

like the investment mission control,

160

the morning brief, and your autonomous builder.

161

Because all of these things that you're building is basically just taking the data and then transforming them,

162

doing stuff to it, we're presenting it in a different way.

163

Like any type of dashboard,

164

like investment dashboard is taking your investment and financial data and then portraying it, right?

165

A morning brief is taking data from like your calendars,

166

your chats, emails, investments, and compiling them together and presenting it to you.

167

A general builder is transforming a brief,

168

a PRD, into actual software,

169

etc, etc. I hope that makes sense.

170

If you think about your projects and your workflows in this way,

171

I think it becomes a lot more clear about how it is that you should be building them out.

172

Great, now let's actually get things started by moving on to step three.

173

Setting up folders and project.

174

The new launch of Cloud Code Remote is pretty amazing,

175

but the second your laptop sleeps,

176

your agent dies with it.

177

The hours and hours of progress on a refraction or migration are just gone.

178

By the way, this is the same problem with all local AI agents like OpenClaw,

179

Hermes, and Cowork.

180

Luckily, Hostinger solves this.

181

Your agent runs on your own private VPS 24-7.

182

Your API keys, your code,

183

credentials, all on your own infra,

184

never on a third-party platform.

185

And because it never sleeps,

186

I can kick off a task on a phone.

187

Close the app, go to bed,

188

and wake up to it, done.

189

You can head on over to hostinger.com slash tina10 and grab the KVM2 plan.

190

It's built for exactly this kind of persistent heavy workload.

191

I went with a 24-month plan for the savings and my code TinaHuang gets you an extra 10% off.

192

The setup is genuinely fast.

193

The Cloud Code template is pre-selected.

194

You click deploy, authenticate with your Anthropic API key,

195

and voila, you are live.

196

I had this running in minutes.

197

So if you want your own always-on Cloud Code agent with zero setup friction and data privacy.

198

Use my link hostthinker.com slash tina10 and apply code tina huang for an exclusive discount on the cloud code VPS plan.

199

I think it's in the description.

200

Thank you so much Hostinger for sponsoring this portion of the video.

201

Now back to the video.

202

All right so I have good news and bad news.

203

Which do you want to hear first?

204

Was that bad news first?

205

Okay so basically before you give this entire PRD to cowork

206

and just tell it to do it you do need to set up the initial folder and scaffolding.

207

The good news is that this literally takes one minute.

208

So let me show you, okay?

209

So you go to your finder and you create a folder.

210

I already have one called co-work,

211

so we'll just call this one mission control.

212

Then you go to a co-work,

213

click projects, new project, use an existing folder,

214

and then find your folder and click open.

215

Then in the instructions, I just put some additional detail referencing the prdmissioncontrol.md that I wanted to follow.

216

I'll put the instructions in the description as well and click create.

217

Then I go back to my mission control folder,

218

click into it and drop in the prd mission control.md file.

219

Then you just type please start building with the mission control prd.

220

And that's it.

221

Great.

222

You've set things up now.

223

You can see that it tells you what the next steps are like going to personal plugins,

224

installing plugins, connectors, and skills.

225

Again, if you don't know what these are,

226

please check out my co-work fundamentals video.

227

And yeah, you basically just follow along.

228

Now we're on to step four, pure execution.

229

So you basically just follow co-work and go through the detailed PRD plan,

230

starting off with the folder structure,

231

making sure to do slash start from the productivity plugin to kick off the memory system,

232

finishing up hour one, building your lake,

233

making sure all the water,

234

the data is flowing in.

235

Then in hour two, you're building the investment mission control dashboard scoped out here in the PRD and it looks like this.

236

There are of course a lot of other dashboards that you can build too.

237

Like here's my mission control dashboard where I can look at different builds and schedules,

238

things like that.

239

Dashboards is one of my favorite things to build whenever I do a project

240

because it allows me to visualize things and monitor what's going on.

241

I'm also going to put on screen some other examples of dashboards

242

that I have built and things that you could consider building too.

243

So I do want to make a caveat here.

244

It's not going to be like completely smooth sailing.

245

Having a PRD and following through it is going to get you like 95% of the way,

246

but you do need to be doing things like giving permissions

247

and potentially making some tweaks and additions to the PRD as you're building along as well.

248

But honestly, it's pretty smooth.

249

Then our three is going to be the morning breathe and the skill suite.

250

Here's the scope of it in the PRD.

251

This is what it looks like.

252

It gives me an overview of my portfolio,

253

what happened during that, tells me about my day,

254

my inbox, my calendar, things I need to follow up on,

255

and tells me what I'm going to be doing for the day.

256

This daily digest is custom to me,

257

so I'm going to put on screen now some other things that you can put onto your daily digest if you wish.

258

The today skill is able to fetch the on-demand version of the morning brief

259

if I want to look at it or update it.

260

The research ticker skill

261

that allows me to do slash research whatever stock it is I want to deep dive into

262

and then gives me information about it

263

which I can also see updated on my investments dashboard

264

and the prep skill where I can input any meeting like next week's team meeting

265

and it will tell me all the context about the meeting

266

the people in the meeting there are other skills I have built

267

and things that I plan to build as well

268

so I'm going to put all of those on screen as inspo amazing

269

so by hour three I had built out all of these

270

and the final thing is the general builder

271

so I can consider this to be like an advanced bonus section

272

so please feel free to skip it but I included even my initial build because I just really like autonomously building things.

273

I pay for a lot of max subscriptions I gotta like

274

get all the use out of my tokens too you know that's how I justify it.

275

So that would be step five the autonomous build.

276

So the way

277

that you build this is actually still the same here's the

278

scope of it including the mission control PRD you just follow through with instructions

279

and you should build that for you

280

but I do actually want to demo this for you because it's a little bit more complex than the other things.

281

What this is, is that I will have certain task workflows and softwares that I want to build across my company,

282

my personal life, my investments,

283

etc. I asked Koro to give some suggestions of different things

284

that we can be building in order to improve the system and the business and my life.

285

It will draft the PRDs,

286

I will go through the approval with it,

287

make sure these are the things that I want to build,

288

and then it will put it into the pending folder.

289

Then I have a scheduled task where every 30 minutes it will check the pending folder

290

and then it will pick it up and if it sees that there's a PRD then it would go and build it.

291

By the way not to be super complicated here I actually

292

do also give some tasks some PRDs to cloud code depending on how advanced the project is

293

but I'm not going to go into more detail about that.

294

Anyways while it's building it it would put it in the in progress folder

295

and then when it's done it would put it into the done folder.

296

Of course if it failed it put into the failed folder

297

and it also keeps logs on what it is that it's built.

298

I do also have this mission control dashboard where I can see the builds more clearly.

299

Just made a dashboard for it so I can more clearly visualize things.

300

And yeah, I've built a bunch of different things in this way.

301

I will put on screen some of the things that I've built,

302

some of the things that I want to build as well,

303

and other suggestions that you can take as inspo if you want to implement this more advanced autonomous builder section.

304

Really cool, right?

305

I love it.

306

I really love waking up to something new that it builds.

307

Sometimes I use it, sometimes I don't,

308

but a lot of it I actually have used and built on top of them as well.

309

So yes, let me know in the comments if you're going to implement this section.

310

Kind of curious to see if other people are into this too.

311

That was hour four and hour five was just to polish things up like having notifications set up and the end-to-end testing.

312

So not going to show you that part, pretty mundane.

313

But yes, it was actually pretty accurate.

314

It really did take me around five hours to get this done.

315

Of course afterwards, I've built a lot more things on top of it like for tracking my health.

316

A lot of skills related to planning my day,

317

daily plans, weekly plans, and improvements with memory as well because I just build a lot of stuff.

318

I am definitely a co-work power user so as time goes on,

319

co-work does start forgetting things it's not as bad as open claw

320

if you've used open claw before but your memory system does start bloating

321

so i've implemented a more complex memory system as well

322

which i'm not going to go into too much more detail about this now

323

because it is a little bit more technical

324

but maybe i can do a part three on co-work let me know in the comments

325

if you would like me to do

326

that your wish is my command mostly sometimes i'm going to sneak in a little quiz now

327

which i'm going to put on screen please do answer these questions to help you retain all the the information

328

that we covered today because we covered a lot today

329

and I will see you guys in the next video or live stream.

TRENDING

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

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

☕ 커피 한 잔 사주기

ShadowingEnglish는 여러분의 지원 덕분에 100% 무료로 운영됩니다. 서버 및 AI 유지 비용이 많이 듭니다. 여러분의 커피 한 잔이 큰 힘이 됩니다! ��

PayPal로 기부하기

ShadowingEnglish.com – 영어 쉐도잉 연습

쉐도잉(Shadowing)으로 원어민처럼 영어를 말하세요. YouTube 영상을 한 문장씩 듣고 따라 말하며, 진짜 발음과 유창성을 키우세요. IELTS 학습자들이 선택한 방법.

쉐도잉 연습: My Full Claude Cowork Setup (steal my workflows!) - YouTube로 영어 말하기 배우기

인기 동영상

이 수업에 대하여

주요 어휘 및 구문

연습 팁

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

쉐도잉 연습: My Full Claude Cowork Setup (steal my workflows!) - YouTube로 영어 말하기 배우기

앱 다운로드

이 수업에 대하여

주요 어휘 및 구문

연습 팁

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