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.

Here's how I'm building Claude Code Templates... When repos get too large, AI can't navigate them properly. You need advanced techniques to send context to the model. I'm using Code Graph to load the complete codebase graph, this way responses are way more optimized. Thread showing how easy it... show more

Daniel San

34,104 subscribers

19,481 views • 1 year ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

5 Comments

Daniel San1 year ago

Go to connect your Github Account and upload your code graph... That's it 🙌 The platform handles creating the graph, documenting it, and optimizing it for retrieval in VSCode or JetBrains.

Daniel San1 year ago

Each code graph works through MCP or directly in the CodeGPT extension. Download the extension here... it's free

Stephen Reed 🤖1 year ago

On the other hand you could partition your code base into many small modules each with a repo. Claude Code is comfy reading and understanding less than 1000 lines of Java for example.

Min Chon Chi1 year ago

Interesting approach using Code Graph to optimize large codebase responses. The scalability of this method for extremely large repos is key.

MikeZ931 year ago

Just use @RepoPrompt

Related Videos

Introducing Deep Graph MCP for Claude Code 🤩 Claude Code by Anthropic is excellent and arguably one of the best tools for working with code today but... It has one major limitation, its native code search capabilities don't scale well to large repositories. By adding Deep Graph MCP, Claude's ability to explore large codebases improves dramatically. In this thread 🧵 I’ll show you how easy it is to connect this MCP to Claude Code.

Introducing Deep Graph MCP for Claude Code 🤩 Claude Code by Anthropic is excellent and arguably one of the best tools for working with code today but... It has one major limitation, its native code search capabilities don't scale well to large repositories. By adding Deep Graph MCP, Claude's ability to explore large codebases improves dramatically. In this thread 🧵 I’ll show you how easy it is to connect this MCP to Claude Code.

Daniel San

31,974 views • 1 year ago

Introducing Deep Graph Codebase to MCP with One Click... Now Available for Gemini CLI too! 🤩 Transform any public GitHub repository into an AI-ready Code Graph by simply changing the URL from to This instantly prepares the repository for seamless integration with AI assistants. It's that easy! You can now use repositories like ollama as a code graph within any project using Gemini CLI... just add the MCP Server JSON configuration to your .gemini/settings.json file

Introducing Deep Graph Codebase to MCP with One Click... Now Available for Gemini CLI too! 🤩 Transform any public GitHub repository into an AI-ready Code Graph by simply changing the URL from to This instantly prepares the repository for seamless integration with AI assistants. It's that easy! You can now use repositories like ollama as a code graph within any project using Gemini CLI... just add the MCP Server JSON configuration to your .gemini/settings.json file

Daniel San

53,516 views • 1 year 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

$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

Head of Claude Code: "85% of our engineers are running dozens or hundreds of agents. The way you do it is graph engineering." In 40 minutes he explains how a single engineer now does the work of a whole team, how far this has gone inside Anthropic and where it goes next. This is something you can't skip if you don't want to be left behind. Watch it, then read the full guide on graph engineering below.

Head of Claude Code: "85% of our engineers are running dozens or hundreds of agents. The way you do it is graph engineering." In 40 minutes he explains how a single engineer now does the work of a whole team, how far this has gone inside Anthropic and where it goes next. This is something you can't skip if you don't want to be left behind. Watch it, then read the full guide on graph engineering below.

Anatoli Kopadze

1,729,592 views • 1 month ago

Skills allow you to extend Claude Code in new ways using pre-packaged instructions and code. For example, add the docx skill to let Claude Code create word documents. I think skills make Claude Code even better as a general purpose agent, I'm excited to see how you use them!

Skills allow you to extend Claude Code in new ways using pre-packaged instructions and code. For example, add the docx skill to let Claude Code create word documents. I think skills make Claude Code even better as a general purpose agent, I'm excited to see how you use them!

Thariq

127,999 views • 11 months ago

I found an excellent use case for Remotion & claude code - get it to create a video explaining how the codebase works. In this case I got it to explain how codebase works

I found an excellent use case for Remotion & claude code - get it to create a video explaining how the codebase works. In this case I got it to explain how codebase works

Peter Gostev

15,379 views • 8 months ago

Introducing Jev Model Router for Claude Code This Claude Code Mod lets you use Jev through its direct TypeSafe AI API or Vercel AI Gateway With every request you send to Claude Code, Jev classifies the subagent model, main model (only at session start to avoid breaking the cache), and effort level Install it with one command: npx claude-code-templates@latest --mod productivity/jev-model-router Full Mod details:

Introducing Jev Model Router for Claude Code This Claude Code Mod lets you use Jev through its direct TypeSafe AI API or Vercel AI Gateway With every request you send to Claude Code, Jev classifies the subagent model, main model (only at session start to avoid breaking the cache), and effort level Install it with one command: npx claude-code-templates@latest --mod productivity/jev-model-router Full Mod details:

Daniel San

187,645 views • 6 days ago

Introducing Claude Code Hook - Context Timeline (Saving this to try later) Install with: npx claude-code-templates@latest --hook monitoring/context-timeline Managing the context window and the subagents running in Claude Code is hard to keep track of That's why I built this hook... It starts the moment you open a session and shows a timeline with the main agent's context window and how subagents start working in their own separate context Every subagent you have running will show up in real time This way you can manage the context and the subagents you run, and see everything in a much simpler way than in the console

