Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

🤯 Andrej Karpathy's coding rules have officially broken the internet. [BOOKMARK THIS NOW] 144,000 stars. #1 on GitHub for 28 days straight. But 99% of people still haven't heard of them. Here's what a CLAUDE.md ACTUALLY is, and why it quietly fixed the biggest problem with AI coding: It's... a text file Claude reads before it touches your code. Standing instructions. It never forgets them. The 4 rules that went viral: - Think before coding. State assumptions. Ask when unsure. Never guess. - Simplicity first. Minimum code that solves the problem. Nothing extra. - Surgical changes. Touch only what was asked. Every line traces back to the request. - Goal-driven. Turn vague instructions into a test that proves it works, before writing code. The dev who built it says it took his accuracy from ~65% to ~94%. The rules aren't the interesting part though. The interesting part is that almost nobody knows you can do this at all.show more

Coin Bureau

1,110,976 subscribers

59,130 views • 1 month ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

GITHUB JUST KILLED THE WORST PART OF VIBE CODING they shipped a free tool called Spec Kit and it already crossed 120,000 stars the fix is stupidly simple instead of tossing vague prompts at an agent and praying it doesn't wreck your project Spec Kit makes the AI write a full structured spec before it touches a single line of code it works through the problem first figures out what you want to build asks about the gaps lays out the project then it starts coding you get fewer insane bugs, cleaner output and results you can predict the flow looks like this: /constitution for your rules and standards /specify for what you want to build /clarify for the open questions before you start /plan for architecture and stack /tasks for the ordered work /implement to run it it plugs into Claude Code, Cursor, Copilot, Codex, Gemini CLI and 25+ other agents 120,000 stars, 10,000 forks, open source, shipped by GitHub itself learning to drive agents like this is most of what separates people getting hired as AI engineers from everyone still fighting their prompts

GITHUB JUST KILLED THE WORST PART OF VIBE CODING they shipped a free tool called Spec Kit and it already crossed 120,000 stars the fix is stupidly simple instead of tossing vague prompts at an agent and praying it doesn't wreck your project Spec Kit makes the AI write a full structured spec before it touches a single line of code it works through the problem first figures out what you want to build asks about the gaps lays out the project then it starts coding you get fewer insane bugs, cleaner output and results you can predict the flow looks like this: /constitution for your rules and standards /specify for what you want to build /clarify for the open questions before you start /plan for architecture and stack /tasks for the ordered work /implement to run it it plugs into Claude Code, Cursor, Copilot, Codex, Gemini CLI and 25+ other agents 120,000 stars, 10,000 forks, open source, shipped by GitHub itself learning to drive agents like this is most of what separates people getting hired as AI engineers from everyone still fighting their prompts

Atlas

479,804 views • 3 days ago

Simplicity is at the heart of great software. This is one of the reasons why Claude Code has been sticky for me. As a builder, I love planning and brainstorming, and this is now a key focus of Claude Code. I use Shift + Tab a lot to cycle between brainstorming, planning, and execution. This functionality provides the appropriate interface for me to either be very involved or less involved as I please. This works particularly well when building out new and complex features or entire new projects. This saves a huge amount of time. It allows me to tune Claude Code to execute and build more effectively. It also builds a loop of trust, and I often (surprisingly) find Claude Code asking for clarifications when it's confused. Coding agents don't normally do that. I have shared before on the power of brainstorming with AI for longer times. Try it and you will not be disappointed. Vibe coding is fun, but pair it with intentional development cycles, and you watch how far you can take a project with coding agents today.

Simplicity is at the heart of great software. This is one of the reasons why Claude Code has been sticky for me. As a builder, I love planning and brainstorming, and this is now a key focus of Claude Code. I use Shift + Tab a lot to cycle between brainstorming, planning, and execution. This functionality provides the appropriate interface for me to either be very involved or less involved as I please. This works particularly well when building out new and complex features or entire new projects. This saves a huge amount of time. It allows me to tune Claude Code to execute and build more effectively. It also builds a loop of trust, and I often (surprisingly) find Claude Code asking for clarifications when it's confused. Coding agents don't normally do that. I have shared before on the power of brainstorming with AI for longer times. Try it and you will not be disappointed. Vibe coding is fun, but pair it with intentional development cycles, and you watch how far you can take a project with coding agents today.

