Kirill · Launch Video Breakdown: Hook, Pacing & Motion Design

Scene-by-scene timeline & spoken transcript

1. 0:00 – 0:04

   The Hook

   GitHub Trending Spotlight

   “(No spoken dialogue — A driving, arpeggiated synth melody with a sub-bass drop/impact introduces the main theme.)”

   On screen

   forrestchang / andrej-karpathy-skills Public A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls. 82.1k stars 7.8k forks X.COM/KIRILLK_WEB3

   Camera

   Static, wide shot of a GitHub repository page, with subtle highlights on key metrics.

   Motion

   Subtle highlight animations on text elements, simulating user interaction or emphasis.

2. 0:04 – 0:09

   Problem Agitation

   Identifying LLM Pitfalls

   “(No spoken dialogue — The electronic score continues, maintaining a consistent energy.)”

   On screen

   Karpathy-Inspired Claude Code Guidelines The Problems *The models make wrong assumptions on your behalf and just run along with them without checking. They don't manage their confusion, don't seek clarifications, don't surface inconsistencies, don't present tradeoffs, don't push back when they should.* *They really like to overcomplicate code and APIs, bloat abstractions, don't clean up dead code... implement a bloated construction over 1000 lines when 100 would do.* *They still sometimes change/remove comments and code they don't sufficiently understand as side effects, even if orthogonal to the task. X.COM/KIRILLK_WEB3

   Camera

   Smooth vertical scroll down the GitHub README, revealing problem statements.

   Motion

   Continuous vertical scrolling, with text highlights appearing as the content enters the viewport.

3. 0:09 – 0:15

   Product Reveal

   The Four Principles Solution

   “(No spoken dialogue — The music builds slightly in complexity with additional synth layers.)”

   On screen

   The Solution Four principles in one file that directly address these issues: Principle Addresses Think Before Coding Wrong assumptions, hidden confusion, missing tradeoffs Simplicity First Overcomplication, bloated abstractions Surgical Changes Orthogonal edits, touching code you shouldn't Goal-Driven Execution Leverage through tests-first, verifiable success criteria The Four Principles in Detail 1. Think Before Coding Don't assume. Don't hide confusion. Surface tradeoffs. LLMs often pick an interpretation silently and run with it. This principle forces explicit reasoning: • State assumptions explicitly — If uncertain, ask rather than guess • Present multiple interpretations — Don't pick silently when ambiguity exists 2. Simplicity First Minimum code that solves the problem. Nothing speculative. Combat the tendency toward overengineering: • No features beyond what was asked • No abstractions for single-use code • No "flexibility" or "configurability" that wasn't requested • No error handling for impossible scenarios • If 200 lines could be 50, rewrite it The test: Would a senior engineer say this is overcomplicated? If yes, simplify. 3. Surgical Changes X.COM/KIRILLK_WEB3

   Camera

   Continued smooth vertical scroll, focusing on the principles table and detailed explanations.

   Motion

   Sequential highlighting of table rows and principle descriptions as the scroll progresses, drawing attention to key information.

4. 0:15 – 0:19.6

   Call to Action

   Installation & Impact

   “(No spoken dialogue — The track builds in intensity with a pronounced beat, leading into a robotic voice countdown from 3 to 1.)”

   On screen

   Install Option A: Claude Code Plugin (recommended) From within Claude Code, first add the marketplace: /plugin marketplace add forrestchang/andrej-karpathy-skills Then install the plugin: /plugin install andrej-karpathy-skills@karpathy-skills This installs the guidelines as a Claude Code plugin, making the skill available across all your projects. Option B: CLAUDE.md (per-project) New project: curl -o CLAUDE.md https://raw.githubusercontent.com/forrestchang/andrej-karpathy-skills/main/CL Existing project (append): echo "" >> CLAUDE.md curl https://raw.githubusercontent.com/forrestchang/andrej-karpathy-skills/main/CLAUDE.md >> CL Using with Cursor Key Insight From Andrej: "LLMs are exceptionally good at looping until they meet specific goals... Don't tell it what to do, give it success criteria and watch it go." The "Goal-Driven Execution" principle captures this: transform imperative instructions into declarative goals with verification loops. How to Know It's Working These guidelines are working if you see: • Fewer unnecessary changes in diffs — Only requested changes appear • Fewer rewrites due to overcomplication — Code is simple the first time • Clarifying questions come before implementation — Not after mistakes • Clean, minimal PRs — No drive-by refactoring or "improvements" Customization These guidelines are designed to be merged with project-specific instructions. Add them to your existing CLAUDE.md or create a new one. For project-specific rules, add sections like: ## Project-Specific Guidelines - Use TypeScript strict mode - All API endpoints must have tests - Follow the existing error handling patterns in 'src/utils/errors.ts' Tradeoff Note These guidelines bias toward caution over speed. For trivial tasks (simple typo fixes, obvious one-liners), use judgment — not every change needs the full rigor. The goal is reducing costly mistakes on non-trivial work, not slowing down simple tasks. License MIT X.COM/KIRILLK_WEB3

   Camera

   Rapid vertical scroll, revealing installation instructions and benefits, ending with a quick zoom out.

   Motion

   Fast-paced vertical scrolling with command-line text appearing and disappearing, simulating quick interaction. A final countdown animation with robotic voice effect.