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.

Introducing Claude Code Analytics Dashboard 🙌 Open source project to monitor your Claude Code agents in real-time as they work on your projects. Just run: npx claude-code-templates@latest --analytics Dashboard opens at localhost:3333 showing: - All active Claude Code sessions - Token usage & conversation stats - Real-time activity monitoring... show more

Daniel San

32,606 subscribers

62,057 views • 1 year ago •via X (Twitter)

Science & Technology

Anya Rossi• Live Now

Private livecam show

10 Comments

Daniel San1 year ago

Open source repo... give it a star or contribute if you find it useful! ⭐

Eyal Toledano1 year ago

Brilliant work!

Himanshu Kumar1 year ago

Real-time monitoring could unexpectedly shift focus from true project goals to micro-management.

43051 year ago

Very nice! Will use

👾1 year ago

This is brilliant. Nice one.

Sudheer Salavadi1 year ago

Amazing! Thank you.

Cederik ᯅ1 year ago

very cool, well done!

Josh English1 year ago

this is kewl

Joe Winke1 year ago

This is run at project level right? If I have multiple can I run in parent code folder?

Daniel San1 year ago

The analytics runs across all Claude Code instances running on your computer. You'll see each instance separated by project in the dashboard list

Related Videos

Share Claude Code sessions with this command 👇 Just shipped v1.26.1 of claude-code-templates because I kept needing to hand off work mid-session. Run: npx claude-code-templates@latest --chats - All your sessions grouped by chat - Download any conversation To share a session: - Share the file, and add it to your project - Then run: claude "read @ chat-file .md and continue" Or if you are in the same account click on "Resume" and you will see the command: claude --resume session_id Built this to keep context flowing across the team without losing momentum.

Share Claude Code sessions with this command 👇 Just shipped v1.26.1 of claude-code-templates because I kept needing to hand off work mid-session. Run: npx claude-code-templates@latest --chats - All your sessions grouped by chat - Download any conversation To share a session: - Share the file, and add it to your project - Then run: claude "read @ chat-file .md and continue" Or if you are in the same account click on "Resume" and you will see the command: claude --resume session_id Built this to keep context flowing across the team without losing momentum.

Daniel San

10,787 views • 10 months ago

Best way to debug Claude Code sessions and inspect agent context. Just Run: npx claude-code-templates@latest --chats Browser interface with advanced search across all your sessions (name, ID, directory, dates, message content). Shows every tool call with exact JSON executed. Resume button lets you continue any session - efficient context loading. Runs completely local and open source 👏

Best way to debug Claude Code sessions and inspect agent context. Just Run: npx claude-code-templates@latest --chats Browser interface with advanced search across all your sessions (name, ID, directory, dates, message content). Shows every tool call with exact JSON executed. Resume button lets you continue any session - efficient context loading. Runs completely local and open source 👏

Daniel San

32,873 views • 10 months ago

If you use Claude Code, install this immediately. It's called Claude Code Templates. It adds an entire ecosystem of AI tools to Claude. Here's what you get: 1. Agent Teams Visual dashboards showing how multiple AI agents collaborate on code. 2. Specialized Agents Front-end developers, backend engineers, QA testers, marketers. 3. MCP Integrations Connect Claude to external tools and workflows. 4. Real-Time Monitoring Track AI development sessions and performance analytics. 5. Automation Scheduling Run tasks automatically every day. Example: You can schedule an agent team to run daily at 5AM. It researches trends, generates content, and builds workflows. All automatically. The best part? Everything is free and open source.

If you use Claude Code, install this immediately. It's called Claude Code Templates. It adds an entire ecosystem of AI tools to Claude. Here's what you get: 1. Agent Teams Visual dashboards showing how multiple AI agents collaborate on code. 2. Specialized Agents Front-end developers, backend engineers, QA testers, marketers. 3. MCP Integrations Connect Claude to external tools and workflows. 4. Real-Time Monitoring Track AI development sessions and performance analytics. 5. Automation Scheduling Run tasks automatically every day. Example: You can schedule an agent team to run daily at 5AM. It researches trends, generates content, and builds workflows. All automatically. The best part? Everything is free and open source.

Julian Goldie SEO

107,454 views • 6 months 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,766 views • 1 year ago

$Running Claude Code Agents in Docker and it's working great 👏 Just executed this and watched Claude build a complete Express REST API inside an isolated container: npx claude-code-templates@latest --sandbox docker \ --agent development-team/backend-architect \ --prompt "Create a REST API with Express with validation and error handling" - Container spins up - installs Claude Agent SDK - downloads the agent - Claude starts coding Everything visible in Docker logs. Output: Full Express project with routes, validation, error handling. All files extracted to local after execution. Next tutorials: Adding Telemetry and Hooks to monitor what Claude does inside the container. Running these agents on ECS or Kubernetes would be interesting 🤔$