Introducing Claude Code Hook - Context Timeline (Saving this to try later) Install with: npx claude-code-templates@latest --hook monitoring/context-timeline Managing the context window and the subagents running in Claude Code is hard to keep track of That's why I built this hook... It starts the moment you open a session and shows a timeline with the main agent's context window and how subagents start working in their own separate context Every subagent you have running will show up in real time This way you can manage the context and the subagents you run, and see everything in a much simpler way than in the console

Daniel San

51,706 views • 5 months ago

Head of Claude Code, Boris Cherny: "You're not supposed to write code anymore. You're supposed to build a graph that writes itself." In 30 minutes he breaks down how engineers at Anthropic build graphs that write the code, catch the bugs, and ships. The missing piece most developers skip: how to wire those agents into a graph that runs, verifies, and improves without you. Watch it, then read the full guide on graph engineering below.

Head of Claude Code, Boris Cherny: "You're not supposed to write code anymore. You're supposed to build a graph that writes itself." In 30 minutes he breaks down how engineers at Anthropic build graphs that write the code, catch the bugs, and ships. The missing piece most developers skip: how to wire those agents into a graph that runs, verifies, and improves without you. Watch it, then read the full guide on graph engineering below.

Mahax

417,048 views • 1 month ago

Claude Code creator, Boris Cherny: "Forget everything you learned about computer science theory, now you just explain to the model what you need and it does the rest." 32 minutes of the head of Claude Code showing exactly how he builds now. He gave Claude one prompt two weeks ago and it's still running, spawning thousands of agents on its own. The people winning right now aren't writing more code, they're building loops that run without them. Watch it, then go deeper with the graph engineering guide that combines agents and loops below.

Claude Code creator, Boris Cherny: "Forget everything you learned about computer science theory, now you just explain to the model what you need and it does the rest." 32 minutes of the head of Claude Code showing exactly how he builds now. He gave Claude one prompt two weeks ago and it's still running, spawning thousands of agents on its own. The people winning right now aren't writing more code, they're building loops that run without them. Watch it, then go deeper with the graph engineering guide that combines agents and loops below.

Anatoli Kopadze

50,081 views • 1 month ago

Old way of using Claude Code: Prompt → wait → review → prompt → wait → review → repeat 20 times. You are the loop. You are the condition check. You are the reason it keeps going. New way: /goal all tests pass and lint is clean Claude works. You do something else. You come back to a result. Here's exactly how to set it up — and how to write conditions that actually work ↓

Old way of using Claude Code: Prompt → wait → review → prompt → wait → review → repeat 20 times. You are the loop. You are the condition check. You are the reason it keeps going. New way: /goal all tests pass and lint is clean Claude works. You do something else. You come back to a result. Here's exactly how to set it up — and how to write conditions that actually work ↓

Rahul

38,382 views • 4 months ago

Here is how you can give Claude Code access to any data that exists online. It's an easy way to make it 10x more powerful than it already is. For example: Use Claude Code to find open LinkedIn jobs in your area, tailor your resume to them, and apply for them automatically.

Here is how you can give Claude Code access to any data that exists online. It's an easy way to make it 10x more powerful than it already is. For example: Use Claude Code to find open LinkedIn jobs in your area, tailor your resume to them, and apply for them automatically.

Santiago

179,198 views • 7 months ago

I'm giving away Claude Code for FREE. Yes, you read that right -- the world's best AI, now completely FREE. My mission is to get the next billion people to write great software. I believe EVERYONE should have access to the best AI, but so many are constrained by costs. I'm solving this by: disrupting the world's fastest growing industry = AI + with the most proven business model = Ads You can actually try it out now -- just one line of code, and you unlock all the powers of Claude Code, for free. how it works: 1. sign up on Giga AI Free 2. change Claude Code env variables to use our inference endpoint 2. to support the free usage, we'll add ads inside the AI responses (only contextual and relevant ads, no spam) Since we get too many signups, there's a waitlist, but we'll be rolling it out to the maximum people as we can. Watch the video to get started & comment and retweet to get access first.

I'm giving away Claude Code for FREE. Yes, you read that right -- the world's best AI, now completely FREE. My mission is to get the next billion people to write great software. I believe EVERYONE should have access to the best AI, but so many are constrained by costs. I'm solving this by: disrupting the world's fastest growing industry = AI + with the most proven business model = Ads You can actually try it out now -- just one line of code, and you unlock all the powers of Claude Code, for free. how it works: 1. sign up on Giga AI Free 2. change Claude Code env variables to use our inference endpoint 2. to support the free usage, we'll add ads inside the AI responses (only contextual and relevant ads, no spam) Since we get too many signups, there's a waitlist, but we'll be rolling it out to the maximum people as we can. Watch the video to get started & comment and retweet to get access first.

Namanyay

488,614 views • 11 months ago

How to hide the claude code sidebar in cursor without exiting it! now you can use the claude code extension in cursor and toggle it off when you need some space to code without an AI agent 😱

How to hide the claude code sidebar in cursor without exiting it! now you can use the claude code extension in cursor and toggle it off when you need some space to code without an AI agent 😱

Ian Nuttall

22,322 views • 1 year ago

Building 3D worlds in a collaborative way assisted by an AI generating code for you! In this demo, I'm using Microsoft Teams AI and Azure #OpenAI to generate Babylon.js code in a meeting, while using #TeamsToolkit for the developer experience. Is it the future of 3D design?

Building 3D worlds in a collaborative way assisted by an AI generating code for you! In this demo, I'm using Microsoft Teams AI and Azure #OpenAI to generate Babylon.js code in a meeting, while using #TeamsToolkit for the developer experience. Is it the future of 3D design?

David Rousset

15,881 views • 3 years 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,124 views • 2 months ago