elvis

81,765 views • 8 months ago

you need to tattoo this Boris Cherny quote into your brain: "coding is the easy part, it's knowing the domain that's the hard part" every week a new startup drops a launch video saying they "killed influencer marketing" or something but they don't get it. creating the thing is NOT the hard part it's understanding what thing you have to create, at what moment, and in what way and that takes years of pattern recognition from actually being in the arena and seeing what works AI can't shortcut that for you

you need to tattoo this Boris Cherny quote into your brain: "coding is the easy part, it's knowing the domain that's the hard part" every week a new startup drops a launch video saying they "killed influencer marketing" or something but they don't get it. creating the thing is NOT the hard part it's understanding what thing you have to create, at what moment, and in what way and that takes years of pattern recognition from actually being in the arena and seeing what works AI can't shortcut that for you

Ole Lehmann

47,738 views • 2 months ago

I genuinely don't understand why everyone isn't using this yet Andrej Karpathy, a co-founder of OpenAI, posted a simple idea that hit 16 million views: stop using AI to write code, use it to build a second brain. You point Claude Code at a folder, drop in any source, an article, a transcript, a PDF, and Claude reads it, links it, and files it into a living wiki of everything you know. It compounds like interest, the more you feed it, the smarter it gets. Here's the whole thing: > Install Obsidian, create a vault, open it in Claude Code > Paste Karpathy's wiki idea file and tell Claude to build it > Claude makes three folders: raw for sources, wiki for its pages, a CLAUDE.md that runs it > Drop any source into raw and say "ingest this" > Ask questions across everything, forever Five minutes to set up, and you never start from a blank chat again. Full step-by-step guide with Claude and Obsidian, link below. Bookmark this

I genuinely don't understand why everyone isn't using this yet Andrej Karpathy, a co-founder of OpenAI, posted a simple idea that hit 16 million views: stop using AI to write code, use it to build a second brain. You point Claude Code at a folder, drop in any source, an article, a transcript, a PDF, and Claude reads it, links it, and files it into a living wiki of everything you know. It compounds like interest, the more you feed it, the smarter it gets. Here's the whole thing: > Install Obsidian, create a vault, open it in Claude Code > Paste Karpathy's wiki idea file and tell Claude to build it > Claude makes three folders: raw for sources, wiki for its pages, a CLAUDE.md that runs it > Drop any source into raw and say "ingest this" > Ask questions across everything, forever Five minutes to set up, and you never start from a blank chat again. Full step-by-step guide with Claude and Obsidian, link below. Bookmark this

Ridark

6,826,512 views • 25 days ago

Karpathy method + Claude Code reading your whole Obsidian vault is the smartest second brain on earth. The method is simple and brutal. If you can’t build a thing from scratch, you don’t know it. Tutorials are fake learning and your brain deletes them in 3 days. Most people ignore this. They build a second brain that just sits there, folders of notes nobody reopens, dead text. Point Claude Code at the vault and it wakes up. 5,000 notes, one mind. It reads all of it and answers in your own words and your own proofs, not a model’s guess. Then the loop closes. Want to understand neural nets? Skip the 3-hour video and ask Claude Code to build a tiny one. 200 lines from scratch. Watch it train, break a layer, watch it fail, fix it. It clicks in 20 minutes instead of 3 weeks. The second it lands the note gets written. One idea per file, linked to 10 others, dropped into the vault while the memory is still hot. Now it compounds. Month 1: is 60 notes. Month 6 is 900. Every new note pulls in old ones, so you ask anything and the answer comes from your brain, not the internet. Before: 40 tabs, 6 half read PDF, 0 retained. After: build it once, own it for life. Setup takes 4 minutes. Plain text, no lock-in. A second brain nobody reads is a graveyard. Yours just started thinking.

