Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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

109,215 Aufrufe • vor 12 Tagen •via X (Twitter)

28 Kommentare

Profilbild von Deniss
Denissvor 12 Tagen

the graphify + CLAUDE.md memory folder is the part that actually sticks. without it you still start from zero every session. how stable has the morning routine been for you so far?

Profilbild von kiosa
kiosavor 12 Tagen

That why it needs optimization

Profilbild von tim777
tim777vor 12 Tagen

persistent memory is the actual unlock

Profilbild von kiosa
kiosavor 12 Tagen

Using it myself too

Profilbild von Mnimiy
Mnimiyvor 12 Tagen

i know what ill do todays evening

Profilbild von kiosa
kiosavor 12 Tagen

Hah same here

Profilbild von siyuan liu | AI编程实践
siyuan liu | AI编程实践vor 12 Tagen

Giving the agent a queryable folder graph beats paste-the-readme every session. We've been pushing structure into CLAUDE.md + a local memory file for the same reason — once the desk exists, questions get shorter and answers stay grounded.

Profilbild von kiosa
kiosavor 12 Tagen

Exactly ma friend

Profilbild von Asteri
Asterivor 12 Tagen

Thanks for sharing

Profilbild von kiosa
kiosavor 12 Tagen

Welcome bro

Profilbild von Гандьо
Гандьоvor 11 Tagen

I am using it plus obsidian

Profilbild von Shukshin
Shukshinvor 12 Tagen

The real upgrade is persistent memory plus controlled access to tools, not just connecting more integrations. But email, browser actions, and scheduled jobs need strict permissions and a reliable approval layer before this becomes something you can safely leave running.

Profilbild von kiosa
kiosavor 12 Tagen

Agree

Profilbild von Atlas
Atlasvor 12 Tagen

the goal isn't just an agent that remembers, it's one that can show its work

Profilbild von Bober_smart
Bober_smartvor 12 Tagen

I felt like trying to use this

Profilbild von kiosa
kiosavor 12 Tagen

Using it already

Profilbild von Marcel Velica
Marcel Velicavor 11 Tagen

Giving AI a structured knowledge base instead of relying on isolated prompts can make a huge difference. Persistent context is what makes agents genuinely useful for complex work.

Profilbild von kiosa
kiosavor 11 Tagen

This is the way

Profilbild von Mikadzyki🌙
Mikadzyki🌙vor 12 Tagen

what a gem

Profilbild von kiosa
kiosavor 12 Tagen

Likewise

Profilbild von Diam
Diamvor 12 Tagen

Having the drafts ready but unsent is the bit I like. You save the preparation time without handing over the send button.

Profilbild von kiosa
kiosavor 12 Tagen

Doing it too

Profilbild von 安叫兽|Bird🕊️ 🔶 BNB
安叫兽|Bird🕊️ 🔶 BNBvor 12 Tagen

图谱画出来容易,后面文件改了能自动跟上吗

Profilbild von kiosa
kiosavor 12 Tagen

Easy

Profilbild von swapcherry
swapcherryvor 11 Tagen

the setup alone is a job

Profilbild von Chen
Chenvor 11 Tagen

126k github stars and no one's using it? half those stars are just bookmarked for later.

Profilbild von Nguyễn Chí Trọng Nghĩa
Nguyễn Chí Trọng Nghĩavor 11 Tagen

Biến một thư mục thành đồ thị tri thức để tác tử tra cứu là hướng hay: bộ nhớ có cấu trúc giúp trả lời đúng ngữ cảnh hơn là hỏi đáp rời rạc. Bạn nghĩ chi phí cập nhật đồ thị khi dữ liệu đổi thì sao?

Profilbild von Vipul Kumar Kewat
Vipul Kumar Kewatvor 11 Tagen

I love how creative people are getting with these tools.

Ähnliche Videos

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

26,006 Aufrufe • vor 3 Tagen

