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.

GARRY TAN PUBLISHED HIS PERSONAL CLAUDE CODE SETUP ON GITHUB. IT HIT 108,000 STARS AND AN 18 YEAR OLD WON A HACKATHON BUILDING A FULL GAME IN 2 HOURS the repo is called gstack. the president of y combinator open sourced his claude code workflow with 23 structured skills... most developers treat claude code like smart autocomplete. gstack turns it into a full pipeline for product thinking, architecture, design, qa and docs an 18 year old from bishkek used it to win the cursor hackathon. he built a multiplayer game with computer vision in 1 hour 45 minutes install is 3 commands. git clone the repo, run setup, add the skills to your claude.md. then call /office-hours, /plan-eng-review, /qa, /ship gbrain gives claude persistent memory between sessions. developers report saving 3 to 5 hours a day on routine work bookmark this and read the article belowshow more

starmex

8,316 subscribers

94,715 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

GStack is an open-source toolkit built by YC President & CEO Garry Tan that turns Claude Code into an AI engineering team — with skills for office hours, design, code review, QA, and browser testing. In this video, Garry walks through how GStack works, starting with Office Hours, a skill modeled after real YC partner sessions that pressure-tests your idea before you write a line of code. He demos it live, going from idea through adversarial review, design mockups, and automated QA in a single session.

GStack is an open-source toolkit built by YC President & CEO Garry Tan that turns Claude Code into an AI engineering team — with skills for office hours, design, code review, QA, and browser testing. In this video, Garry walks through how GStack works, starting with Office Hours, a skill modeled after real YC partner sessions that pressure-tests your idea before you write a line of code. He demos it live, going from idea through adversarial review, design mockups, and automated QA in a single session.

Y Combinator

922,755 views • 3 months ago

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this

Yarchi

811,683 views • 1 month ago

Motion graphics used to take me an hour per scene (or more) Now I'm creating them in 3-5 minutes — without After Effects, without Premiere, without writing a single line of code. I'm a former LA filmmaker (still PGA). My entire video stack is now 3 tools: Claude Code + HyperFrames (from HeyGen) + Descript Here's how the workflow runs: 1. Drop my brand style guide into a folder (colors, fonts, components Claude reuses forever) 2. Paste a line from my Descript transcript into Claude Code: "Create a scene for this part of the video" 3. Claude Code reads my brand, generates the HyperFrames scene, renders it to MP4 4. Drag the MP4 into Descript, drop it on the matching line of the transcript 5. Done. 3-5 minutes per scene. The unlock is the brand style guide. Once Claude has your colors, fonts, and reusable components, every scene inherits your look automatically. Bonus — you can take a Claude Design export (.zip), hand it to Claude Code, and it'll convert the HTML into a HyperFrames video you can render and edit. I built a GitHub repo with all the skills pre-loaded. Non-developers can clone it, open Claude Code, and be rendering scenes in under 10 minutes. Full walkthrough (20 min video) below Repo (skills + brand template + music-from-transcript plugin): Bookmark this if you make videos. The brand-style-guide pattern alone will save you hours every week. If you're a creator or operator using AI for content — share this with someone who's still living in After Effects.

JJ Englert

102,785 views • 3 months ago

A 26-YEAR-OLD AI ENGINEER WHOSE BIRMINGHAM THESIS OUTPERFORMED GOOGLE SCHOLAR BY 50% JUST SHIPPED GRAPHIFY: ONE COMMAND TURNS ANY FOLDER INTO A CLAUDE CODE SECOND BRAIN Safi Shamsi built Graphify 48 hours after Karpathy posted his LLM wiki idea. It turns any folder, codebase, docs, PDFs, into a knowledge graph Claude reads instead of grepping. Up to 43x fewer tokens per query. The trick almost nobody is using yet: one flag exports the entire graph as a fully-linked Obsidian vault. Repo: /safishamsi/graphify Setup, end to end: 1. Install: uv tool install graphifyy (or pipx install graphifyy). Verify with graphify --version. 2. Install the skill in Claude Code: graphify claude install. This wires Graphify into Claude Code so you can call it as a skill. 3. Open the folder you want mapped in Claude Code. In the terminal: graphify . It extracts every concept and builds the graph in graphify-out/. 4. Export to Obsidian: graphify . --obsidian. Writes one note per concept, every relationship as a wikilink, every node linked back to its source. 5. Open the new vault in Obsidian (Manage vaults → Open folder as a vault), or drag it as a subfolder into your existing one. That's it. Your Claude Code instance now has a navigable map of the codebase that loads instantly instead of re-reading files every session. Full step-by-step build of the Claude + Obsidian second brain in the article below. Bookmark this