Running Claude Code Agents in Docker and it's working great 👏 Just executed this and watched Claude build a complete Express REST API inside an isolated container: npx claude-code-templates@latest --sandbox docker \ --agent development-team/backend-architect \ --prompt "Create a REST API with Express with validation and error handling" - Container spins up - installs Claude Agent SDK - downloads the agent - Claude starts coding Everything visible in Docker logs. Output: Full Express project with routes, validation, error handling. All files extracted to local after execution. Next tutorials: Adding Telemetry and Hooks to monitor what Claude does inside the container. Running these agents on ECS or Kubernetes would be interesting 🤔

Daniel San

100,028 views • 10 months ago

I got curious how compaction works as a PM, so I did some brain surgery on Claude Code: (Anthropic's been doing really interesting work on context editing - they showed Claude Opus playing Settlers of Catan for 75+ minutes in a single thread by constantly editing the context instead of starting fresh. When I saw that Claude Code has a compaction command with optional custom instructions, I wanted to understand what's actually happening.) Abhishek Katiyar and Aman Khan gave me the key tip: Claude Code stores all your conversation history as text files on your computer. Open a new directory and give Claude Code a task. Here's how to watch compaction happening: 1. Go to your user's root directory 2. Press Command+Shift+Period (Mac) to show hidden folders 3. Navigate to ~/.claude/projects/ 4. Find your project folder and use Cursor/VSCode to open it (there's a reason) 5. Install the JSONL Gazelle plugin (open source, thank you Gabor Cselle!) 6. Open the most recent JSONL file - each row is a message in your conversation 7. Run the compact command in Claude Code with custom instructions 8. Watch what happens in the file What I learned: When you compact, Claude Code doesn't just summarize and delete everything. It creates a "compact boundary" in the conversation file, writes a summary of what happened before, but keeps the full original conversation (!!!!) The new thread can still retrieve any details from before compaction if needed. That is so damn cool. Why this matters: What you're getting in Claude Code is similar to what Anthropic ships in their developer SDK - so inspecting your daily tools is how you build real product intuition. The best way to understand AI systems is to open them up and look inside. Everything is text files.

I got curious how compaction works as a PM, so I did some brain surgery on Claude Code: (Anthropic's been doing really interesting work on context editing - they showed Claude Opus playing Settlers of Catan for 75+ minutes in a single thread by constantly editing the context instead of starting fresh. When I saw that Claude Code has a compaction command with optional custom instructions, I wanted to understand what's actually happening.) Abhishek Katiyar and Aman Khan gave me the key tip: Claude Code stores all your conversation history as text files on your computer. Open a new directory and give Claude Code a task. Here's how to watch compaction happening: 1. Go to your user's root directory 2. Press Command+Shift+Period (Mac) to show hidden folders 3. Navigate to ~/.claude/projects/ 4. Find your project folder and use Cursor/VSCode to open it (there's a reason) 5. Install the JSONL Gazelle plugin (open source, thank you Gabor Cselle!) 6. Open the most recent JSONL file - each row is a message in your conversation 7. Run the compact command in Claude Code with custom instructions 8. Watch what happens in the file What I learned: When you compact, Claude Code doesn't just summarize and delete everything. It creates a "compact boundary" in the conversation file, writes a summary of what happened before, but keeps the full original conversation (!!!!) The new thread can still retrieve any details from before compaction if needed. That is so damn cool. Why this matters: What you're getting in Claude Code is similar to what Anthropic ships in their developer SDK - so inspecting your daily tools is how you build real product intuition. The best way to understand AI systems is to open them up and look inside. Everything is text files.

Tal Raviv

57,910 views • 7 months ago

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.

Elias

14,096 views • 3 months ago

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Kanika

20,648 views • 1 month ago

Introducing MagicPath 2.0. MagicPath is now a multiplayer canvas for humans and agents like Codex or Claude Code to design and build with AI. Use your codebase, grab data from anywhere, and see the agents work in real time as a team while building fully functional prototypes.

Introducing MagicPath 2.0. MagicPath is now a multiplayer canvas for humans and agents like Codex or Claude Code to design and build with AI. Use your codebase, grab data from anywhere, and see the agents work in real time as a team while building fully functional prototypes.

Pietro Schirano

408,978 views • 3 months ago

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

Ado

71,910 views • 6 months ago

THIS GUY TURNED A DESK LAMP INTO A LIVE CLAUDE CODE STATUS INDICATOR the lamp changes color based on what claude code is doing in real time when claude is thinking it's one color. when it's writing code it shifts. when it's done it changes again. when it errors out you know instantly without even looking at your screen the lamp is a moonside halo and i'm already tryna to buy one I might even buy multiple for the multiple claude sessions running in the background and turn my room into a disco if the color reflected the operational status of claude it would just be red 24/7 it could also track your usage limit. green at the start of the session, slowly fading to red as your tokens drain people are already hooking this up to their philips hue and govee setups at home

THIS GUY TURNED A DESK LAMP INTO A LIVE CLAUDE CODE STATUS INDICATOR the lamp changes color based on what claude code is doing in real time when claude is thinking it's one color. when it's writing code it shifts. when it's done it changes again. when it errors out you know instantly without even looking at your screen the lamp is a moonside halo and i'm already tryna to buy one I might even buy multiple for the multiple claude sessions running in the background and turn my room into a disco if the color reflected the operational status of claude it would just be red 24/7 it could also track your usage limit. green at the start of the session, slowly fading to red as your tokens drain people are already hooking this up to their philips hue and govee setups at home

Om Patel

108,254 views • 4 months ago

We've partnered with Paul Jankura to host an official Claude Code workshop in NYC and I genuinely cannot stop thinking about how good this is going to be. We've been getting an incredible amount of requests from our enterprise clients for Claude Code training, and we're thrilled to finally be doing something official with Anthropic to meet that demand. This workshop is being run by an Anthropic engineer, one of our senior AI Strategists at tenex, and myself — and we're going all in on teaching you how to orchestrate agents with Claude Code. Getting set up, skills, hooks, plugins, and more. You'll leave having actually built things, not just watched a demo. You'll see the magic of Claude firsthand! We're also pulling back the curtain on how our engineers at Tenex are using Claude Code inside Fortune 500 companies right now to accelerate impact — and we'll take live questions on what implementing Claude Code at scale actually looks like. World-class venue, the right people in the room, and a real hands-on experience your team can bring back and put to work immediately. Free event. 30 spots total. We're accepting up to 2 people per org — usually a senior decision maker and a technical partner. April 10th, New York City. If you're serious about bringing Claude Code into your org, this is the room to be in. Apply here:

We've partnered with Paul Jankura to host an official Claude Code workshop in NYC and I genuinely cannot stop thinking about how good this is going to be. We've been getting an incredible amount of requests from our enterprise clients for Claude Code training, and we're thrilled to finally be doing something official with Anthropic to meet that demand. This workshop is being run by an Anthropic engineer, one of our senior AI Strategists at tenex, and myself — and we're going all in on teaching you how to orchestrate agents with Claude Code. Getting set up, skills, hooks, plugins, and more. You'll leave having actually built things, not just watched a demo. You'll see the magic of Claude firsthand! We're also pulling back the curtain on how our engineers at Tenex are using Claude Code inside Fortune 500 companies right now to accelerate impact — and we'll take live questions on what implementing Claude Code at scale actually looks like. World-class venue, the right people in the room, and a real hands-on experience your team can bring back and put to work immediately. Free event. 30 spots total. We're accepting up to 2 people per org — usually a senior decision maker and a technical partner. April 10th, New York City. If you're serious about bringing Claude Code into your org, this is the room to be in. Apply here:

JJ Englert

41,213 views • 5 months ago

I’ve been asked a lot why I keep Claude Code auto-compact turned off. Here’s why 👇 If you configure commands, sub-agents, and hooks properly, you almost never hit auto-compact. Every time it triggered for me, I lost important context. After looking at how compaction actually works, it was clear that key details were being dropped. So I disabled it and focused on better context management per session instead. If you want to see what happens under the hood when a compact runs: npx claude-code-templates@latest --chats You’ll get a full breakdown + per-session analytics to keep improving your workflows.

I’ve been asked a lot why I keep Claude Code auto-compact turned off. Here’s why 👇 If you configure commands, sub-agents, and hooks properly, you almost never hit auto-compact. Every time it triggered for me, I lost important context. After looking at how compaction actually works, it was clear that key details were being dropped. So I disabled it and focused on better context management per session instead. If you want to see what happens under the hood when a compact runs: npx claude-code-templates@latest --chats You’ll get a full breakdown + per-session analytics to keep improving your workflows.

Daniel San

105,795 views • 8 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,292 views • 2 months ago

Sure, everyone loves Claude Code but if you ask non-coders: they're all obsessed with Cowork. JJ Englert at tenex is one of them, and he's giving us the power user's guide to getting started with Claude Cowork. In this ep, JJ walks me through: - How to set up Claude Cowork projects (hint: it's just a folder on your computer) - His "brain" file: a doc that tells Claude who he is, how he works, and who he works with, so he never has to re-explain himself - 3 AI agents with different personas that review your work before you share it with real humans My favorite take from this ep: Cowork teaches you the mental models of Claude Code without ever opening a terminal. If you've been stuck in chat mode wondering how to actually get AI to do work for you, this is your episode. ty to our amazing sponsors! 🔀 Tines - Start building intelligent workflows today 🖱️Cursor - The best way to code with AI Full episode:

Sure, everyone loves Claude Code but if you ask non-coders: they're all obsessed with Cowork. JJ Englert at tenex is one of them, and he's giving us the power user's guide to getting started with Claude Cowork. In this ep, JJ walks me through: - How to set up Claude Cowork projects (hint: it's just a folder on your computer) - His "brain" file: a doc that tells Claude who he is, how he works, and who he works with, so he never has to re-explain himself - 3 AI agents with different personas that review your work before you share it with real humans My favorite take from this ep: Cowork teaches you the mental models of Claude Code without ever opening a terminal. If you've been stuck in chat mode wondering how to actually get AI to do work for you, this is your episode. ty to our amazing sponsors! 🔀 Tines - Start building intelligent workflows today 🖱️Cursor - The best way to code with AI Full episode:

