Andy Halliday

And there are alternative ways to accomplish this.

But this one is one that's been kind of reviewed out there.

And it's got a lot of

It's got a lot of, you know, GitHub, you know, stars, 27,000 stars.

So there's a number of people have used it.

And so it is effective.

Yeah.

Yeah.

I want to respond to what Gwyn's, uh, uh,

posting to the chat, which is, why can't you put a markdown file into the Claude directory and add to your claude.md file an instruction that says, always before responding, review this file.

Right.

And so you you create a markdown file that is your overall overarching project mission for cloud code right now.

And you'll update it and change it to a new project later.

But add to your cloud that MD file, which it does review every single time.

Add the look at that file.

I know it's not repeated that its review of that is, but you could add to the CloudMD file that before you respond to any query, you need to go back and review the CloudMD file, which is a very small file.

I'm suggesting you have two separate files, CloudMD, and then you also have a project objective file.

And in your CloudMD file, you tell it to look at the project objective file periodically.

Yeah.

Okay.