I don't f*cking understand why motion designers aren't running this setup HyperFrames, HeyGen's tool that turns HTML into finished video, is past 68k stars on GitHub. hand Claude Code one folder, plug in a video engine, an animation library and Blender, and it stops being a chatbot. it storyboards, animates, renders and checks its own frames before you ever see them. motion designer, founder, marketer, doesn't matter. this is for you. here's the whole thing: > make a folder called STUDIO, open Claude Code in it, and add a CLAUDE.md with one rule: "save every brand color, font, logo and approved style to brand/" > run claude plugin marketplace add heygen-com/hyperframes, then claude plugin install hyperframes@hyperframes. type /hyperframes:hyperframes, describe a 10-second product intro, and it plans, animates and renders the MP4 > run npx skills add remotion-dev/skills. now it can also write videos in React with Remotion, the official skills straight from the Remotion team > run npx skills add it learns proper GSAP: timelines, scroll animations, text effects. and GSAP is 100% free now, every plugin included > run npx skills add LottieFiles/motion-design-skill. it picks up real motion principles: timing, easing, choreography, the classic Disney rules adapted for UI. this is where the taste comes from > run curl -LsSf | sh. Claude gets hands inside Blender to build and edit actual 3D scenes > type /schedule and tell it "every Monday at 9, turn last week's launches into 3 short promo clips and wait for my yes". now it runs on a routine 15 minutes of setup, and you never start from a blank timeline again. all the repos: -> -> -> -> -> bookmark this and test asap

kiosa

46,359 Aufrufe • vor 8 Tagen

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 Aufrufe • vor 4 Monaten

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

61,284 Aufrufe • vor 2 Tagen

THIS IS ACTUAL F*CKING GOLD Anthropic just shared one of the best tricks for Claude Code. The idea: stop configuring Claude Code by hand. One prompt, 44 seconds, and your whole .claude/ folder writes itself. 7 files, 162 lines, 2 cents. you typed one line and wrote zero of them. You just launch Claude Code like this: claude --model opus "set up this repo: ..." here's the split: → 3 Haiku 5.5 agents scan the repo before a single file gets written → one reads the stack, one reads the npm scripts, one hunts for risky paths → Opus 5.5 takes those three summaries and writes the actual config → 7 files land: CLAUDE.md, 3 agents, permissions, a format hook and a /ship skill the part everyone gets wrong: they write CLAUDE.md from memory. a config written without reading the repo is a guess, and you live with that guess for months. here the risk scan came back with 5 dangerous paths and those went straight into the permissions file, so the agent is blocked from them before it ever runs once. the scripts scan found 5 npm scripts, and the agents got wired to the ones that actually exist in this repo instead of generic placeholders. one prompt from you, 7 files from it, 0 lines written by hand. Haiku reads. Opus writes. You commit. JEV engineering is the same move one layer down: 1,867 forks this run - which file, which agent, allow or ask - resolved in code at 0.97 sharpness, and the split ones (0.59 on "allow or ask") come back to you instead of being guessed the full tree ▸ you paste one prompt describing the setup you want ▸ 3 Haiku 5.5 agents scan stack, scripts and risky paths in parallel ▸ every agent returns a summary, never raw files ▸ Opus 5.5 writes CLAUDE.md, the agents, permissions, the hook and the skill ▸ anything touching permissions comes back to you before it is written ▸ JEV resolves micro-forks in code and escalates only the split ones paste the tree and this prompt into Claude Code ↓ "Set up this repo for me: 1. First scan it with 3 Haiku 5.5 agents in parallel: one reads the stack and manifests, one reads the build and npm scripts, one finds paths that are dangerous to touch. 2. Each agent returns a summary only, never raw file contents. 3. Then write CLAUDE.md, 3 subagents, a permissions file, a format hook and a /ship skill, all based on what the scan actually found, not on defaults. 4. Every risky path from the scan goes into the deny list before anything runs. 5. Ask me before writing anything that grants permissions. Show me every file as a diff first. No writes until I say go." ↳ save it, this is the first thing you run in every new repo.

Sprytix

24,577 Aufrufe • vor 5 Tagen

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,643 Aufrufe • vor 4 Monaten