claire vo 🖤

50,362 views • 4 months 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

56,177 views • 3 months ago

DOWNLOAD MASTERCARD DESIGN MD AND BUILD CLEAR WITH CLAUDE CODE people onboard Claude with text designers actually getting results onboard it with a file most never think to write step everyone skips: A design md - plain text rulebook for colors, fonts, spacing, component patterns, tone You don’t write it from scratch - pull a public one from an open design system repo, or literally download a real brand’s guidelines and tell Claude “design like this” Upload it once to a Claude Design system, pick the strongest model, set effort to Max, wait 10-20 minutes for real mockups to review Every project after that pulls your actual brand automatically - zero re explaining your look every single prompt mistake that burns the most hours: designing and coding in the same conversation Claude Design is for visual exploration Claude Code is for production “Mixing them is where beginners lose entire afternoons re litigating decisions that were already made” real workflow, start to finish: design system once - structured brief - first draft - refine with chat, inline comments, sliders - export handoff bundle - Claude Code converts it to a real Next.js app - push, deploy, done 10 dashboards in 10 minutes isn’t the headline Never re explaining your brand again is full below

YARD

31,614 views • 9 days ago

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering

Om Patel

159,590 views • 5 months ago

Claude Code + computer use is f*cking cracked 🤯 Build a landing page → Claude opens Chrome, looks at it, spots every issue, and fixes it — without you describing a single thing. All inside Claude Code. Perfect for DTC brands and agencies who are still vibe-coding landing pages and advertorials in Claude Code, then manually opening them in Chrome, spotting 15 things wrong, and describing every visual issue back to Claude one at a time. If you're building pages in Claude Code and your workflow looks like this — build the page, open it in Chrome, spot broken spacing, go back to Claude, type "the CTA button is too low and the hero image is cut off," wait for the fix, open Chrome again, find 3 new issues, describe those too ... Claude Code + computer use eliminates the entire loop: → Claude writes the full landing page or advertorial → Opens Chrome and navigates to it → Spots layout issues, broken spacing, off-brand colors, missing elements → Fixes everything and re-checks until the page looks right → Tests your Shopify product pages by clicking through like a real customer → Walks through your checkout flow and flags friction before customers hit it → You only see the finished, visually verified result No describing what you see on screen. No "the CTA button needs more contrast" back-and-forth. No being the eyeballs for an AI that can't see. What you get: → Landing pages and advertorials Claude builds AND visually QAs before you ever look at them → Product pages Claude clicks through — testing layout, images, and CTAs like a real user → HTML dashboards Claude opens and verifies the charts actually render → Checkout flows Claude walks through step by step to catch friction → All of it happening in one session — build, test, fix, done One prompt. Claude builds it, checks it, and fixes it. You just review the finished page. I put together a full playbook with the exact setup, the prompts, and 5 DTC workflows that use Claude Code + computer use. Want it for free? > Like this post > Comment "CLAUDE" And I'll send it over (must be following so I can DM)

Mike Futia

19,143 views • 5 months ago