Karpathy method + Claude Code reading your whole Obsidian vault is the smartest second brain on earth. The method is simple and brutal. If you can’t build a thing from scratch, you don’t know it. Tutorials are fake learning and your brain deletes them in 3 days. Most people ignore this. They build a second brain that just sits there, folders of notes nobody reopens, dead text. Point Claude Code at the vault and it wakes up. 5,000 notes, one mind. It reads all of it and answers in your own words and your own proofs, not a model’s guess. Then the loop closes. Want to understand neural nets? Skip the 3-hour video and ask Claude Code to build a tiny one. 200 lines from scratch. Watch it train, break a layer, watch it fail, fix it. It clicks in 20 minutes instead of 3 weeks. The second it lands the note gets written. One idea per file, linked to 10 others, dropped into the vault while the memory is still hot. Now it compounds. Month 1: is 60 notes. Month 6 is 900. Every new note pulls in old ones, so you ask anything and the answer comes from your brain, not the internet. Before: 40 tabs, 6 half read PDF, 0 retained. After: build it once, own it for life. Setup takes 4 minutes. Plain text, no lock-in. A second brain nobody reads is a graveyard. Yours just started thinking.

West Lord

585,056 views • 18 days ago

I just built a Meta Ads diagnostic in Claude Code that tells you WHY your account broke, not just what changed 🤯 It spins up a team of agents that each investigate a different reason performance dropped, then argue against each other to kill the wrong answer before it ever reaches you. All inside Claude Code. Perfect for DTC brands and agencies who panic-kill creative the second CPA spikes. If you've watched ROAS fall off a cliff and opened Ads Manager with ten tabs going, you already know what happens next. Your gut says "creative fatigue." You kill your best-performing ad. A week later performance is still broken, because that was never the problem. Guessing wrong is the most expensive move in paid social. This workflow ends the guessing: → One agent investigates each competing theory — creative fatigue, budget and delivery changes, traffic quality, offer and seasonality → Each one is blind to the others, reasoning only from its own slice of the data so they can't bias each other → A refuter agent then attacks every surviving theory and tries to kill it → A theory only stands if the data can't disprove it → You get a ranked diagnosis: the real cause, the evidence for and against it, and the one move to make this week No anchoring on the first obvious answer. No killing winning creative on a hunch. No "here's what happened" reports that never tell you why. What you get: → Every theory tested in parallel instead of one biased guess → An adversarial pass that kills the wrong answer before you act on it → A ranked diagnosis with confidence levels and evidence both ways → A reusable workflow you drop next month's export into and re-run Built 100% in Claude Code with the new dynamic workflows. The first account I ran it on looked like textbook creative fatigue. The workflow disagreed, and traced the real cause to a budget change that had doubled spend and flooded delivery with junk traffic. I put together a full playbook with the exact workflow, the prompt, and how to run it on your own account. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

I just built a Meta Ads diagnostic in Claude Code that tells you WHY your account broke, not just what changed 🤯 It spins up a team of agents that each investigate a different reason performance dropped, then argue against each other to kill the wrong answer before it ever reaches you. All inside Claude Code. Perfect for DTC brands and agencies who panic-kill creative the second CPA spikes. If you've watched ROAS fall off a cliff and opened Ads Manager with ten tabs going, you already know what happens next. Your gut says "creative fatigue." You kill your best-performing ad. A week later performance is still broken, because that was never the problem. Guessing wrong is the most expensive move in paid social. This workflow ends the guessing: → One agent investigates each competing theory — creative fatigue, budget and delivery changes, traffic quality, offer and seasonality → Each one is blind to the others, reasoning only from its own slice of the data so they can't bias each other → A refuter agent then attacks every surviving theory and tries to kill it → A theory only stands if the data can't disprove it → You get a ranked diagnosis: the real cause, the evidence for and against it, and the one move to make this week No anchoring on the first obvious answer. No killing winning creative on a hunch. No "here's what happened" reports that never tell you why. What you get: → Every theory tested in parallel instead of one biased guess → An adversarial pass that kills the wrong answer before you act on it → A ranked diagnosis with confidence levels and evidence both ways → A reusable workflow you drop next month's export into and re-run Built 100% in Claude Code with the new dynamic workflows. The first account I ran it on looked like textbook creative fatigue. The workflow disagreed, and traced the real cause to a budget change that had doubled spend and flooded delivery with junk traffic. I put together a full playbook with the exact workflow, the prompt, and how to run it on your own account. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

12,670 views • 1 month ago