A 26-YEAR-OLD AI ENGINEER WHOSE BIRMINGHAM THESIS OUTPERFORMED GOOGLE SCHOLAR BY 50% JUST SHIPPED GRAPHIFY: ONE COMMAND TURNS ANY FOLDER INTO A CLAUDE CODE SECOND BRAIN Safi Shamsi built Graphify 48 hours after Karpathy posted his LLM wiki idea. It turns any folder, codebase, docs, PDFs, into a knowledge graph Claude reads instead of grepping. Up to 43x fewer tokens per query. The trick almost nobody is using yet: one flag exports the entire graph as a fully-linked Obsidian vault. Repo: /safishamsi/graphify Setup, end to end: 1. Install: uv tool install graphifyy (or pipx install graphifyy). Verify with graphify --version. 2. Install the skill in Claude Code: graphify claude install. This wires Graphify into Claude Code so you can call it as a skill. 3. Open the folder you want mapped in Claude Code. In the terminal: graphify . It extracts every concept and builds the graph in graphify-out/. 4. Export to Obsidian: graphify . --obsidian. Writes one note per concept, every relationship as a wikilink, every node linked back to its source. 5. Open the new vault in Obsidian (Manage vaults → Open folder as a vault), or drag it as a subfolder into your existing one. That's it. Your Claude Code instance now has a navigable map of the codebase that loads instantly instead of re-reading files every session. Full step-by-step build of the Claude + Obsidian second brain in the article below. Bookmark this

Yarchi

140,729 views • 1 month ago

Claude Code Templates now has a web interface for browsing and contributing templates 🙌 What it does: Install templates for different languages/frameworks to get started with Claude Code faster. How to use: - Go to - Run: npm install -g claude-code-templates - Pick a template from the site - Copy and run the template command - Start coding with Claude Code The whole thing runs on GitHub - no fancy backend, no hidden stuff. Everything you're installing is right there in the repo for you to inspect. Contributing: Want to add your own template? Just follow the contribution guide and send a PR. Once merged, it automatically shows up on the site. That's it... nothing fancy, just something to save a few minutes when starting new projects with Claude Code Repo:

Claude Code Templates now has a web interface for browsing and contributing templates 🙌 What it does: Install templates for different languages/frameworks to get started with Claude Code faster. How to use: - Go to - Run: npm install -g claude-code-templates - Pick a template from the site - Copy and run the template command - Start coding with Claude Code The whole thing runs on GitHub - no fancy backend, no hidden stuff. Everything you're installing is right there in the repo for you to inspect. Contributing: Want to add your own template? Just follow the contribution guide and send a PR. Once merged, it automatically shows up on the site. That's it... nothing fancy, just something to save a few minutes when starting new projects with Claude Code Repo:

Daniel San

60,074 views • 1 year ago

$THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this$

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

55,345 views • 1 month ago

My friend applied to 200 tech jobs in two years. No MIT. No Stanford. Last month Anthropic offered him $750,000. I asked him how he broke in from zero. He sent me the exact video that got him in. A 4-hour course on mastering Claude Code. I watched it last night. Halfway through, I realized I've been using Claude Code completely wrong for a year. Bookmark this and read the article below. • 00:00 - Claude Code setup • 49:34 - building apps with Claude Code • 2:07:52 - prompting Claude Code • 2:46:16 - Claude Code for production

