§ 01 · The Hook
The bait, then the rug-pull.
One hundred thousand GitHub stars and seven million X views. When Andrej Karpathy — ex-Tesla AI director, OpenAI founding team — writes down what's wrong with how LLMs code, the community listens. Eric Tech took those four rules and dropped them into a real Claude Code project to find out if they actually work. They do. But the bigger move is what you do after the install.
What the video promised.
stated at 00:00 "what it is, how does it work, and how is it different compared to any other skills that we have used in the past" delivered at 10:10
Where the time goes.
00:00 – 00:47
01 · Intro — Karpathy's 4 problems with LLM coding
Names the authority (Karpathy, 100K stars, 7M views), states the three problems: wrong assumptions, over-complicated code, rogue edits.
00:47 – 01:48
02 · School community CTA
Mid-video ad read for Skool community — AI agents, automations, Claude Code masterclass, weekly live calls.
01:48 – 02:57
03 · The Four Principles
Walks through all four rules in the README: think before coding, simplicity first, surgical changes, goal-driven execution.
02:57 – 04:03
04 · Install options
Three install paths: Claude Code plugin (global), new project curl, existing project append-curl.
04:03 – 05:30
05 · Live install on bookzero.ai
Runs the append command, opens git diff, then asks Claude Code to merge conflicts and clean up the CLAUDE.md.
05:30 – 07:48
06 · CLAUDE.md vs Skills (Superpowers / GSD / G-Stack)
Defines the key distinction: CLAUDE.md rules are always-on personality; skills are triggered. Compares functionality overlap and unique contributions.
07:48 – 10:10
07 · Combining Karpathy rules with skills
Maps each principle to a specific skill invocation path: brainstorming, debugging, planning, simplify-before-commit, test-driven dev, security review.
10:10 – 11:03
08 · Outro + playlist CTA
Subscribe ask, link to full spectrum-dev frameworks playlist in description.
Visual structure at a glance.
Named ideas worth stealing.
00:00
list
The Four Karpathy Coding Principles
- Think Before Coding
- Simplicity First
- Surgical Changes
- Goal-Driven Execution
Embedded as always-on CLAUDE.md guardrails. Derived from Karpathy's X post on LLM coding pitfalls.
Steal for Any CLAUDE.md file — paste these in and tell Claude to merge with your existing rules
00:00
concept
CLAUDE.md = Personality, Skills = Triggers
CLAUDE.md rules fire on every message without invocation. Skills require explicit trigger. Combine both: CLAUDE.md sets the floor, skills add the workflow ceiling.
Steal for Explaining to clients or students why CLAUDE.md matters beyond just preferences
00:00
model
Karpathy + Skills Wiring Map
- Think Before Coding: superpowers brainstorming (features) / superpowers static-debugging (bugs)
- Multi-step task: superpowers writing-plans or gsd plan-phase
- Simplicity First: simplify skill before commit
- Surgical Changes: scope-creep guard; worktrees per change
- Goal-Driven: gsd test-driven-dev, superpowers verification, security-review
Eric's final recommended CLAUDE.md shape: Karpathy rules + per-rule skill routing.
Steal for Template for a combined CLAUDE.md that routes every situation to the right skill
Lines you could clip.
05:10
"It's personality embedded into the model's brain — every time it does something, it knows this because it's embedded into its soul."
06:50
"Superpowers and G-Stack teach how to work carefully but they don't say how much to do — these guardrails fix that gap."
08:50
"The possibility here is endless — just pick the skill you want and add it into your CLAUDE.md and Claude knows exactly what skill is gonna trigger."
How they spent the runtime.
Hook length12s
Info densityhigh
Filler8%
Sponsor blocks
- 00:47 – 01:48 · Skool community (own product)
Things they pointed at.
How they asked for the click.
00:47
product
"I recently launched our school community where I help you to master AI agents, automations, and so much more"
Placed at ~45s before the main tutorial content. Own-product ad. Also pushed a playlist CTA at the outro.
Word for word.
HOOK opening / re-engagementCTA the pitch metaphor analogy
00:00HOOKIn this video, we're gonna go over this Andrew Kaparvi skills, which gone over a 100,000 stars on GitHub, and this skill is derived from this x post that Andrew Kaparvi has wrote. And if you don't know what Andrew Kaparvi is, he is previously a director of AI at Tesla and a founding team at OpenAI. And currently, this X post has gone over 7,000,000 views on X.
00:19HOOKAnd essentially, what this skill does is addressing the problems that Angi Kaparvi sees on X. And the first problem we see is the model here always make the wrong assumption. So it doesn't ask clarification question.
00:30HOOKWhen you give it a prompt, it just act on it. And the second problem they see is that a model here oftentimes overcomplicating things.
00:37HOOKCTAThings can be run-in 100 lines, often rows in a thousand lines. And oftentimes, large language model here making changes that they're not supposed to without a clear understanding about the full side effects. So that's why in this video, we're gonna take a look at what it is, how does it work, and how is it different compared to any other skills that we have used in the past.
00:54CTASo with that being said, if you're interested, let's get into the video. Now before we continue, I recently launched our school community where I help you to master AI agents, automations, and so much more. And that's all coming from someone who used to work as a senior AI software engineer at companies like Amazon and Microsoft.
01:10CTAAnd in this community, you're gonna get over a 100 plus video materials like templates and workflows that I personally built and sold over a 100 plus times. On top of that, you're also gonna get access to our weekly live calls. And just to give you an idea, this week, we're actually running a Clawcode masterclass where we're gonna dive into how to improve Clawcode's accuracy when we're gonna use it to build the applications.
01:29CTAPlus, you're also gonna get full community supports where you're get a chance to ask questions and get direct answers back. So if you're ready to level up, make sure to jump right in, and I'll see you in a community. Alright.
01:38CTASo to get started, let's take a look at what this skill is trying to offer. So right here, can see this skill here offers four principles that we can use in our project, which will basically roll inside of our CloudMD file. So first principle here you can see is think before coding.
01:51Largely new model here, like I said, makes wrong assumptions, doesn't clarify things, and by having this principle, it's gonna force AI here to have to think before it's gonna do the execution. And the second here is simplicity. Things that can be wrote in 100 lines of code never should be wrote like 500 or a thousand lines of code.
02:09Right? Never should be complicating things. And the success criteria here is that if a senior engineer says that this is over complicated, that we should definitely simplify.
02:17And that's exactly what this principle is trying to solve. And the third one here is surgical changes. So let's say we're making changes.
02:23Large language models should never touch code that are not related to the instruction that we provide, and that's essentially what this principle does. And the last one that we have is goal driven execution. We need to have a clear goal on exactly how large an extra model can perform before it's going to do the executions.
02:39And it's similar to the first one, but we need to have a clear success criteria for the expected behavior on the end results. And that's the four principles that the skill is trying to introduce, and they all compacted down into a single CloudMV file that we can add into a project to make sure that large language model here never hallucinates when writing code.
02:57Now to put this into practice, here you can see it tells exactly how to install this. First of all, what we can do here is that we can install this in Claw plugins. Simply, we're just gonna add the skill in our marketplace and install it.
03:07And the second option that we have is, let's say, you want to install this not globally, but in a project level, simply you can just do this curl command here and add this onto your new project. But if you have an existing project, you can simply just gonna run this command right here, and simply it's gonna write this rule onto your CloudWeb file onto your existing project.
03:24Now for my case here, I do have an existing project called BookZero dot a I, where I help business here to manage receipts and transactions all using AI. What And I wanna do here is I wanna install this onto this project and see how does it work. Now in order to install this, all I had to do here is just gonna copy this command.
03:38It's gonna install this on existing projects. So here, I'm just gonna come over to a project terminal, open a new terminal, and just gonna paste that command here. And what this essentially, this command does is going to modify my CloudMD file by simply adding those four rows onto there.
03:52So in this case, I'm gonna click click on enter, and you can see that it's going to modify my CloudMD file. So now if I would open the git diff, and here you can see this is the change that has applied. And for most of you guys, you probably already have your CloudMD file with your existing project.
04:05And by installing it, it might have some contradiction or conflict with your existing rules. So what I highly recommend you to do is basically tell Cloudcode to basically try to modify your ClawdMD file once you paste that, once you paste those four principal to see if there's any contradictions,
04:20any conflicts, anything that's not following what you have in your ClawdMD file. Like, try to merge the conflicts that you have.
04:27And you can see here that this is what it recommends. After it pastes it from the original Cardpathic Skills repository, here's some problem that I found.
04:34For example, we have the duplicate h one tag for the CloudMD file because the CloudMD file already has that. And here you can see there's some meta framing here that really tells a human reader what a doc does, but the CloudMD file here doesn't really need that. It needs the instruction, a clear instruction on exactly what it needs to do.
04:51Now we also have removed some redundant stuff that's not really relevant to our CloudMD file, and you can see Cloggo has also removed that and make it more concise. So again, same rule, less to read, so that we can be able to make our CloudMD file here more shorter. So now you can see if I were to close this, this is exactly what it has modified.
05:08Right? So you can see we have our behavior guardrails, that's gonna be an h two tag, and now we have our think before coding and simplicity first,
05:17as well as the surgical changes and the goal driven executions. So you can see that all the four principles are still here, and there's no conflicts between what we have above versus what we have here. K?
05:27So you can see that's exactly how this works. Alright. So now you know exactly how to install it.
05:31Let's take a look at the clear difference between how is it different compared to all the skills that we have mentioned on this channel, like Gstack, Supa Powers, GSD, all those frameworks that we have introduced. And a clear difference is this.
05:42GSD, Suhowers, GSDTACK, they are all skills. They're all skills that are being triggered whenever we trigger them.
05:49Right? But Clawd. Md file is different.
05:51It's that we enforce those rules instead of our Claude. D file, kinda like personality embedded into the bottle's brain. That every time when it do something, we don't have to mention it.
06:00It knows that because it's embedded into its personality, that is gonna follow these four constraints every time we do something. When it asks to do do anything, like maybe helping us to writing a blog post or helping us to generate images or helping us to writing code, it's going to embed that.
06:18It's going to do this exactly like we mentioned in our CloudMD file. So that's the clear difference between the two. Now other than their types,
06:24let's talk about the functionalities. Right? Because these four principles actually cover a lot of those things that we have mentioned previously on this channel for those skills that we have mentioned, like GSTAC, superpower,
06:36and GST. How is it different, right, in terms of functionality? And you can see here that I asked AI on exactly the difference.
06:43And you can see here that rule number two and rule number three here has pointed out by AI that is uniquely different compared to superpower and GSTAC because none of them has mentioned anything about, like, adding extra stuff or staying your length or they don't really mention about these things as, like, the constraints.
06:59They both teach how to work carefully, but they don't know how much, like, to do. Right? Your guardrails here, which is, you know, our CloudMD file here, fix that gap by mentioning these things.
07:08Right? And we also have something that's similar to what we have with superpower g stack is rule number one and rule number four, which is think people coding and goal driven. Right?
07:16That's exactly what spectrum development does. It's creating the plan before doing executions. And what superpower and g stack does different is not just bunch of text sets inside of a CloudMD file, it's a framework that we have to first write our spec.
07:31From spec created a to do list, and from to do list creating a action. Right? That's exactly what superpower and g stack does.
07:38It's creating a framework that large numbers model here follow, but it doesn't built into the brain. But most of them are very similar. Right?
07:44The same rule, the same concept is very similar between the two. But that's why my recommendation, my workflow is combining the all of them.
07:52Right? Combining the two. Not just showing them the constraints, but also giving them the path on exactly which skill to trigger.
07:59For example, each of the principles that Karpathy has mentioned, like think before coding, like don't assume, like, service the the trade off before writing code, we will give them the path on exactly what skill to trigger. For example, just couple of MD files is not gonna cut it.
08:14We're gonna let them to basically direct them to trigger the superpower skills. Like, for example, the superpower brainstorming skill for adding new features. Or if it's like bug, error, or test, like, test error, like test failure, we're gonna have them trigger the superpower system debugging skill.
08:29If it's a multi step, like three files, we're just gonna directly having to trigger the writing plan skill or the GSD planning phase skill. Basically, try to
08:39execute it really fast, creating a to do list and try to execute it. Right? And for simplicity first, there's actually bunch of skills for simplicity, like making code more simplified, like minimize the code that solves the problem, nothing speculative.
08:52So you can see before committing, polish. So whenever we try to commit things, okay, well, let's trigger the Symbolize skill and try to Symbolize everything. Alright.
08:59So pretty much that's it for this video and alright. So you can see that's pretty much it for this video. And if you do find this video, please make sure to like this video, consider subscribing for more content like this.
09:08But with that being said, I will see you in the next video. And honestly, don't even stop there. You can also include in G Stack, like the auto plan skill, where you can do have different roles here to introduce for think before coding.
09:18The possibility here is is endless. Right? You can actually add a lot of things in here.
09:22For example, there's also surgical changes. You can also add, like, using different work trees for, you know, breaking it into different environments, and there's also goal
09:31driven executions. Right? Making sure that we're setting a clear goal, right, for the success criteria.
09:37So implement a feature or bug fix. Okay. Well, let's trigger the test driven developments here.
09:41If it's like executing a a written plan, well, let's do the executing plans. Right? So there's actually a lot of skills that does that.
09:48For example, if we want to do a security review, there's also security review. There's also data audits. There's also QA.
09:53CTASo we'll give them path to the skills that we have and making sure that not only following the constraints, but also calling the right skills to act on it. Right? So you can see the possibility here is endless, and you can just pick the skill that you want and just add it into your cloud.me file, and Cloud knows exactly what skill is gonna trigger based on your preference.
10:10CTAOkay. So pretty much that's it for this video. And, honestly, I don't want to have my CloudMD file here to be too long, so I just wanted to keep it short.
10:18CTAJust keep some skills that I really like inside of our CloudMD file. Alright. So you can see that's exactly the engine capacity skills.
10:24CTAAnd, of course, if you're interested in learning more about spectrum data frameworks, be sure to check out the playlist here inside of the description below where I show you all the spectrum data frameworks that I've talked about on this channel on how you can be able to make your large entry model here to be highly accurate when performing task on your project.
10:39CTARight? So if you're interested for that, uh, make sure to check it out in the link in the description below. But with that being said, if you do feel like this video, please make sure to like this video, Consider subscribing for more content like this.
— full transcript
§ 05 · For Joe
The unlock is the wiring, not the install.
Claude Code CLAUDE.md playbook
Karpathy's four rules do nothing in isolation — the real move is routing each rule to the specific skill that operationalizes it.
- Install the karpathy-skills append on every existing CLAUDE.md project — takes 30 seconds, ask Claude to merge conflicts.
- Treat CLAUDE.md as the always-on personality layer; treat skills (Superpowers, GSD) as the workflow layer above it.
- Map each principle to a skill trigger: brainstorm → Superpowers, multi-step → GSD plan, simplify → simplify skill pre-commit, goal-driven → TDD or security-review.
- Keep the CLAUDE.md short — less to read means the model actually follows it. Strip meta-commentary and duplicates after every install.
- The JoeFlow CLAUDE.md already implements most of this. Run the append, let Claude self-merge, and you're ahead of 99% of users.
§ 05 · For You
What this means for your Claude Code projects.
If you use Claude Code
Four rules in your CLAUDE.md make Claude meaningfully better at not wrecking your codebase.
- Add the karpathy-skills rules to any existing project in under a minute: one curl command + a merge pass.
- The model stops assuming and starts asking — you get fewer 1000-line rewrites when you wanted a 20-line fix.
- Surgical changes means Claude stops touching code you did not ask about. Alone, that is worth the install.
- If you already use Superpowers or GSD, wire the principles to those skills so Claude always knows which workflow to kick off.
- Check the repo: github.com/multica-ai/andrej-karpathy-skills — it's free, MIT-licensed, and merges cleanly.