THIS GUY IS RUNNING CLAUDE CODE ON A NINTENDO 3DS imagine vibe coding a startup from a handheld console that came out in 2011 he built a native SSH terminal for it from scratch in C. GPU-rendered, custom VT100 parser with full truecolor. even added a Nerd Font bitmap atlas so it looks exactly like his desktop terminal the 3DS connects to his Mac over SSH and runs Claude Code straight from it you can now play pokemon while you vibe code all on the same system

THIS GUY IS RUNNING CLAUDE CODE ON A NINTENDO 3DS imagine vibe coding a startup from a handheld console that came out in 2011 he built a native SSH terminal for it from scratch in C. GPU-rendered, custom VT100 parser with full truecolor. even added a Nerd Font bitmap atlas so it looks exactly like his desktop terminal the 3DS connects to his Mac over SSH and runs Claude Code straight from it you can now play pokemon while you vibe code all on the same system

Om Patel

77,692 views • 3 months ago

Your Claude Code setup is probably bloated and you don't even know it. Every MCP server you add loads its full tool list into your context window the second your session starts. Stack too many and you're burning context before you type a word. So the move was never "add more." It's "add the right ones." Anthropic dropped an official plugin that does exactly that. It scans your actual codebase and tells you what's worth adding across all five layers: → hooks → skills → MCP servers → subagents → slash commands React project? It suggests Playwright. Auth code? It flags a security reviewer. It's read-only. Touches nothing. Just hands you the blueprint. The plugin isn't the edge. Knowing it exists is. /plugin install claude-code-setup@claude-plugins-official Steal this before everyone does.

Your Claude Code setup is probably bloated and you don't even know it. Every MCP server you add loads its full tool list into your context window the second your session starts. Stack too many and you're burning context before you type a word. So the move was never "add more." It's "add the right ones." Anthropic dropped an official plugin that does exactly that. It scans your actual codebase and tells you what's worth adding across all five layers: → hooks → skills → MCP servers → subagents → slash commands React project? It suggests Playwright. Auth code? It flags a security reviewer. It's read-only. Touches nothing. Just hands you the blueprint. The plugin isn't the edge. Knowing it exists is. /plugin install claude-code-setup@claude-plugins-official Steal this before everyone does.

Evan Luthra

36,455 views • 19 days ago

SOMEONE TURNED 33 PILES OF DEAD BOOKMARKS INTO A GRAVITY MAP CLAUDE REBUILDS ITSELF EVERY NIGHT - AND IT RUNS ON THE 80% OF CLAUDE NOBODY TOUCHES most people drive Claude Code like a chatbot with file access - type a prompt, watch it edit, move on. that's maybe 20% of the tool this is the opposite. she's not typing at Claude. she's running it - loops on a mac mini overnight, claude linking every node while she sleeps the gravity map in the video is just the 80% maxed out: 1 system that organizes itself, not a human babysitting a chat box the other 80% is a steering layer Anthropic shipped quietly on june 18 - 7 ways to instruct the model, and a stack of commands almost nobody opens /context to see your bloat. /clear between tasks. path-scoped rules, subagents, hooks - conventions that load themselves the exact second they matter i stopped typing at Claude months ago - now i configure it once and it shows up already running the work, 10x cleaner a prompt helps for 1 message. the steering layer pays you back every session, for life the people who learn it stop being users and become operators - everyone else is still arguing about which model is smartest the article below is the full map - all 4 layers, every file and command, start to finish

SOMEONE TURNED 33 PILES OF DEAD BOOKMARKS INTO A GRAVITY MAP CLAUDE REBUILDS ITSELF EVERY NIGHT - AND IT RUNS ON THE 80% OF CLAUDE NOBODY TOUCHES most people drive Claude Code like a chatbot with file access - type a prompt, watch it edit, move on. that's maybe 20% of the tool this is the opposite. she's not typing at Claude. she's running it - loops on a mac mini overnight, claude linking every node while she sleeps the gravity map in the video is just the 80% maxed out: 1 system that organizes itself, not a human babysitting a chat box the other 80% is a steering layer Anthropic shipped quietly on june 18 - 7 ways to instruct the model, and a stack of commands almost nobody opens /context to see your bloat. /clear between tasks. path-scoped rules, subagents, hooks - conventions that load themselves the exact second they matter i stopped typing at Claude months ago - now i configure it once and it shows up already running the work, 10x cleaner a prompt helps for 1 message. the steering layer pays you back every session, for life the people who learn it stop being users and become operators - everyone else is still arguing about which model is smartest the article below is the full map - all 4 layers, every file and command, start to finish