My friend applied to 200 tech jobs in two years. No MIT. No Stanford. Last month Anthropic offered him $750,000. I asked him how he broke in from zero. He sent me the exact video that got him in. A 4-hour course on mastering Claude Code. I watched it last night. Halfway through, I realized I've been using Claude Code completely wrong for a year. Bookmark this and read the article below. • 00:00 - Claude Code setup • 49:34 - building apps with Claude Code • 2:07:52 - prompting Claude Code • 2:46:16 - Claude Code for production

Roan

37,290 views • 12 days ago

THIS IS THE MOST COMPLETE CLAUDE CODE SETUP I'VE EVER SEEN someone open-sourced a full agent harness for Claude Code 38 agents. 156 skills. 72 commands. all pre-configured the kind of setup you'd spend weeks building yourself what's inside: → planner - feature implementation planning → architect - system design decisions → tdd-guide - test-driven development workflow → code-reviewer - quality and security review → security-reviewer - vulnerability analysis → build-error-resolver - fixes broken builds → refactor-cleaner - dead code cleanup → doc-updater - keeps docs in sync → chief-of-staff - communication triage → + 29 more agents 156 skills covering token optimization, memory persistence, continuous learning, verification loops, parallelization, subagent orchestration it ships with AgentShield baked in a security auditor that runs vulnerability checks on every agent action before execution works on Claude Code, Cursor, OpenCode, and Codex CLI one repo, one install, configured everywhere one warning: loading 38 agents and 156 skills into your context at once will burn your usage limits in minutes pick the 3-4 you actually need and load only those free. open-source. MIT licensed like + bookmark - you'll need this

THIS IS THE MOST COMPLETE CLAUDE CODE SETUP I'VE EVER SEEN someone open-sourced a full agent harness for Claude Code 38 agents. 156 skills. 72 commands. all pre-configured the kind of setup you'd spend weeks building yourself what's inside: → planner - feature implementation planning → architect - system design decisions → tdd-guide - test-driven development workflow → code-reviewer - quality and security review → security-reviewer - vulnerability analysis → build-error-resolver - fixes broken builds → refactor-cleaner - dead code cleanup → doc-updater - keeps docs in sync → chief-of-staff - communication triage → + 29 more agents 156 skills covering token optimization, memory persistence, continuous learning, verification loops, parallelization, subagent orchestration it ships with AgentShield baked in a security auditor that runs vulnerability checks on every agent action before execution works on Claude Code, Cursor, OpenCode, and Codex CLI one repo, one install, configured everywhere one warning: loading 38 agents and 156 skills into your context at once will burn your usage limits in minutes pick the 3-4 you actually need and load only those free. open-source. MIT licensed like + bookmark - you'll need this

self.dll

19,710 views • 3 months ago

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Khairallah AL-Awady

39,243 views • 1 month ago

Boris Cherny: "My job is to write loops." 5-day version you can copy for Claude Code Day 1: repo memory - write CLAUDE.md - include stack, test commands, code style, release rules, gotchas - add .claude/settings.json with the shell commands Claude can run Day 2: verification skill - pick 1 flow Claude keeps breaking - put the browser/API test in .claude/skills/ /scripts/ - make it return: pass/fail, failing step, screenshot/log path Day 3: commands Add these files: .claude/commands/babysit.md - checks your PRs - reads CI - handles obvious review nits - surfaces design questions .claude/commands/triage-issues.md - labels new issues - dedupes against existing ones - assigns owners .claude/commands/deploy-watch.md - checks the live app - reports regressions - avoids touching production Day 4: loops > /loop 5m /babysit > /loop 15m /triage-issues > /loop 5m /deploy-watch Day 5: overnight work - schedule /morning-report - schedule /deep-audit - write results to .claude/inbox/ - let your morning loop read from that folder The rule: every code-writing loop gets a separate verifier. Builder makes the change. Verifier runs the real app. You read the diff. Skip that and you wake up to 14 broken PRs with very confident summaries. Video: "Reflecting on a year of Claude Code" with Boris Cherny & Cat Wu

