Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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...

141,580 görüntüleme • 4 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

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,568 görüntüleme • 4 ay önce

I can't f*cking believe people still use Claude Code like a chat bot. the ones getting real work out of it gave it a folder, tools and a map of everything it knows. that map is graphify. you point it at a folder and it builds a knowledge graph of everything inside. code, docs, PDFs, images, even video. then your agent searches the graph instead of opening files one by one. 134k stars on GitHub. backed by Y Combinator. and most people still haven't tried it. what makes it different: -> the code part runs fully on your machine. nothing gets uploaded -> no vector database, no embeddings. it's a real graph your agent walks through -> every connection is labeled: read straight from the source, or figured out by graphify. you always know which -> you get 3 files: a clickable map you open in your browser, a report with the key ideas and surprising links, and the full graph your agent queries anytime on a public memory benchmark it found the right answer in its top 10 results about half the time. mem0 managed under 5%. and building the graph cost 0 model credits. here's the full setup around it: > create a folder called AGENT, open Claude Code inside it, and add a CLAUDE.md with one line: "save every decision, person and project to memory/" > run uv tool install graphifyy, then graphify install, then type /graphify . and the whole folder becomes a map Claude can search in seconds > run npm install -g @googleworkspace/cli, then gws auth setup and gws auth login. Claude can now read your Gmail, Calendar and Drive > run claude mcp add playwright npx @playwright/mcp@latest. it gets its own browser for sites, forms and data > run npm i -g jev-guard, then jev-guard key "...", then jev-guard install claude. Jev checks every action before it runs. rm -rf gets blocked, emails with hidden instructions get flagged, about 4 cents per 1,000 checks > type /schedule and say "every morning at 7:30, send me what came in, what you drafted and what needs my yes" one folder. 15 minutes. and Claude finally knows where everything is. all the repos: -> -> -> -> bookmark this and try graphify first. it's the piece everyone skips.

kiosa

31,346 görüntüleme • 11 gün önce

Holy sh*t I spent weeks turning Claude Code into a design studio. no Figma license. no agency. no plugins I had to pay for. here's the stack I used and it's embarrassingly simple: -> graphify: teach Claude your brand dump your guidelines, logos, PDFs and old projects into one folder. graphify turns it into a knowledge graph, so every design Claude makes follows your rules instead of guessing. 134k stars, Y Combinator. uv tool install graphifyy -> graphify install -> /graphify . -> Figma-Context-MCP: Figma straight to code it hands your actual Figma file to the agent. the README says it builds designs in one shot, and does it better than pasting screenshots. -> Penpot: the open-source Figma free, open source, and its MCP server lets AI read and edit your designs, then hand them to code and back. -> React Bits: the "expensive" look, for free the biggest open-source library of animated React components. those smooth hover effects and text animations you see on high-end sites? copy, paste, done. -> HyperFrames: designs that move write HTML, get a finished video. made by HeyGen for AI agents. your landing page can now have its own launch video by tonight. claude plugin marketplace add heygen-com/hyperframes -> claude plugin install hyperframes@hyperframes -> MCP for Blender: 3D without learning Blender connects Claude to Blender. describe a scene, the agent builds and edits it in real 3D. the order that works: brand into graphify -> design in Figma or Penpot -> Claude builds it with React Bits -> HyperFrames makes the promo -> Blender adds the 3D hero shot the uncomfortable part: tools used to be the moat. now everyone has them for free. the only thing that still separates good design from AI slop is taste. and taste is the one thing you can't install. bookmark this. your next client will ask why you're suddenly so fast.

kiosa

72,515 görüntüleme • 10 gün önce