KingWilliam

12,305 views • 21 days ago

ANTHROPIC JUST TURNED AI AGENTS INTO GIT REPOS Anthropic shipped "ant" - a CLI that runs every Claude API endpoint straight from your terminal. The headline isn't the terminal access. It's that you can now version-control an AI agent as YAML in Git and have CI sync it to the Claude Platform, the same way you ship code. - Every API resource is a subcommand: messages, models, files, agents, sessions - Define an agent in a YAML file, check it into your repo, and keep it in sync with one update command - Spin up a session, send it an event, then pull every event and tool call back from the same CLI - Claude Code knows how to drive ant out of the box - it shells out and reads the results with no glue code Agents just stopped being prompts you babysit and became infrastructure you deploy.

ANTHROPIC JUST TURNED AI AGENTS INTO GIT REPOS Anthropic shipped "ant" - a CLI that runs every Claude API endpoint straight from your terminal. The headline isn't the terminal access. It's that you can now version-control an AI agent as YAML in Git and have CI sync it to the Claude Platform, the same way you ship code. - Every API resource is a subcommand: messages, models, files, agents, sessions - Define an agent in a YAML file, check it into your repo, and keep it in sync with one update command - Spin up a session, send it an event, then pull every event and tool call back from the same CLI - Claude Code knows how to drive ant out of the box - it shells out and reads the results with no glue code Agents just stopped being prompts you babysit and became infrastructure you deploy.

BuBBliK

200,080 views • 1 month ago

Nobody comes into my office and says they've been losing ground for years. They come in for a knee or a shoulder. But when you ask the right questions, a different story emerges. They stopped hiking because it got too hard. They gave up tennis. They hesitate before the stairs they used to take without thinking. They've quietly rearranged their lives around what they can no longer do... and most of them didn't notice it happening. This is what I think of as the narrowing of people's lives. It's not a dramatic event. Instead, it's a gradual shrinking of what's physically possible, so slow that people mistake the adaptation for a choice. It wasn't a choice. It was the slow, quiet disappearance of capacity that nobody warned them to protect. They normalized all the changes and attributed them solely to aging. The narrowing is not inevitable!! Dammit... it's not ;-)! But it requires intention to resist because the body will not hold the capacity to do things you do not train, and the losses accumulate in silence until they don't.

Nobody comes into my office and says they've been losing ground for years. They come in for a knee or a shoulder. But when you ask the right questions, a different story emerges. They stopped hiking because it got too hard. They gave up tennis. They hesitate before the stairs they used to take without thinking. They've quietly rearranged their lives around what they can no longer do... and most of them didn't notice it happening. This is what I think of as the narrowing of people's lives. It's not a dramatic event. Instead, it's a gradual shrinking of what's physically possible, so slow that people mistake the adaptation for a choice. It wasn't a choice. It was the slow, quiet disappearance of capacity that nobody warned them to protect. They normalized all the changes and attributed them solely to aging. The narrowing is not inevitable!! Dammit... it's not ;-)! But it requires intention to resist because the body will not hold the capacity to do things you do not train, and the losses accumulate in silence until they don't.

Howard Luks MD

76,768 views • 4 months ago

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

elvis

18,374 views • 2 months ago

SOMEONE BUILT A CLAUDE CODE PLUGIN THAT REFUSES TO WORK UNTIL YOU DO PUSH-UPS OR SQUATS its called workout gate and it is exactly as cursed as it sounds when the hook fires, it blocks your prompt, opens your webcam, and makes you exercise to keep coding > it counts your reps live through the webcam with mediapipe, no honor system rounding down > only releases your prompt once you actually finish the reps > quit halfway and the leftover reps get saved as debt for your next session > chill, demo and hardcore presets, plus prompt based, time based or random triggers > tracks stats, streaks and personal records right in the claude code statusline we automated the coding, now we're automating the part where we actually take care of ourselves

