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.

The Premonition Vault: a sealed-prediction engine on Nox by iExec RLC, powered by ChainGPT. Crypto Twitter is full of "I called it" posts nobody can verify. Tweets get deleted. Screenshots get faked. We built a demo to fix it. Predictions are encrypted client-side via Nox by iExec, then judged... by a ChainGPT-powered AI Oracle once a time-lock expires. Only the right ones become public. Two modes: → Personal: seal your own. Right ones go public with proof, wrong ones stay sealed forever. → KOL: seal an influencer's call. If they're wrong, it becomes a public receipt. No deleted tweets. No "trust me bro." The whole thing was lab-coded with the ChainGPT Claude Code skill. One prompt scaffolded the frontend, Nox encryption, Sepolia commits, smart contracts, oracle wiring, and UI. What used to take devs weeks now takes a prompt and an afternoon. Install: /plugin install ChainGPT-org/chaingpt-claude-skill Anyone can build with ChainGPT and iExec! Demo below.show more

ChainGPT

786,698 subscribers

40,043 views • 2 months ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

How to install the ChainGPT AI skill for Claude Code so you can ship Web3 projects with ZERO coding experience. Setup takes about 3 minutes: 1. Install Claude Code at 2. Run /plugin install ChainGPT-org/chaingpt-claude-skill ( 3. Get a ChainGPT API key at: 4. Add credits at: 5. Type /chaingpt and describe what you want to build What I built: I asked for a cat-themed AI NFT generator. The skill knew which API endpoint to hit, how to handle the response, and how to display the image. If I can do this in under an hour with no coding background, so can you. Anyone can build with ChainGPT AI! Get your API key → Top up credits →

How to install the ChainGPT AI skill for Claude Code so you can ship Web3 projects with ZERO coding experience. Setup takes about 3 minutes: 1. Install Claude Code at 2. Run /plugin install ChainGPT-org/chaingpt-claude-skill ( 3. Get a ChainGPT API key at: 4. Add credits at: 5. Type /chaingpt and describe what you want to build What I built: I asked for a cat-themed AI NFT generator. The skill knew which API endpoint to hit, how to handle the response, and how to display the image. If I can do this in under an hour with no coding background, so can you. Anyone can build with ChainGPT AI! Get your API key → Top up credits →

ChainGPT

26,832 views • 3 months ago

We gave an AI agent its own wallet and a job. Then we tried to rob it. Meet the Casper Agent Simulator: an AI analyst paying its own way over x402 on Casper, powered by ChainGPT. Right now AI agents can't buy anything on their own. Every API wants a human to sign up, hand over a card, and babysit the keys. The whole internet runs on subscriptions because charging half a cent was never worth the payment fee. We built a demo to show what happens when that changes. Meet Caspi. She's an AI research analyst with a Casper wallet, an era allowance, and a client who wants a market briefing. She buys her own inputs, one request at a time: → live CSPR market data → two headlines from ChainGPT's AI News API → one ChainGPT LLM call for the analyst take → a second of compute to compile it Every purchase is a real HTTP 402. The stall quotes a price, Caspi signs an x402 payment payload, the server verifies it and hands back the goods with a settlement receipt. Around 8.5 CSPR of micropayments become a finished briefing. No signup, no card, no API key. What Casper brings to it: → Fixed 0.1 CSPR fees, so tiny payments actually make sense → Zug finality, settled in one block, no reversals → Smart-account guardrails: era spend cap, per-payment ceiling, endpoint whitelist, verifiable identity (caspi.cspr) That last one is the good part. You can fool an AI agent. You can't fool its account. So there's a "try to rob the agent" panel. A 4,800 CSPR fake NFT. A phishing invoice. A shady endpoint. A thousand-payment drain. Every one of them bounces off a rule the chain enforces. Losses: 0.000 CSPR. The whole thing was lab-coded with the ChainGPT Claude Code skill. One prompt scaffolded the x402 server, the signed-payment client, the live news and LLM integration, the guardrail logic, and the entire 8-bit agent floor. What used to take a team a sprint now takes a prompt and an afternoon. Install: /plugin install ChainGPT-org/chaingpt-claude-skill Anyone can build on Casper with ChainGPT!

We gave an AI agent its own wallet and a job. Then we tried to rob it. Meet the Casper Agent Simulator: an AI analyst paying its own way over x402 on Casper, powered by ChainGPT. Right now AI agents can't buy anything on their own. Every API wants a human to sign up, hand over a card, and babysit the keys. The whole internet runs on subscriptions because charging half a cent was never worth the payment fee. We built a demo to show what happens when that changes. Meet Caspi. She's an AI research analyst with a Casper wallet, an era allowance, and a client who wants a market briefing. She buys her own inputs, one request at a time: → live CSPR market data → two headlines from ChainGPT's AI News API → one ChainGPT LLM call for the analyst take → a second of compute to compile it Every purchase is a real HTTP 402. The stall quotes a price, Caspi signs an x402 payment payload, the server verifies it and hands back the goods with a settlement receipt. Around 8.5 CSPR of micropayments become a finished briefing. No signup, no card, no API key. What Casper brings to it: → Fixed 0.1 CSPR fees, so tiny payments actually make sense → Zug finality, settled in one block, no reversals → Smart-account guardrails: era spend cap, per-payment ceiling, endpoint whitelist, verifiable identity (caspi.cspr) That last one is the good part. You can fool an AI agent. You can't fool its account. So there's a "try to rob the agent" panel. A 4,800 CSPR fake NFT. A phishing invoice. A shady endpoint. A thousand-payment drain. Every one of them bounces off a rule the chain enforces. Losses: 0.000 CSPR. The whole thing was lab-coded with the ChainGPT Claude Code skill. One prompt scaffolded the x402 server, the signed-payment client, the live news and LLM integration, the guardrail logic, and the entire 8-bit agent floor. What used to take a team a sprint now takes a prompt and an afternoon. Install: /plugin install ChainGPT-org/chaingpt-claude-skill Anyone can build on Casper with ChainGPT!

ChainGPT

55,142 views • 1 month ago

We put TRON mainnet inside a Star Fox level. Then we let the news cycle write the final boss. Meet TRXFOX: a browser rail shooter flying escort over live TRON DAO data, powered by ChainGPT. Most blockchain games wear the chain like a skin. A logo on a billboard, a token in the corner, nothing underneath. We built the opposite: a game where the mechanics are the chain's mechanics. You're a pilot. Your job is escorting USDT transfers to finality, five blocks and a boss per run. The chain is genuinely live under you: → The HUD streams TRON mainnet in real time, block height and transactions per block, refreshing every ~3 seconds because that's TRON's actual block time → Your briefing shows the exact block you're defending at takeoff. Mine just read #84,619,787 → Your cannons run on Energy. Hold SHIFT to stake and recharge, mirroring how staked TRX provides Energy on the real network → Every zone cleared is a block hitting ~3 second finality The enemies are the network's real threat model. Your wingmate is SR-27, named after the 27 Super Representatives producing TRON's blocks while you fly. Now the good part. The boss doesn't exist until you take off. ChainGPT's news API pulls a live TRON or USDT headline. The LLM turns it into a villain attacking the network. The image API paints its pilot's portrait. The name lands on the health bar before you reach the final block. Yesterday it was TRONIC TERROR, Master of USDT Mayhem, born from a real exploit story that morning. Next week's boss hasn't happened yet. Score is TX Secured, the count of transactions you protected. No tokens, nothing to buy, just Star Fox with a working diagram of TRON's plumbing inside it. The whole thing was lab-coded with the ChainGPT Claude Code skill. One prompt wired the news API, the LLM and the image generator into the boss pipeline. Another turned TRON's staking model into the Energy meter. What used to take a game team a sprint now takes a prompt and an afternoon. Install: /plugin install ChainGPT-org/chaingpt-claude-skill Anyone can build on TRON with ChainGPT.

ChainGPT

41,433 views • 1 month ago

Free gas shouldn't come with a public relationship graph. Every sponsored tx can reveal who is backing whom. That's useful alpha for chain watchers, but terrible privacy for teams, grants and apps. For iExec RLC's Write the Future hackathon, I built Chit. Chit brings private gas sponsorship to ERC-4337. Who sent the tx is public. Who backed them stays behind ciphertext, powered by iExec Nox. It is live on Sepolia. The demo follows a sponsored UserOp into encrypted settlement, then shows the auditor decrypting it while another wallet gets denied. #WriteTheFuture

Free gas shouldn't come with a public relationship graph. Every sponsored tx can reveal who is backing whom. That's useful alpha for chain watchers, but terrible privacy for teams, grants and apps. For iExec RLC's Write the Future hackathon, I built Chit. Chit brings private gas sponsorship to ERC-4337. Who sent the tx is public. Who backed them stays behind ciphertext, powered by iExec Nox. It is live on Sepolia. The demo follows a sponsored UserOp into encrypted settlement, then shows the auditor decrypting it while another wallet gets denied. #WriteTheFuture

Bambam

21,640 views • 1 month ago

My whole company runs on skills I bundled into a GitHub repo. Here's how to build the same thing for your team: - Put your skills in a GitHub repo - Get Claude to write the couple of JSON files that make it readable as a plugin - In Claude Code, type /plugin, go to marketplaces, add marketplace, paste your repo URL - Split the plugins by department, so your copywriter isn't installing the finance skills It works in Codex too. I've got the same team skills installed there and I use them the same way. Now when I build something like my Notion formatting skill, I add it to the repo and it lands on everyone's Claude and Codex. If someone wrecks a skill, we roll it back to an older version. The key is enabling auto-update, so when someone improves a skill everyone benefits. I don't have a clue how the JSON works. I got Claude to set the whole thing up for me. Start with one skill and before you know it your whole team will be AI pilled.

My whole company runs on skills I bundled into a GitHub repo. Here's how to build the same thing for your team: - Put your skills in a GitHub repo - Get Claude to write the couple of JSON files that make it readable as a plugin - In Claude Code, type /plugin, go to marketplaces, add marketplace, paste your repo URL - Split the plugins by department, so your copywriter isn't installing the finance skills It works in Codex too. I've got the same team skills installed there and I use them the same way. Now when I build something like my Notion formatting skill, I add it to the repo and it lands on everyone's Claude and Codex. If someone wrecks a skill, we roll it back to an older version. The key is enabling auto-update, so when someone improves a skill everyone benefits. I don't have a clue how the JSON works. I got Claude to set the whole thing up for me. Start with one skill and before you know it your whole team will be AI pilled.

The Startup Ideas Podcast (SIP) 🧃

19,532 views • 12 days ago

I solved building decks with AI agents — by giving them a CLI tool like Powerpoint or Google Slides. AI could already make a beautiful deck if you asked it to using Ant's pptx skill. The problem was working with it. If it made one alignment mistake, fixing it on one slide would break something on another, and it became a game of whack-a-mole. One time I spent two days playing AI roulette, hoping the next prompt would finally fix the thing, and ended up building the whole deck by hand because I was on a deadline. So I built Hands-on Deck. And the reason it works is that this isn't just a skill — this is PowerPoint. The actual application: PowerPoint, Google Slides, Keynote, whatever you use. This is that, but for an agent, presented as a CLI. Every gesture you make in a deck app maps to a command. Click a box and type, drag a shape from here to there, look at a slide – agent can do it all in a command. And that changes how the agent behaves. With this CLI it works and thinks like a designer — it looks, makes an edit, looks again, makes another surgical edit. Compare that to Anthropic's pptx skill, built on the idea that Claude is a great programmer: it literally writes code to manipulate the deck, hand-editing XML and hoping it doesn't break anything else in the middle. The real test isn't creating something once — it's whether it can make surgical edits like you want. That's what I did in this video walkthrough and my claude crushed it! Check it out for yourself. So decks can be built like a designer now — with real flavor and taste. If you spend hours every week on decks, this gives those hours back. You can install it as a skill in Claude Code, Codex, whatever you use. Works every harness that supports skills. Let me know if you make something cool with it.

I solved building decks with AI agents — by giving them a CLI tool like Powerpoint or Google Slides. AI could already make a beautiful deck if you asked it to using Ant's pptx skill. The problem was working with it. If it made one alignment mistake, fixing it on one slide would break something on another, and it became a game of whack-a-mole. One time I spent two days playing AI roulette, hoping the next prompt would finally fix the thing, and ended up building the whole deck by hand because I was on a deadline. So I built Hands-on Deck. And the reason it works is that this isn't just a skill — this is PowerPoint. The actual application: PowerPoint, Google Slides, Keynote, whatever you use. This is that, but for an agent, presented as a CLI. Every gesture you make in a deck app maps to a command. Click a box and type, drag a shape from here to there, look at a slide – agent can do it all in a command. And that changes how the agent behaves. With this CLI it works and thinks like a designer — it looks, makes an edit, looks again, makes another surgical edit. Compare that to Anthropic's pptx skill, built on the idea that Claude is a great programmer: it literally writes code to manipulate the deck, hand-editing XML and hoping it doesn't break anything else in the middle. The real test isn't creating something once — it's whether it can make surgical edits like you want. That's what I did in this video walkthrough and my claude crushed it! Check it out for yourself. So decks can be built like a designer now — with real flavor and taste. If you spend hours every week on decks, this gives those hours back. You can install it as a skill in Claude Code, Codex, whatever you use. Works every harness that supports skills. Let me know if you make something cool with it.

Nityesh

70,020 views • 2 months ago

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

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

Yarchi

141,580 views • 2 months ago

Claude Opus 5 just one-shotted this FPS. Less than 1 hour from prompt to playable demo. Every weapon, enemy, mechanic and environment was generated from scratch. Prompt below 👇 There is no prompt below, because the first section is exactly the kind of post I’m tired of seeing every time a new model drops. A flashy demo, “one-shot” in the caption, “built in under an hour”… anything to farm impressions while conveniently hiding the actual process. If it was really made from a single prompt, show the prompt. That’s what I do on this account. When I claim something is a one-prompt prototype built with GPT-5.6 Sol Ultra and Codex, I share the prompt publicly so anyone can verify it. AI is already making game prototyping incredible. We don’t need fake “one-shot” stories to prove it. Original footage:

Claude Opus 5 just one-shotted this FPS. Less than 1 hour from prompt to playable demo. Every weapon, enemy, mechanic and environment was generated from scratch. Prompt below 👇 There is no prompt below, because the first section is exactly the kind of post I’m tired of seeing every time a new model drops. A flashy demo, “one-shot” in the caption, “built in under an hour”… anything to farm impressions while conveniently hiding the actual process. If it was really made from a single prompt, show the prompt. That’s what I do on this account. When I claim something is a one-prompt prototype built with GPT-5.6 Sol Ultra and Codex, I share the prompt publicly so anyone can verify it. AI is already making game prototyping incredible. We don’t need fake “one-shot” stories to prove it. Original footage:

Givros

14,794 views • 1 month ago

I tried to see how far I could push my current AI + 3D workflow and build a playable 3D game prototype in just 3 days😶 Not by asking AI to make the whole game in one prompt. I had my own idea, knew what I wanted to build, and used AI as a tool: - for concepting, - asset generation & texturing, - gameplay logic with the new UE 5.8 MCP + Claude Code. And honestly, it is crazy how far you can get now with the right workflow. Full video - #UE5 #ClaudeCode #AI3D #3DAI

I tried to see how far I could push my current AI + 3D workflow and build a playable 3D game prototype in just 3 days😶 Not by asking AI to make the whole game in one prompt. I had my own idea, knew what I wanted to build, and used AI as a tool: - for concepting, - asset generation & texturing, - gameplay logic with the new UE 5.8 MCP + Claude Code. And honestly, it is crazy how far you can get now with the right workflow. Full video - #UE5 #ClaudeCode #AI3D #3DAI

Stefan 3D AI

20,994 views • 2 months 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

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

Yarchi

54,840 views • 2 months 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 • 2 months ago

Once you learn these three things, you can build nearly anything yourself. Skills, chains, and plugins. Learn them once and you can automate a real part of your week yourself. Here's the system: A skill is a standard operating procedure. It's one long, reusable prompt that does one thing well, like writing a newsletter, setting up a PPC campaign, triaging your inbox, or drafting a note to the board. You write it once and reuse it forever. The trick is to feed it your real work. For my writing skill, I gave Claude posts I admire and my own exported analytics with the winners marked, so it could see the patterns. Show it what good looks like and it nails your voice. Skip that step and it guesses. A chain connects skills into an automation. One skill's output feeds the next, in order. A copywriting skill writes the messaging, then hands it to a PPC-setup skill that builds the campaign. That's an automation, and you built it without writing code. A plugin is the harness that holds it all. It bundles your skills and chains into one thing you share with your team. Instead of sending 15 separate prompts around, you send one plugin, and it knows when to use each skill on its own. Skill, chain, plugin. It's one step up the ladder, and once you're up there it's easy. Now the worked example. I call it the Daily Driver. It's five skills chained together: email triage, a writer, Slack triage, a thinking partner, and a setup skill that connects my tools and personalizes everything. I chained them into one morning brief and scheduled it to run at 9am and message me the list. Two things made the biggest difference. Give it memory. I made plain docs for About Me, my Brand Voice, and my working preferences. I had Claude interview me and saved each answer as a file. Now every output sounds like me and knows my projects and my team. Connect your tools. The plugin reads my inbox, Slack, and calendar through MCP connectors for Gmail, Slack, and Google Calendar. That's what turns "summarize my morning" into a real brief instead of an empty wish. This is the highest-ROI thing an operator can set up this week. I run my YouTube channel, podcast, community, and newsletter on plugins I built myself, all on the $100 Max plan with no engineer in sight. I made a full walkthrough that shows the whole build start to finish. Want the Daily Driver plugin to start from? Comment PLUGIN below and I'll send it to you. #AI #automation #ClaudeCode

JJ Englert

53,969 views • 2 months ago

Claude Code + Shopify AI is f*cking cracked 🤯 Shopify just dropped an official AI Toolkit that connects Claude Code directly to your store. One prompt → Claude reads your products, rewrites your descriptions for AI shopping, and pushes the updates live. All from the terminal. All inside Claude Code. Perfect for DTC brands on Shopify who are still manually editing product pages, writing descriptions in Google Docs, and copy-pasting into the Shopify admin one product at a time. Claude Code + the Shopify AI Toolkit fixes the entire workflow: → Install the official Shopify plugin in Claude Code → Authenticate to your store → Claude reads your entire product catalog → Rewrites every description to be optimized for AI shopping → Pushes the updates directly to your store automatically → Validates every API call against Shopify's official docs before executing No Shopify admin tab-switching. No copy-pasting from a Google Doc. No hiring a copywriter to rewrite 50 product pages. What you get: → Claude Code connected directly to your live Shopify store → Product descriptions optimized for how ChatGPT, Gemini, and Perplexity recommend products → Bulk updates across your entire catalog from a single prompt → Full access to Shopify's GraphQL API — products, themes, inventory, orders, everything Claude can read and write → An official plugin built by Shopify that auto-updates as new features ship I put together a full playbook with the plugin install, the store authentication walkthrough, 5 DTC workflows to run on day one, and the exact prompts I used. Want it for free? > Like this post > Comment "SHOP" And I'll send it over (must be following so I can DM)

Claude Code + Shopify AI is f*cking cracked 🤯 Shopify just dropped an official AI Toolkit that connects Claude Code directly to your store. One prompt → Claude reads your products, rewrites your descriptions for AI shopping, and pushes the updates live. All from the terminal. All inside Claude Code. Perfect for DTC brands on Shopify who are still manually editing product pages, writing descriptions in Google Docs, and copy-pasting into the Shopify admin one product at a time. Claude Code + the Shopify AI Toolkit fixes the entire workflow: → Install the official Shopify plugin in Claude Code → Authenticate to your store → Claude reads your entire product catalog → Rewrites every description to be optimized for AI shopping → Pushes the updates directly to your store automatically → Validates every API call against Shopify's official docs before executing No Shopify admin tab-switching. No copy-pasting from a Google Doc. No hiring a copywriter to rewrite 50 product pages. What you get: → Claude Code connected directly to your live Shopify store → Product descriptions optimized for how ChatGPT, Gemini, and Perplexity recommend products → Bulk updates across your entire catalog from a single prompt → Full access to Shopify's GraphQL API — products, themes, inventory, orders, everything Claude can read and write → An official plugin built by Shopify that auto-updates as new features ship I put together a full playbook with the plugin install, the store authentication walkthrough, 5 DTC workflows to run on day one, and the exact prompts I used. Want it for free? > Like this post > Comment "SHOP" And I'll send it over (must be following so I can DM)

Mike Futia

113,939 views • 4 months ago

This is one of the wildest things I have built with AI so far 😱 Asked Claude Fable 5 to create a fully interactive 3D crime investigation board using Three.js and it did it in ONE Prompt. It took one more prompt to give it a polished UI inspired by a reference design that I created with GPT Image. What surprised me most was not how it looked. It was how it worked. Fable built a complete Verlet rope physics system with 46 particles in every thread. It handled gravity, damping, distance constraints and all other features of file upload, text and everything. The threads/ropes even lift naturally with pinned evidence instead of clipping through it. I never asked it to implement any of that. I only described the experience I wanted. Maybe that's how we should work with AI. Instead of writing long long specs, we should explain what we want as an experience and let AI do its thing. Anyway, every day Fable 5 raises the bar for what I think AI can build. More to this Live: Code:

This is one of the wildest things I have built with AI so far 😱 Asked Claude Fable 5 to create a fully interactive 3D crime investigation board using Three.js and it did it in ONE Prompt. It took one more prompt to give it a polished UI inspired by a reference design that I created with GPT Image. What surprised me most was not how it looked. It was how it worked. Fable built a complete Verlet rope physics system with 46 particles in every thread. It handled gravity, damping, distance constraints and all other features of file upload, text and everything. The threads/ropes even lift naturally with pinned evidence instead of clipping through it. I never asked it to implement any of that. I only described the experience I wanted. Maybe that's how we should work with AI. Instead of writing long long specs, we should explain what we want as an experience and let AI do its thing. Anyway, every day Fable 5 raises the bar for what I think AI can build. More to this Live: Code:

The Bugged Dev

104,609 views • 1 month ago

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below

Morty

136,663 views • 3 months ago

anthropic's head of product just revealed how they're able to ship faster than any other AI company. their secret: "side quest maxxing." here's how it works: instead of long-term roadmaps, anthropic runs on unplanned afternoon experiments. anyone on the team gets full freedom to spend an afternoon prototyping an idea and show it to the team. you get to skip the approval process entirely. then, employees at anthropic try it. if they keep using it the next day and the day after that, it gets polished into a real feature. if nobody touches it again, it dies. that's the whole process. claude code on desktop started as one engineer's afternoon project. he wanted it to work on desktop so he built a prototype. people on the team started using it immediately. so they shipped it. the todo list feature started the same way. someone built it, the team adopted it internally, and it became one of the most-used parts of the product. plugins started when one engineer shared a spec with claude code and the prototype that came back was close to production-ready. went from idea to working feature in a single session. they also killed standup meetings. instead of telling people what you're working on, you just show a working demo. all walk no talk basically the team structure makes this possible. > designers ship code. > engineers make product decisions. > product managers build prototypes. everyone can take an idea from concept to working demo without waiting on anyone else. the biggest features at a $380b company came from afternoon experiments that nobody asked for. honestly this matches my own experience cooking with ai. some of the best workflows i use every day came from just fucking around. opening a session with zero intention and asking claude what it can do, or jamming on a random idea to see where it goes. if you're only using ai for tasks you already have in mind, you're missing the best part. open a session with no agenda. ask it to surprise you. try building something stupid. half the time it goes nowhere. the other half it becomes the thing you use most. you need to be sidequestmaxxing.

anthropic's head of product just revealed how they're able to ship faster than any other AI company. their secret: "side quest maxxing." here's how it works: instead of long-term roadmaps, anthropic runs on unplanned afternoon experiments. anyone on the team gets full freedom to spend an afternoon prototyping an idea and show it to the team. you get to skip the approval process entirely. then, employees at anthropic try it. if they keep using it the next day and the day after that, it gets polished into a real feature. if nobody touches it again, it dies. that's the whole process. claude code on desktop started as one engineer's afternoon project. he wanted it to work on desktop so he built a prototype. people on the team started using it immediately. so they shipped it. the todo list feature started the same way. someone built it, the team adopted it internally, and it became one of the most-used parts of the product. plugins started when one engineer shared a spec with claude code and the prototype that came back was close to production-ready. went from idea to working feature in a single session. they also killed standup meetings. instead of telling people what you're working on, you just show a working demo. all walk no talk basically the team structure makes this possible. > designers ship code. > engineers make product decisions. > product managers build prototypes. everyone can take an idea from concept to working demo without waiting on anyone else. the biggest features at a $380b company came from afternoon experiments that nobody asked for. honestly this matches my own experience cooking with ai. some of the best workflows i use every day came from just fucking around. opening a session with zero intention and asking claude what it can do, or jamming on a random idea to see where it goes. if you're only using ai for tasks you already have in mind, you're missing the best part. open a session with no agenda. ask it to surprise you. try building something stupid. half the time it goes nowhere. the other half it becomes the thing you use most. you need to be sidequestmaxxing.

Ole Lehmann

106,072 views • 4 months ago

I vibe-coded an AI agent for making presentations 🤖🖼️ - accessible to everyone and open-source! You can upload both your context files, as well as a style template (a file that captures the style of the presentation you want to create). Then you launch a prompt and watch the agent one-shot your presentation. After the presentation is generated, you can edit the text inline, chat with the agent to add/modify/delete slides, and export to Powerpoint or PDF. Built with Claude Code, powered by Claude Agent SDK + LlamaParse. Hosted on Vercel/Render. To use it, you do need to specify your LlamaCloud API key and Anthropic API key (see below). App: Repo: Sign up to LlamaCloud:

I vibe-coded an AI agent for making presentations 🤖🖼️ - accessible to everyone and open-source! You can upload both your context files, as well as a style template (a file that captures the style of the presentation you want to create). Then you launch a prompt and watch the agent one-shot your presentation. After the presentation is generated, you can edit the text inline, chat with the agent to add/modify/delete slides, and export to Powerpoint or PDF. Built with Claude Code, powered by Claude Agent SDK + LlamaParse. Hosted on Vercel/Render. To use it, you do need to specify your LlamaCloud API key and Anthropic API key (see below). App: Repo: Sign up to LlamaCloud:

Jerry Liu

21,073 views • 7 months ago

What if any post on 𝕏 could become a playable game? I built it. 𝕏 Games takes any post on this platform and turns it into a real, playable canvas game — generated in real-time by Grok and Grok Imagine. Pick a post. Any post. Grok reads it, designs a game around it, generates the art, and builds the whole thing in seconds. Leaderboards, score sharing, all native to X. Here's the thing that still blows my mind — I didn't write a single line of code. The entire app was built by AI through Pokee AI and PokeeClaw. The games are generated live by Grok. Every pixel, every mechanic, every asset. All AI. This is what's possible right now. Not in some future demo. Right now, today, on 𝕏. I built this because I wanted to show what Grok can really do when you push it beyond chatbot Q&A. It can create. It can build entire interactive experiences from a tweet. Hey xAI — if you ever want someone to build this for real, into the platform... I'm right here. 👀 Try it yourself: 🎮 walkthrough below ⬇️

What if any post on 𝕏 could become a playable game? I built it. 𝕏 Games takes any post on this platform and turns it into a real, playable canvas game — generated in real-time by Grok and Grok Imagine. Pick a post. Any post. Grok reads it, designs a game around it, generates the art, and builds the whole thing in seconds. Leaderboards, score sharing, all native to X. Here's the thing that still blows my mind — I didn't write a single line of code. The entire app was built by AI through Pokee AI and PokeeClaw. The games are generated live by Grok. Every pixel, every mechanic, every asset. All AI. This is what's possible right now. Not in some future demo. Right now, today, on 𝕏. I built this because I wanted to show what Grok can really do when you push it beyond chatbot Q&A. It can create. It can build entire interactive experiences from a tweet. Hey xAI — if you ever want someone to build this for real, into the platform... I'm right here. 👀 Try it yourself: 🎮 walkthrough below ⬇️

Mike

39,639 views • 4 months ago

Harvey is valued at $11B. Legora just raised at $5.5B. I built their entire web application in two weeks and I'm making it open-source and free for everyone to use. Say hi to Mike: When I got the chance to try Harvey and Legora, I was surprised by how simple they were. A thought came to mind: I could probably build something similar in no time at all with Claude. And so I did. Assistant, project, tabular review and workflows. You get it all without vendor lock-in. Mike offers law firms an alternative, where they own the application layer and aren't stuck with a vendor they're renewing forever. You can try Mike in the demo on the website, or go to the GitHub link on the site to download the code and run a local version yourself.

Harvey is valued at $11B. Legora just raised at $5.5B. I built their entire web application in two weeks and I'm making it open-source and free for everyone to use. Say hi to Mike: When I got the chance to try Harvey and Legora, I was surprised by how simple they were. A thought came to mind: I could probably build something similar in no time at all with Claude. And so I did. Assistant, project, tabular review and workflows. You get it all without vendor lock-in. Mike offers law firms an alternative, where they own the application layer and aren't stuck with a vendor they're renewing forever. You can try Mike in the demo on the website, or go to the GitHub link on the site to download the code and run a local version yourself.

Will Chen

1,326,204 views • 4 months ago

This is the most insane story of 2025 The number 1 game in the entire world right now was built and shipped by a single person Made $20,000,000+ legit over night TylerTVGS built a Breaking Bad simulator by himself and now it has more players than games 1000+ devs worked on This is the power you have in 2025 Literally ANYONE can do this AI gives the power for ANY single person to come up with an idea, build it, and ship it no matter how little skills you have If you're thinking "oo you gotta be special and talented to do something like that" I promise you're wrong I did the same thing. I built and shipped an AI tool for X by myself and now it's my full time business I truly believe this is the single greatest economic opportunity of the last 1,000 years If you haven't started using Grok yet to plan and build apps, even if you have 0 experience, you're letting down your entire blood line Carve out your calendar, copy the prompt below, and run it today: "I have 0 programming experience at all but would like to build an app. Here is a list of my 5 interests. What are challenges than I can build with software? Choose the easiest challenge to solve then build me a plan for building it even though I've never programmed before in my life." Don't waste this opportunity.

This is the most insane story of 2025 The number 1 game in the entire world right now was built and shipped by a single person Made $20,000,000+ legit over night TylerTVGS built a Breaking Bad simulator by himself and now it has more players than games 1000+ devs worked on This is the power you have in 2025 Literally ANYONE can do this AI gives the power for ANY single person to come up with an idea, build it, and ship it no matter how little skills you have If you're thinking "oo you gotta be special and talented to do something like that" I promise you're wrong I did the same thing. I built and shipped an AI tool for X by myself and now it's my full time business I truly believe this is the single greatest economic opportunity of the last 1,000 years If you haven't started using Grok yet to plan and build apps, even if you have 0 experience, you're letting down your entire blood line Carve out your calendar, copy the prompt below, and run it today: "I have 0 programming experience at all but would like to build an app. Here is a list of my 5 interests. What are challenges than I can build with software? Choose the easiest challenge to solve then build me a plan for building it even though I've never programmed before in my life." Don't waste this opportunity.

Alex Finn

1,430,662 views • 1 year ago