Boris Cherny: "My job is to write loops." 5-day version you can copy for Claude Code Day 1: repo memory - write CLAUDE.md - include stack, test commands, code style, release rules, gotchas - add .claude/settings.json with the shell commands Claude can run Day 2: verification skill - pick 1 flow Claude keeps breaking - put the browser/API test in .claude/skills/ /scripts/ - make it return: pass/fail, failing step, screenshot/log path Day 3: commands Add these files: .claude/commands/babysit.md - checks your PRs - reads CI - handles obvious review nits - surfaces design questions .claude/commands/triage-issues.md - labels new issues - dedupes against existing ones - assigns owners .claude/commands/deploy-watch.md - checks the live app - reports regressions - avoids touching production Day 4: loops > /loop 5m /babysit > /loop 15m /triage-issues > /loop 5m /deploy-watch Day 5: overnight work - schedule /morning-report - schedule /deep-audit - write results to .claude/inbox/ - let your morning loop read from that folder The rule: every code-writing loop gets a separate verifier. Builder makes the change. Verifier runs the real app. You read the diff. Skip that and you wake up to 14 broken PRs with very confident summaries. Video: "Reflecting on a year of Claude Code" with Boris Cherny & Cat Wu

Alpha Batcher

141,110 views • 1 month ago

Andrej Karpathy quietly shipped the best second brain idea in years not an app. a pattern. let an llm maintain a wiki of your notes. you dump sources, it reads them, links them, files them. knowledge compounds like interest. someone built it into a free claude code plugin. setup is two commands: claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian then open obsidian, open claude code in the same folder, type /wiki. that's it. your notes are now queryable by claude and they get richer every time you read something. bookmark this. best thing you'll build this weekend.

Andrej Karpathy quietly shipped the best second brain idea in years not an app. a pattern. let an llm maintain a wiki of your notes. you dump sources, it reads them, links them, files them. knowledge compounds like interest. someone built it into a free claude code plugin. setup is two commands: claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian then open obsidian, open claude code in the same folder, type /wiki. that's it. your notes are now queryable by claude and they get richer every time you read something. bookmark this. best thing you'll build this weekend.

Avid

336,969 views • 1 month ago

Complete Claude Code Training 6 HOURS. The most comprehensive Claude training on the internet. From A to Z: setup, workflow creation, website deployment, agent team creation, browser automation, client prospecting and pricing your services. All of it without writing a single line of code. In the end: you use Claude Code like a pro and you monetize your skills. Beginner or advanced, everything is there in one place, this course covers it all. It's worth more than all those $500 courses you almost bought. Keep it bookmarked and watch later.

Complete Claude Code Training 6 HOURS. The most comprehensive Claude training on the internet. From A to Z: setup, workflow creation, website deployment, agent team creation, browser automation, client prospecting and pricing your services. All of it without writing a single line of code. In the end: you use Claude Code like a pro and you monetize your skills. Beginner or advanced, everything is there in one place, this course covers it all. It's worth more than all those $500 courses you almost bought. Keep it bookmarked and watch later.

Rahul

241,976 views • 1 month ago

THIS OPERATOR REPLACED A $50,000 AUTOMATION AGENCY WITH A 3-HOUR BUIL 378 browser tabs. 47 Notion pages nobody touched in 6 months. A spreadsheet that crashes every Monday He didn't hire a dev team. He didn't buy n8n enterprise He cloned a GitHub repo, wired 3 API keys, and typed /onboard into Claude Code By day 14 his team messaged the AI OS in Slack instead of messaging him His old workflow: 3 hours of context switching, 2 hours of actual work His new workflow: 5 hours of deep work, 30 minutes of admin This is not a dashboard. This is a command center Full breakdown below ↓

THIS OPERATOR REPLACED A $50,000 AUTOMATION AGENCY WITH A 3-HOUR BUIL 378 browser tabs. 47 Notion pages nobody touched in 6 months. A spreadsheet that crashes every Monday He didn't hire a dev team. He didn't buy n8n enterprise He cloned a GitHub repo, wired 3 API keys, and typed /onboard into Claude Code By day 14 his team messaged the AI OS in Slack instead of messaging him His old workflow: 3 hours of context switching, 2 hours of actual work His new workflow: 5 hours of deep work, 30 minutes of admin This is not a dashboard. This is a command center Full breakdown below ↓