SOMEONE BUILT A CLAUDE CODE PLUGIN THAT REFUSES TO WORK UNTIL YOU DO PUSH-UPS OR SQUATS its called workout gate and it is exactly as cursed as it sounds when the hook fires, it blocks your prompt, opens your webcam, and makes you exercise to keep coding > it counts your reps live through the webcam with mediapipe, no honor system rounding down > only releases your prompt once you actually finish the reps > quit halfway and the leftover reps get saved as debt for your next session > chill, demo and hardcore presets, plus prompt based, time based or random triggers > tracks stats, streaks and personal records right in the claude code statusline we automated the coding, now we're automating the part where we actually take care of ourselves

Om Patel

669,084 views • 1 month ago

Only your TWIN FLAME holds the key to your heart - not because you gave it away, but because it was never meant to be locked from them. No matter the distance, the silence, or the timing, there is a space within you that only their energy can reach. It's not obsession. It's recognition. It's soul memory. The kind that defies logic, yet brings you back to life every time. If your heart still beats in rhythm with theirs — trust it. This love was written long before this lifetime. ✨🙌🏾💫 © twinflames_infinity

Only your TWIN FLAME holds the key to your heart - not because you gave it away, but because it was never meant to be locked from them. No matter the distance, the silence, or the timing, there is a space within you that only their energy can reach. It's not obsession. It's recognition. It's soul memory. The kind that defies logic, yet brings you back to life every time. If your heart still beats in rhythm with theirs — trust it. This love was written long before this lifetime. ✨🙌🏾💫 © twinflames_infinity

🧬Maxpein🧬

27,961 views • 11 months ago

one of my favorite ways to use claude code skills right now - combining remotion with claude-in-chrome for motion video creation. the workflow is addictive. the clip you see here was produced with minimal prompting effort let me know if you would like me to write a full break down of this process. you describe to claude code what you want, claude code writes the remotion components, opens the remotion studio (via browser) with claude-in-chrome, sees the actual rendered output, and iterates on it in real time. need the arrows pointing to the center of the bubbles instead of the edge? just say it. need the layout shifted to the center? say it. claude sees the preview, adjusts the code, re-renders. then when you're happy you tell claude code to render the final video. but skills are what make this possible. remotion knowledge + browser automation + the taste to iterate visually. no copy pasting screenshots back and forth. no "can you try moving it 10px to the right" over chat. it just looks and fixes. this is the kind of workflow that makes you realize how much further claude code can go beyond just writing code in a terminal. i didn't touch any code while working on the clip you see if you haven't tried combining skills together like this - start experimenting. the skills combos is where the magic is at.

one of my favorite ways to use claude code skills right now - combining remotion with claude-in-chrome for motion video creation. the workflow is addictive. the clip you see here was produced with minimal prompting effort let me know if you would like me to write a full break down of this process. you describe to claude code what you want, claude code writes the remotion components, opens the remotion studio (via browser) with claude-in-chrome, sees the actual rendered output, and iterates on it in real time. need the arrows pointing to the center of the bubbles instead of the edge? just say it. need the layout shifted to the center? say it. claude sees the preview, adjusts the code, re-renders. then when you're happy you tell claude code to render the final video. but skills are what make this possible. remotion knowledge + browser automation + the taste to iterate visually. no copy pasting screenshots back and forth. no "can you try moving it 10px to the right" over chat. it just looks and fixes. this is the kind of workflow that makes you realize how much further claude code can go beyond just writing code in a terminal. i didn't touch any code while working on the clip you see if you haven't tried combining skills together like this - start experimenting. the skills combos is where the magic is at.

elvis

46,426 views • 5 months ago

SOMEONE JUST VIBECODED A PROGRAM THAT DOWNLOADS ANY WEBSITE ON THE INTERNET every $35,000 agency site is now yours to rip clean for $0 fully open source, save it before it's gone you paste one url and it does the rest: → crawls the entire site → grabs every file: html, css, js, images, even the fonts → rewrites every link to run fully offline → packs it all into a downloadable zip runs entirely in the browser, nothing to install or sign up for point it at any site you admire and the whole front-end is yours: → clone it → archive it before it dies → crack open exactly how it was built the thing agencies gatekeep for five figures is now a 10-second download bookmark this one