I truly don't understand why nobody is using this setup graphify, a tool that turns any folder into a knowledge graph your agent can query, just passed 126k stars on github and got into Y Combinator. people stopped asking ai questions. they're giving it a desk, a memory and a job. you give Claude Code one folder, plug in your email, calendar and a browser, and it turns into an agent. it reads, remembers, acts, and checks itself before it does anything stupid. doesn't matter if you're a founder, a marketer or a student, you need this the full setup: > create a folder called AGENT, open Claude Code inside it and add a CLAUDE.md with one rule: "save every decision, person and project to memory/" > run npm install -g @googleworkspace/cli, then gws auth setup. now it reads your Gmail, Calendar and Drive > run claude mcp add playwright npx @playwright/mcp@latest. it gets its own browser to open sites, fill forms and pull data for you > run uv tool install graphifyy, then graphify install, then type /graphify .. everything in the folder becomes a knowledge graph it queries in seconds instead of digging file by file > run npm i -g jev-guard, jev-guard key "...", jev-guard install claude. a tiny model called Jev scores every action before it runs. rm -rf gets blocked, a poisoned email gets flagged, for about 4 cents per 1,000 checks > type /schedule and tell it "every morning at 7:30, send me what came in, what you drafted and what waits for my yes". from now on it works on a routine 15 minutes to set up, and you never start from a blank chat again. every repo is below: -> -> -> -> bookmark this

kiosa

110,288 görüntüleme • 20 gün önce

this is f*cking insane. andrej karpathy: "the biggest regret of every engineer in my field right now is every AI conversation they never saved, and in 10 years the ones who started saving in 2024 will be running circles around the rest of us" andrej karpathy, co-founder of openai, pulled 16M views on one idea: stop using AI to write code, use it to build a second brain that remembers every article, pdf, transcript and conversation you ever fed it you point claude code at a folder, drop anything into it, and claude reads it, cross-links it with everything already there, and writes it into a living wiki. your knowledge finally compounds instead of leaking out of your head every friday the stack: → brew install obsidian, mkdir ~/vault, cd ~/vault → run claude in that folder and type "init a knowledge vault with CLAUDE.md as the rules, /raw for sources, /wiki for your pages" → drop any file into /raw (youtube transcript, meeting notes, 400-page pdf, screenshot of a tweet) and type "ingest" → claude writes a wiki page, links it to 5 existing ones automatically, updates CLAUDE.md with any new pattern it noticed about how you think → never open a blank claude chat again. every question goes through the vault, every answer cites your own sources with dates and links 5 minutes to set up. compounding knowledge from that evening forward the ugly part most will scroll past: in 10 years the engineers who started this in 2024 will remember every book, every podcast, every meeting with receipts. you will remember none of them. karpathy already picked which side he is on and you are still not on his full step-by-step is in the article below bookmark this before you waste another monday

mojesko

450,433 görüntüleme • 4 gün önce

I still don't get why people bother creating a second brain for Claude from scratch when these 10 repositories already provide complete systems They process your sources, organize them into a wiki, verify every single claim, and one of them even operates entirely on your personal machine 1. obsidian-skills-> rightarrow The CEO of Obsidian personally shows Claude the inner workings of Obsidian 2. claude-obsidian-> rightarrow Simply drop any source in, and Claude will read, link, and file it into a unified, connected graph of standard Markdown files that you control 3. obsidian-second-brain-> rightarrow Claude Code retains memory of you across different sessions, featuring 48 commands operating entirely within your Obsidian vault 4. karpathy-llm-wiki-> rightarrow Features a single installation line, followed by ingestion, querying with citations, and linting—all usable within Claude Code, Cursor, Codex, or OpenCode 5. second-brain-> rightarrow Takes raw sources as input and outputs linked wiki pages for easy browsing inside Obsidian 6. second-brain-os-> rightarrow The complete package: includes a 77-page guide, a starter vault, 18 skills, 72 commands, and 6 subagents (four of which are read-only) 7. llm-wiki-> rightarrow Utilizes a two-tier memory system: 10 to 20 rules loaded by Claude during every session, alongside 50 to 200 wiki pages fetched strictly when needed 8. vouch-> rightarrow Agents suggest modifications for your approval, where any claim lacking an explicit source is treated as an error 9. ai-second-brain-> rightarrow Transforms your historical interactions from ChatGPT and Claude into a linked Obsidian vault, which then becomes a wiki 10. LLM_Wiki_SecondBrain-> rightarrow Runs the entire pipeline locally without any cloud APIs (recommended 32 GB of RAM) I recommend adding this to bookmarks and never doing this manually again

Bober_smart

39,281 görüntüleme • 4 gün önce