Claude Code's biggest weakness is memory. On a big codebase it greps through your files every time you ask it something, burns tokens doing it, and forgets the layout the second the session ends. This video walks through Graphify, a free open source tool (nearly 70,000 stars) that fixes that by turning your whole repo into a knowledge graph Claude queries instead of crawling files. I also run a real token test so you can see the actual saving, not the hyped number. Here's what's inside: Step 1: What it actually does Graphify reads your repo once and builds a map. Not just that file A connects to file B, but why. Claude reads the map instead of grepping. Fewer tokens, more accurate answers, and it remembers the structure. Step 2: The three passes Pass 1 is your code, parsed locally with tree-sitter (classes, functions, imports, call graphs), no LLM, free. Pass 2 transcribes any audio/video locally with Whisper. Pass 3 uses Claude sub agents to read docs, PDFs and images and slot them into the graph. Step 3: Why it's not graph RAG Graphify uses no embeddings. It's best for mapping a codebase and how it's wired. A graph RAG system is better for questioning a huge pile of unstructured PDFs. Think of Graphify as sitting between an Obsidian vault and a full RAG setup. Step 4: Installing it Easiest path in Claude Code: copy the Graphify GitHub URL, paste it into Claude, and ask it to install Graphify for you. It comes with a skill that tells Claude which command to use, so you don't have to memorise anything. Step 5: The token test I cloned Papermark (a real, sizable repo), built the graph, then asked the same question twice. With Graphify: ~54k tokens. Without: ~108k. Same correct answer, about half the cost. Not the 70x people throw around, but a real saving that pays for itself. Resources I use: - Graphify (GitHub): https://github.com/safishamsi/graphify Build the map once, and with the commit hook installed it keeps itself current for free. That's the memory people keep talking about.

In this video, I show how I run Claude Code from my phone all day through a Telegram bot wired straight into my Claude Code project. Voice notes, transcription, replies in the chat, the bot running 24/7 on my Mac. No VPS, no Mac mini, no monthly fee. Step 1, Get the skill: Drop the Claude Code Telegram Bot skill into your Claude project. Tell Claude "proceed with the Telegram setup" and it walks you through the whole thing. Step 2, Create the Telegram bot: Message BotFather in Telegram, hit new bot, name it, copy the access token. Paste that into Claude. Step 3, Group and topics: Create a Telegram group, add your bot, promote it to admin, enable topics under group settings. The topics step needs a message in the group before Claude can confirm it. Step 4, API keys: You don't need a new Anthropic API key. Tell the setup to use your existing Claude Code login. Only the OpenAI key is required, and only if you want voice notes ($5 deposit, lasts months). Step 5, Make it run 24/7: Tell Claude to set it up to run all the time. It installs a launchd service that keeps the bot online with the lid closed, auto-restarts on crashes, auto-starts on every login. --- Send this prompt to Claude Code: **copy below this line** I'm giving you a skill called Claude Code Telegram Bot. Get the files with: git clone https://github.com/automatorsplus/claude-code-telegram-bot Follow the README to set it up. Recommend how it would best apply to our setup in plain language, and ask me a few questions to clarify my intent before you install it. --- If you want to drive Claude Code from anywhere, this is the setup.

Most Claude Code skills on YouTube are built for a YouTube clip. These are the five I actually keep installed when work is going out to a paying client. Here they are in install order so they stack: 1. Skill Creator → /plugin install skill-creator@claude-plugins-official The factory. Turns natural language into reusable skills. 2. Superpowers → /plugin install superpowers@claude-plugins-official Stops Claude sprinting. Plans, tests, verifies before claiming done. 3. Claude Mem → /plugin marketplace add thedotmack/claude-mem Carries memory across sessions automatically. 4. GSD → npx get-shit-done-cc --claude --global Beats context rot by splitting work across sub-agents. Heads up: uses more tokens. 5. Frontend Design → /plugin install frontend-design@claude-plugins-official Fixes the AI-slop look on UI work. Strongest before-after of the bunch. Install them in this order. Each one fills a hole the next one doesn't try to cover. If you've got a sixth one I should be running, drop it below — always testing.

Just dropped a full walkthrough of the AI stack I use for animated sites: Higgsfield (GPT Image 2) for the hero, Claude Design for the layout, and Seedance 2.0 for motion. The trick most people miss: Claude Design eats credits when you let it regenerate from scratch. The one-line plan-mode prompt at the end of the brief saves you a ton. 📦 Resource pack in the classroom - every prompt I used, the reference image, and the final Folio assets.

Seedance 2.0 is one of the strongest AI video models out right now. Cinematic motion, real camera moves, holds physics where most models fall apart. The catch was always the workflow — picking the model, writing the prompt the way it expects, managing shots. I built a skill that hands all of that to Claude. Three live shots end-to-end in the video. Send this prompt to Claude Code: **copy below this line** I'm giving you a skill called Seedance. Get the files with: git clone https://github.com/automatorsplus/seedance-skill Follow the README to set it up. Recommend how it would best apply to our setup in plain language, and ask me a few questions to clarify my intent before you install it.