SOMEONE JUST VIBECODED A PROGRAM THAT DOWNLOADS ANY WEBSITE ON THE INTERNET every $35,000 agency site is now yours to rip clean for $0 fully open source, save it before it's gone you paste one url and it does the rest: → crawls the entire site → grabs every file: html, css, js, images, even the fonts → rewrites every link to run fully offline → packs it all into a downloadable zip runs entirely in the browser, nothing to install or sign up for point it at any site you admire and the whole front-end is yours: → clone it → archive it before it dies → crack open exactly how it was built the thing agencies gatekeep for five figures is now a 10-second download bookmark this one

Argona

121,691 views • 11 days ago

i tried Framer Agent to build a brand guidelines website template, something i've meant to do for a while. a site i can swap a logo, nudge a colour, update the type, and send a link instead of re-exporting a pdf nobody opens. a few observations on the AI process: - i started with references. pulled together a handful of minimalist grid layouts and had Claude describe the visual style back to me. you can do the same inside Framer, feeding it the references directly. - from there i had it write a detailed prompt aimed at that exact style, then asked it to break it into a few smaller steps. then i fed those into the agent, one at a time. - the scaffolding stage is the satisfying part. for something this grid-driven (the columns, the spans, the whole underlying structure) watching it land in seconds is hard to look away from. - but then i still have to sweat the details: text alignment, line-heights, image sizes. i don't mind it at all; it's the part i like, making these design decisions. the strength of the agent is the mundane work. point it at the stuff that eats your time: cleaning up the build, adding responsiveness, dropping in small effects, checking text and colour styles stay consistent, writing alt text for every image. then i get the time back for the parts of web design that are actually fun. 🤝

charlota

34,421 views • 22 days ago

I just built a Meta ad policy checker in Claude Code that catches rejections BEFORE Meta does 🤯 Drop in your ad copy → it pulls Meta's LIVE Advertising Standards, checks every line against the actual policy text, and hands each ad a verdict: Cleared for launch, Fix before launch, or Grounded. All inside Claude Code. Perfect for media buyers and DTC brands who've had ads bounced — or an account restricted — and never got a straight answer why. If you're finding out about policy problems only after the rejection email, resubmitting the same ad and praying, losing days of delivery while the appeal sits in review, and every bounce quietly teaches Meta to trust your account a little less... This runs the review before Meta ever sees the ad: → Drop in your ad copy (one ad or a whole batch) → It reads each ad and figures out which of Meta's policies apply → Scrapes the live policy pages from Meta's Transparency Center → Flags the exact phrase that violates, with Meta's own policy quoted next to it → Rewrites the risky lines so the message survives but the violation doesn't → Renders a dashboard: every ad, every finding, every fix in one place No guessing which word killed the ad. No resubmit-and-pray loops. No stacking rejections on your account history. What you get: → A verdict on every ad before you spend a dollar → The violating phrase + the policy citation, side by side → Rewrites that keep the selling intent → A report you can hand straight to your team or client Built 100% in Claude Code. No API keys, no Meta login. I'm giving away the complete Claude skill file. Want the skill for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

I just built a Meta ad policy checker in Claude Code that catches rejections BEFORE Meta does 🤯 Drop in your ad copy → it pulls Meta's LIVE Advertising Standards, checks every line against the actual policy text, and hands each ad a verdict: Cleared for launch, Fix before launch, or Grounded. All inside Claude Code. Perfect for media buyers and DTC brands who've had ads bounced — or an account restricted — and never got a straight answer why. If you're finding out about policy problems only after the rejection email, resubmitting the same ad and praying, losing days of delivery while the appeal sits in review, and every bounce quietly teaches Meta to trust your account a little less... This runs the review before Meta ever sees the ad: → Drop in your ad copy (one ad or a whole batch) → It reads each ad and figures out which of Meta's policies apply → Scrapes the live policy pages from Meta's Transparency Center → Flags the exact phrase that violates, with Meta's own policy quoted next to it → Rewrites the risky lines so the message survives but the violation doesn't → Renders a dashboard: every ad, every finding, every fix in one place No guessing which word killed the ad. No resubmit-and-pray loops. No stacking rejections on your account history. What you get: → A verdict on every ad before you spend a dollar → The violating phrase + the policy citation, side by side → Rewrites that keep the selling intent → A report you can hand straight to your team or client Built 100% in Claude Code. No API keys, no Meta login. I'm giving away the complete Claude skill file. Want the skill for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