Asteri

10,194 views • 1 month ago

I just found a way to use Claude Code completely free. Claude Code is Anthropic’s terminal coding agent that usually needs a paid API key to run. But a viral GitHub project called Free Claude Code, now sitting at 37k stars, lets you skip the billing entirely. It works as a tiny proxy that sits between Claude Code and free model providers like NVIDIA NIM, OpenRouter, DeepSeek, and Gemini. Every request Claude Code would send to Anthropic gets quietly rerouted to a free model on the other side. The interface stays the same. What’s actually thinking behind it changes. Setup takes a couple of quick commands and a free API key from NVIDIA NIM or OpenRouter. Paste it into the local dashboard, pick a model, and you’re building. The catch is you’re not really using Claude anymore. But when the code ships, does the model badge matter? -- I have shared the Github Link in my free Whatsapp Community ↓

I just found a way to use Claude Code completely free. Claude Code is Anthropic’s terminal coding agent that usually needs a paid API key to run. But a viral GitHub project called Free Claude Code, now sitting at 37k stars, lets you skip the billing entirely. It works as a tiny proxy that sits between Claude Code and free model providers like NVIDIA NIM, OpenRouter, DeepSeek, and Gemini. Every request Claude Code would send to Anthropic gets quietly rerouted to a free model on the other side. The interface stays the same. What’s actually thinking behind it changes. Setup takes a couple of quick commands and a free API key from NVIDIA NIM or OpenRouter. Paste it into the local dashboard, pick a model, and you’re building. The catch is you’re not really using Claude anymore. But when the code ships, does the model badge matter? -- I have shared the Github Link in my free Whatsapp Community ↓

Vaibhav Sisinty

36,560 views • 24 days ago

Spent the day testing Claude Opus 4.7. Last month I built a design director agent for OpenClaw and now it cooks. 15 minutes in, Paper Design MCP + Claude Code had made me a rough draft. In under an hour, a Framer worthy site. My workflow: 1. Feed my agent references so it can extract design systems and lock in on my taste 2. Claude Code calls Paper Design MCP to generate the visual system (just keep the Paper app open) 3. Paper exports the assets and Claude Code then preps the build docs 4. Agent loops back, critiques, iterates Got no clue why anyone is paying $10K for a website anymore. It’s easy now.

Spent the day testing Claude Opus 4.7. Last month I built a design director agent for OpenClaw and now it cooks. 15 minutes in, Paper Design MCP + Claude Code had made me a rough draft. In under an hour, a Framer worthy site. My workflow: 1. Feed my agent references so it can extract design systems and lock in on my taste 2. Claude Code calls Paper Design MCP to generate the visual system (just keep the Paper app open) 3. Paper exports the assets and Claude Code then preps the build docs 4. Agent loops back, critiques, iterates Got no clue why anyone is paying $10K for a website anymore. It’s easy now.

klöss

14,574 views • 3 months ago

Anthropic just dropped a 3-hour course on how to actually master Claude Code, taught by the engineer who built it: 00:07 – everything new in Claude Code 24:39 – Boris Cherny builds a full app live 55:38 – the complete prompting playbook 1:29:07 – the "thinking" lever almost everyone misses 1:52:58 – how to pick the right model for the job 2:24:22 – how Anthropic itself codes with Claude This 3-hour watch will replace 10 paid Claude Code courses on the internet. Watch it now, then read how to build an AI that codes while you sleep, in the article below.

Anthropic just dropped a 3-hour course on how to actually master Claude Code, taught by the engineer who built it: 00:07 – everything new in Claude Code 24:39 – Boris Cherny builds a full app live 55:38 – the complete prompting playbook 1:29:07 – the "thinking" lever almost everyone misses 1:52:58 – how to pick the right model for the job 2:24:22 – how Anthropic itself codes with Claude This 3-hour watch will replace 10 paid Claude Code courses on the internet. Watch it now, then read how to build an AI that codes while you sleep, in the article below.

