Yarchi
@undefinedKi • 7,485 subscribers
AI & tech researcher | Building cool stuff | Sharing everything I learn
Videos
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 graph Claude reads instead of grepping. Up to 43x fewer tokens per query. The trick almost nobody is using yet: one flag exports the entire graph as a fully-linked Obsidian vault. Repo: /safishamsi/graphify Setup, end to end: 1. Install: uv tool install graphifyy (or pipx install graphifyy). Verify with graphify --version. 2. Install the skill in Claude Code: graphify claude install. This wires Graphify into Claude Code so you can call it as a skill. 3. Open the folder you want mapped in Claude Code. In the terminal: graphify . It extracts every concept and builds the graph in graphify-out/. 4. Export to Obsidian: graphify . --obsidian. Writes one note per concept, every relationship as a wikilink, every node linked back to its source. 5. Open the new vault in Obsidian (Manage vaults → Open folder as a vault), or drag it as a subfolder into your existing one. That's it. Your Claude Code instance now has a navigable map of the codebase that loads instantly instead of re-reading files every session. Full step-by-step build of the Claude + Obsidian second brain in the article below. Bookmark this
Yarchi134,462 views • 3 days ago
ANTHROPIC JUST QUIETLY SHIPPED A FEATURE THAT LETS CLAUDE SPAWN A WHOLE TEAM OF AGENTS THAT MESSAGE EACH OTHER AND REVIEW EACH OTHER'S WORK. It's a Claude Code feature called agent teams. The team lead spawns multiple agents that share a task list and message each other directly, not subagents reporting back, actual peers. In the demo a QA agent caught three bugs, sent the work back to the front-end and back-end devs, they fixed it, app shipped in one pass. How to run it: 1. Enable it. Needs Claude Code v2.1.32+. Add to settings.json: "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }. Or paste that to Claude and say "add this to my settings." Restart. 2. Prompt in plain English. Start with a goal (agents wake with zero context), then "create a team of 3 using Sonnet," describe each role, its deliverable, and who it messages when done. 3. The rules: each agent owns its own files, define exact outputs, name who talks to who, keep it to 3-5 agents. Use it for complex work with separate parts running in parallel. Skip it for simple or sequential tasks, teams cost 3-4x the tokens. Bookmark this.
Yarchi449,682 views • 8 days ago
THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this
Yarchi801,588 views • 16 days ago
THIS GUY HAS CLAUDE DOING $500-700 A DAY SELLING ONE DIGITAL PRODUCT, WITH ZERO SPENT ON ADS He sells one digital product and lets Claude run the content that drives the sales. No ad spend, sales starting within a day or two. The product is the easy part. The content engine is what actually sells it, and that's the whole method The exact steps: 1. Find the niche. Ask Claude for specific problems people already pay to solve in a space you know, then check Gumroad and Etsy search to confirm people are buying. Specific beats generic every time 2. Build the product with Claude. Have it design a Notion template for one exact buyer, sections and dashboard included. Recreate it in Notion, set it to "anyone can duplicate." 3. List it on Gumroad. Free account, New Product, paste the Notion link, price it, grab your checkout link 4. Run the 3-prompt content engine. This is the part that sells. First prompt: competition mining, have Claude find the top-selling competitor products and pull the most viral content mentioning them. Second: have it extract the structures and frameworks from that content into reusable templates. Third: feed it your product and those templates and have it write fresh viral content for you 5. Rerun it weekly. The niche shifts, so refresh the templates every week. The winning ones you reuse again and again Build once, post daily, let the content do the selling Bookmark this
Yarchi99,414 views • 20 days ago
HE MAKES MONEY IN REAL ESTATE WITHOUT BUYING, SELLING, OR EVEN SEEING A SINGLE HOUSE. HERE'S THE EXACT SETUP He never owns a property. He takes a single listing, turns it into a polished 30-second video, and sells that to the agent who posted it. Realtors need video for their feeds and almost none of them can make it. He sits in the middle and builds the whole thing once as a skill that runs on command Here is the exact process: 1. Pull the listing. Go to Zillow, open any listing, download the high-res images, and grab the property info. That is your raw material 2. Turn photos into video with Google Veo. Get a Google API key for Veo, the image-to-video model. It takes the listing photos and animates them into clean 30-second footage. This is the best one out right now 3. Add the voice with ElevenLabs. Get an ElevenLabs API key. Feed it the listing details and it returns a voiceover that sounds like a real human, not a robot. Lay it over the video with the text on screen 4. Send it with AgentMail. Get an AgentMail key so the system can send the finished email out on its own Then you wire it into one skill. Scrape the listing, send images to Veo, add the ElevenLabs voiceover and on-screen text, then send the email. Feed it each key one at a time and have it build each step Who you sell to: Pull realtors off Zillow and Realtor com whose listings have flat photos and zero video. That gap is your pitch. Send a free sample made from their own listing first, then charge a monthly rate for ongoing clips. One agent with ten listings is a recurring client, fully online Bookmark this
Yarchi106,174 views • 23 days ago
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
Yarchi57,768 views • 16 days ago
REAL ESTATE PEOPLE WILL HATE HIM FOR THIS. HE BUILT A CLAUDE AGENT THAT TURNS ANY LISTING INTO A SELLABLE VIDEO ON ITS OWN Playbook: connect Claude to a video generator, paste a listing, get a cinematic tour of every room, sell it to the agent But typing the prompt for every listing doesn't scale. He turned it into a skill his Claude runs on its own Here's how to build the automated version: 1. Connect the video engine once. In Claude, go to Customize, Connectors, Add Custom Connector, name it Higgsfield, and paste the server URL from higgsfield. ai/mcp. Authenticate through your account. No API keys. Now Claude can generate video straight from chat 2. Turn the workflow into a skill. Instead of pasting the same prompt every time, have Claude build a skill. Tell it: "Create a skill called listing-to-video. When I give it a listing URL, scrape the room photos, generate a cinematic clip of each room with Higgsfield, and save them to a folder." Now the whole process is one command, not a wall of text 3. Let the agent run the listing. Hand it a URL and say "run listing-to-video on this." It pulls the photos, fires each room through the video model, and brings the clips back. You wrote the prompt once, inside the skill. You never write it again 4. Stitch and deliver. Drop the clips together into one tour. Send a free sample to the listing's agent, then charge per video or a monthly rate for ongoing listings 5. Scale it with your team. Add a skill that drafts the outreach email and one that builds a simple landing page for the agent. Now one operator runs sourcing, production, and pitching from a single Claude session The edge isn't generating one video. It's building the skill once so every future listing runs itself Bookmark this
Yarchi53,418 views • 16 days ago
ANTHROPIC'S PRODUCT CHIEF HAS USED CLAUDE FABLE 5 FOR MONTHS BEFORE ANYONE ELSE. HERE'S WHAT HE LEARNED ABOUT THE MOST POWERFUL MODEL YET Mike Krieger co-founded Instagram and now runs product at Anthropic. He's had Claude Fable 5 for two months before the public, and his takeaway is that it changes how you have to work, not just how much you get done. Here's what stood out, and what to actually do with it 1. It holds the whole project, so stop chopping tasks small. The old habit was breaking work into model-sized pieces and stitching them. Fable keeps the whole thing in context. What to do: stop pre-slicing your prompts into tiny steps. Hand it the full goal and the intent behind it, the way you'd brief a senior engineer, and let it sequence the work itself 2. Delegate big, async, and overnight. He sets it on a hard task at night and wakes to it finished, including the model getting itself unstuck when a service died, scaffolding a workaround, and documenting it. What to do: stop babysitting one prompt at a time. Kick off long jobs and walk away. Run several sessions at once instead of one you watch 3. The skill is planning now, not typing. His day moved to long architecture conversations up front, then execution in chunks. What to do: spend your first prompts planning, not building. Then ask it to output an HTML page or markdown doc of the plan so your team aligns before any code is written. That early alignment is the new leverage 4. Match the effort level to the task. Fable's range is wide, so a heavy reasoning pass on a tiny UI tweak is overkill (and pricey). What to do: dial effort down for small jobs, save the deep thinking for hard ones. And don't use your most expensive model for quick questions, keep a fast model for those 5. Verification is the real bottleneck now. The hard part isn't getting output, it's trusting it. What to do: make every change ship with proof. Have Claude attach a screenshot or video of what it built, so you can see the result instead of reading the diff. Then stand behind the decisions yourself before you merge 6. Cost is per-result, not per-turn. Fable is expensive per call but often one-shots what other models need ten turns to get right. What to do: judge cost by what it takes to finish the task to your satisfaction, not the price of a single message. Give it a real task and see how far it gets before you jump in His bigger point: software engineering isn't over, it's different. The craft moved from writing code to owning intent, taste, and what actually ships. The floor rose so anyone can build, and the ceiling rose so experts go further than before Bookmark this
Yarchi30,559 views • 12 days ago
DRONE VIDEOGRAPHERS CHARGE $10K FOR THIS SHOT. HE PULLS IT FROM GOOGLE EARTH AND A PROMPT You never buy a drone, book a pilot, or leave the house. You pick any city on Earth, trace the flight path you want, and let Gemini render it as real-looking FPV footage. Clients pay thousands for this shot. You make it from a screenshot Here is the exact process: 1. Open Google Earth. Find the city or building you want. Frame the angle you'd want a drone to start from and take a screenshot 2. Draw the path. On that screenshot, draw a red line showing exactly where the drone should fly through the scene. This line is what the AI follows 3. Open Gemini and drop in the screenshot. Use the video generation in the Gemini app, the part that animates a still image into motion. Nano Banana handles images, the video engine is what turns your shot into footage 4. Paste the prompt. Tell it to follow the red flight path through the city, fast smooth motion, banking around buildings, golden-hour light, motion blur, 9:16 vertical, real FPV drone look. Full prompt is in the comments 5. Generate and clean it up. One clip is a few seconds. Stitch a couple together for a full flythrough and you have a reel Set the prompt once and you can re-run it for any location on the planet Who pays for this: Real estate agents, hotels, restaurants and event venues all need aerial b-roll and almost none can afford a real drone shoot Pull listings or venues with flat, ground-level photos and zero aerial footage. Send a free sample flythrough of their own location, then charge per clip or a monthly rate for ongoing reels One agent with ten listings is a recurring client, fully online Full prompt in the comments Bookmark this
Yarchi52,643 views • 22 days ago
ANTHROPIC OPEN-SOURCED A FREE REPO THAT TURNS CLAUDE INTO A SALES REP, A MARKETER AND A FINANCE LEAD. PEOPLE ARE ALREADY SELLING THIS AS A SERVICE You're not prompting from scratch. You're hiring a department How to set it up: 1. Open Cowork. In the Claude desktop app, open Cowork and go to Customize. You'll see a Browse Plugins button. That's the marketplace 2. Pick your first role. Inside you'll find sales, marketing, finance, legal, data, customer support, product management and more. Each plugin has the skills for that role already baked in, plus the connectors it would use. Install the one you need most 3. Put it to work standalone. It works day one with no setup. Trigger a workflow with a slash command like /sales:call-prep or /data:write-query, paste your notes, and it already knows what good output looks like 4. Connect its tools to supercharge it. Authorize the tools that role uses, your CRM, your analytics, your data warehouse. Standalone is the intern. Connected is the senior hire 5. Build the rest of the team. Install more roles and they work together in one session. Data pulls the numbers, finance reconciles them, marketing turns it into a report. One operator, a full cross-functional team, no payroll This is the same base layer Claude for Legal and Claude for Financial Services are built on. You're getting it for free Full breakdown in my article below. Bookmark this
Yarchi31,414 views • 15 days ago
THIS WALLET STACKED $230K ON BTC UP/DOWN BETS. THE BLUEPRINT TO AUTOMATE THE SAME EDGE WITH CLAUDE The wallet is $230K all-time, every position a Bitcoin or Ethereum Up or Down market It never guesses direction. It enters only when the math and the market disagree THE STRATEGY: BTC moves are not fully random. When the market enters a committed directional state, continuation is measurable. That is Markov persistence Entry signal: > Δ = p̂ − q ≥ ε Model probability minus market price. Enter only on a 5% gap or more Persistence filter: > p(j*,j*) ≥ 0.87 Only trade states with 0.87 persistence or higher. Below that, skip. This is what holds the win rate above 65% with zero directional guessing Payout: > r = (1 − q) / q At q = 0.647 that is +54.5% a win. At q = 0.441, +126.7%. Lower entry price, bigger asymmetry Sizing: > f* = p − (1−p)/b Kelly. At p = 0.87, b = 0.647, f* ≈ 0.71. Size to the edge, never to gut HOW TO BUILD IT WITH CLAUDE: What separates this from a static bot: Claude reads its own trade journal every night and rewrites its own thresholds 1. Take an open-source Polymarket bot repo as your base logic. Feed it to Claude and have it migrate to CLOB v2: py_clob_client_v2, Safe wallet support, fee-aware evaluation 2. Hard-code the filters. Enter only when Δ ≥ 0.05 and p(j*,j*) ≥ 0.87. Apply Kelly on every fill. 3. Run DRY_RUN first. Log every signal, entry price, Markov state, and simulated P/L. No real money until the numbers hold for days 4. The nightly loop. Claude reads the journal, finds which persistence states actually won, adjusts MIN_PROB and MIN_EDGE, ships tomorrow's rules. The agent is sharper after 50 to 100 trades THE SETUP: Claude Opus as the brain. An open-source repo as the starting logic. A Polygon wallet with $50 to $100. Telegram for the morning report Start at $1 to $2 per trade while it learns. Scale only when the dry runs and the live fills line up 17,000 trades compound a thin edge into six figures. The model finds the edge. The nightly loop keeps it sharp Bookmark before you point a bot at your first window
Yarchi22,871 views • 1 month ago
No more content to load