16,093 views • 3 days ago

WHY ARE WE STILL ALLOWING BILL GATES TO THINK HE CAN RULE THE REST OVER THE REST OF US? WHO GAVE GATES THE RIGHT TO DECIDE WHAT HUMAN BEINGS STILL MATTER AND WHICH ONES DO NOT? Bill Gates just said humans won’t be needed for most things. And that ”we’ll decide” who still matters. WHO IS THE 'WE'? Let that sit for a second. The man who helped build the digital world is now casually announcing that the people living in it might be optional. No panic. No apology. Just a quiet admission from someone who has never had to worry about being replaced. The scariest part is not the AI. It’s the ”we.” Who is ”we,” Bill? Because it is not the people whose jobs disappear next year. This is not a tech problem. It’s a power problem dressed up as progress. When the people building the tools also decide who needs them, the rest of us are just passengers. Do you trust the people at the top to make that call for you? Courtesy - Captains Obvious

WHY ARE WE STILL ALLOWING BILL GATES TO THINK HE CAN RULE THE REST OVER THE REST OF US? WHO GAVE GATES THE RIGHT TO DECIDE WHAT HUMAN BEINGS STILL MATTER AND WHICH ONES DO NOT? Bill Gates just said humans won’t be needed for most things. And that ”we’ll decide” who still matters. WHO IS THE 'WE'? Let that sit for a second. The man who helped build the digital world is now casually announcing that the people living in it might be optional. No panic. No apology. Just a quiet admission from someone who has never had to worry about being replaced. The scariest part is not the AI. It’s the ”we.” Who is ”we,” Bill? Because it is not the people whose jobs disappear next year. This is not a tech problem. It’s a power problem dressed up as progress. When the people building the tools also decide who needs them, the rest of us are just passengers. Do you trust the people at the top to make that call for you? Courtesy - Captains Obvious

BelannF

14,510 views • 3 months ago

My project has 39,205 lines of code, and Cursor can't answer questions about it. Cursor's context seems to be capped at around 10,000 tokens. Unfortunately, this is not enough for any decent-sized project. If you have a large codebase, check out Augment Code. This thing is faaaast! I'm currently using their Visual Studio Code plugin, but you can also use them on JetBrains, Neovim, and even Vim. (I'm a Neovim fan, but Copilot's implementation for Neovim is nowhere as good as Augment Code.) Augment Code was gracious enough to sponsor this post. After you install their extension and run it for the first time, it will index your entire codebase. This is why it can answer questions as fast as it does, regardless of the size of your codebase. Augment Code supports chat and completions like every other AI coding assistant, but its killer feature is "Next Edit." When you make a change, two things happen: 1. The model analyzes the change to determine the ripple effects across your *entire* codebase. 2. The model suggests everything you need to update to ensure everything works correctly. This is pretty wild!

My project has 39,205 lines of code, and Cursor can't answer questions about it. Cursor's context seems to be capped at around 10,000 tokens. Unfortunately, this is not enough for any decent-sized project. If you have a large codebase, check out Augment Code. This thing is faaaast! I'm currently using their Visual Studio Code plugin, but you can also use them on JetBrains, Neovim, and even Vim. (I'm a Neovim fan, but Copilot's implementation for Neovim is nowhere as good as Augment Code.) Augment Code was gracious enough to sponsor this post. After you install their extension and run it for the first time, it will index your entire codebase. This is why it can answer questions as fast as it does, regardless of the size of your codebase. Augment Code supports chat and completions like every other AI coding assistant, but its killer feature is "Next Edit." When you make a change, two things happen: 1. The model analyzes the change to determine the ripple effects across your entire codebase. 2. The model suggests everything you need to update to ensure everything works correctly. This is pretty wild!

Santiago

247,775 views • 1 year ago