Phosphen

101,077 views • 17 days ago

My favorite way of interacting with Claude Code is to have it generate static HTML files as outputs (reports, explorations, code structure, mockups etc.) I wanted to iterate on the file by commenting in browser and having Claude update the output live. So, I built this Claude Skill👇 How it works: - Install Claude Code skill (ask it to clone repo) - Build an HTML page for anything (e.g. research coding agents and generate HTML report) - Ask it to make the page interactive That's it. CC will launch a localhost server and allow you to then leave comments on the page itself and once it updates, will give you a tour of changes. It's like Google Docs kind of comments/iteration but for HTML pages.

My favorite way of interacting with Claude Code is to have it generate static HTML files as outputs (reports, explorations, code structure, mockups etc.) I wanted to iterate on the file by commenting in browser and having Claude update the output live. So, I built this Claude Skill👇 How it works: - Install Claude Code skill (ask it to clone repo) - Build an HTML page for anything (e.g. research coding agents and generate HTML report) - Ask it to make the page interactive That's it. CC will launch a localhost server and allow you to then leave comments on the page itself and once it updates, will give you a tour of changes. It's like Google Docs kind of comments/iteration but for HTML pages.

Paras Chopra

215,134 views • 2 months ago

ANTHROPIC OPEN-SOURCED A FREE REPO THAT TURNS CLAUDE INTO A SALES REP, A MARKETER AND A FINANCE LEAD. PEOPLE ARE ALREADY SELLING THIS AS A SERVICE You're not prompting from scratch. You're hiring a department How to set it up: 1. Open Cowork. In the Claude desktop app, open Cowork and go to Customize. You'll see a Browse Plugins button. That's the marketplace 2. Pick your first role. Inside you'll find sales, marketing, finance, legal, data, customer support, product management and more. Each plugin has the skills for that role already baked in, plus the connectors it would use. Install the one you need most 3. Put it to work standalone. It works day one with no setup. Trigger a workflow with a slash command like /sales:call-prep or /data:write-query, paste your notes, and it already knows what good output looks like 4. Connect its tools to supercharge it. Authorize the tools that role uses, your CRM, your analytics, your data warehouse. Standalone is the intern. Connected is the senior hire 5. Build the rest of the team. Install more roles and they work together in one session. Data pulls the numbers, finance reconciles them, marketing turns it into a report. One operator, a full cross-functional team, no payroll This is the same base layer Claude for Legal and Claude for Financial Services are built on. You're getting it for free Full breakdown in my article below. Bookmark this

ANTHROPIC OPEN-SOURCED A FREE REPO THAT TURNS CLAUDE INTO A SALES REP, A MARKETER AND A FINANCE LEAD. PEOPLE ARE ALREADY SELLING THIS AS A SERVICE You're not prompting from scratch. You're hiring a department How to set it up: 1. Open Cowork. In the Claude desktop app, open Cowork and go to Customize. You'll see a Browse Plugins button. That's the marketplace 2. Pick your first role. Inside you'll find sales, marketing, finance, legal, data, customer support, product management and more. Each plugin has the skills for that role already baked in, plus the connectors it would use. Install the one you need most 3. Put it to work standalone. It works day one with no setup. Trigger a workflow with a slash command like /sales:call-prep or /data:write-query, paste your notes, and it already knows what good output looks like 4. Connect its tools to supercharge it. Authorize the tools that role uses, your CRM, your analytics, your data warehouse. Standalone is the intern. Connected is the senior hire 5. Build the rest of the team. Install more roles and they work together in one session. Data pulls the numbers, finance reconciles them, marketing turns it into a report. One operator, a full cross-functional team, no payroll This is the same base layer Claude for Legal and Claude for Financial Services are built on. You're getting it for free Full breakdown in my article below. Bookmark this

Yarchi

31,798 views • 1 month ago

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,104 views • 24 days ago

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below

Anatoli Kopadze

16,858 views • 1 month ago