Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

MOONSHOT JUST CLONED CLAUDE CODE AND MADE IT FREE. It's called Kimi Code CLI. Open source, MIT license, maintained by the lab that shipped K3 yesterday. And it does things Claude Code doesn't: → drop a screen recording into the chat as input → built-in coder, explore, and plan... show more

darkzodchi

25,654 subscribers

406,325 Aufrufe • vor 1 Monat •via X (Twitter)

Wissenschaft & Technologie Bildung Finanzen

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Your Claude Code setup is probably bloated and you don't even know it. Every MCP server you add loads its full tool list into your context window the second your session starts. Stack too many and you're burning context before you type a word. So the move was never "add more." It's "add the right ones." Anthropic dropped an official plugin that does exactly that. It scans your actual codebase and tells you what's worth adding across all five layers: → hooks → skills → MCP servers → subagents → slash commands React project? It suggests Playwright. Auth code? It flags a security reviewer. It's read-only. Touches nothing. Just hands you the blueprint. The plugin isn't the edge. Knowing it exists is. /plugin install claude-code-setup@claude-plugins-official Steal this before everyone does.

Your Claude Code setup is probably bloated and you don't even know it. Every MCP server you add loads its full tool list into your context window the second your session starts. Stack too many and you're burning context before you type a word. So the move was never "add more." It's "add the right ones." Anthropic dropped an official plugin that does exactly that. It scans your actual codebase and tells you what's worth adding across all five layers: → hooks → skills → MCP servers → subagents → slash commands React project? It suggests Playwright. Auth code? It flags a security reviewer. It's read-only. Touches nothing. Just hands you the blueprint. The plugin isn't the edge. Knowing it exists is. /plugin install claude-code-setup@claude-plugins-official Steal this before everyone does.

Evan Luthra

36,455 Aufrufe • vor 2 Monaten

Claude Code feels completely different once you install this. Anthropic quietly released an official plugin called claude-code-setup and it basically turns Claude Code from “pretty good” into an actual AI dev environment. It scans your project and recommends: → hooks → skills → MCP servers → subagents → automations Then sets everything up step-by-step for you. Most people are using Claude Code completely vanilla… which is why their experience feels messy. The real power comes from the ecosystem around it. Install: /plugin install claude-code-setup@claude-plugins-official Bookmark this before you forget it.

Claude Code feels completely different once you install this. Anthropic quietly released an official plugin called claude-code-setup and it basically turns Claude Code from “pretty good” into an actual AI dev environment. It scans your project and recommends: → hooks → skills → MCP servers → subagents → automations Then sets everything up step-by-step for you. Most people are using Claude Code completely vanilla… which is why their experience feels messy. The real power comes from the ecosystem around it. Install: /plugin install claude-code-setup@claude-plugins-official Bookmark this before you forget it.

Suryansh Tiwari

1,546,806 Aufrufe • vor 3 Monaten

ANTHROPIC JUST TURNED AI AGENTS INTO GIT REPOS Anthropic shipped "ant" - a CLI that runs every Claude API endpoint straight from your terminal. The headline isn't the terminal access. It's that you can now version-control an AI agent as YAML in Git and have CI sync it to the Claude Platform, the same way you ship code. - Every API resource is a subcommand: messages, models, files, agents, sessions - Define an agent in a YAML file, check it into your repo, and keep it in sync with one update command - Spin up a session, send it an event, then pull every event and tool call back from the same CLI - Claude Code knows how to drive ant out of the box - it shells out and reads the results with no glue code Agents just stopped being prompts you babysit and became infrastructure you deploy.

ANTHROPIC JUST TURNED AI AGENTS INTO GIT REPOS Anthropic shipped "ant" - a CLI that runs every Claude API endpoint straight from your terminal. The headline isn't the terminal access. It's that you can now version-control an AI agent as YAML in Git and have CI sync it to the Claude Platform, the same way you ship code. - Every API resource is a subcommand: messages, models, files, agents, sessions - Define an agent in a YAML file, check it into your repo, and keep it in sync with one update command - Spin up a session, send it an event, then pull every event and tool call back from the same CLI - Claude Code knows how to drive ant out of the box - it shells out and reads the results with no glue code Agents just stopped being prompts you babysit and became infrastructure you deploy.

BuBBliK

200,456 Aufrufe • vor 3 Monaten

GITHUB JUST KILLED THE WORST PART OF VIBE CODING they shipped a free tool called Spec Kit and it already crossed 120,000 stars the fix is stupidly simple instead of tossing vague prompts at an agent and praying it doesn't wreck your project Spec Kit makes the AI write a full structured spec before it touches a single line of code it works through the problem first figures out what you want to build asks about the gaps lays out the project then it starts coding you get fewer insane bugs, cleaner output and results you can predict the flow looks like this: /constitution for your rules and standards /specify for what you want to build /clarify for the open questions before you start /plan for architecture and stack /tasks for the ordered work /implement to run it it plugs into Claude Code, Cursor, Copilot, Codex, Gemini CLI and 25+ other agents 120,000 stars, 10,000 forks, open source, shipped by GitHub itself learning to drive agents like this is most of what separates people getting hired as AI engineers from everyone still fighting their prompts

GITHUB JUST KILLED THE WORST PART OF VIBE CODING they shipped a free tool called Spec Kit and it already crossed 120,000 stars the fix is stupidly simple instead of tossing vague prompts at an agent and praying it doesn't wreck your project Spec Kit makes the AI write a full structured spec before it touches a single line of code it works through the problem first figures out what you want to build asks about the gaps lays out the project then it starts coding you get fewer insane bugs, cleaner output and results you can predict the flow looks like this: /constitution for your rules and standards /specify for what you want to build /clarify for the open questions before you start /plan for architecture and stack /tasks for the ordered work /implement to run it it plugs into Claude Code, Cursor, Copilot, Codex, Gemini CLI and 25+ other agents 120,000 stars, 10,000 forks, open source, shipped by GitHub itself learning to drive agents like this is most of what separates people getting hired as AI engineers from everyone still fighting their prompts

Atlas

501,832 Aufrufe • vor 1 Monat

Claude Code v2.1.198 ships a new built-in skill: /dataviz It loads chart and dashboard design guidance directly into context: chart type selection, layout rules, and visual hierarchy for data-heavy UIs It also includes a runnable color-palette validator, so Claude can check contrast and accessibility programmatically instead of guessing No install needed, it comes with the CLI 👇

Claude Code v2.1.198 ships a new built-in skill: /dataviz It loads chart and dashboard design guidance directly into context: chart type selection, layout rules, and visual hierarchy for data-heavy UIs It also includes a runnable color-palette validator, so Claude can check contrast and accessibility programmatically instead of guessing No install needed, it comes with the CLI 👇

Daniel San

88,420 Aufrufe • vor 2 Monaten

Claude Code + Google Stitch 2.0 is f*cking cracked 🤯 Google just dropped a free AI design agent that solves Claude Code's biggest weakness: frontend design. One screenshot of a high-converting landing page → a production-ready site for your brand in minutes. All inside Google Stitch + Claude Code. Perfect for DTC brands and agencies who are building advertorial pages and product launch pages for Meta but burning days on designer back-and-forth. If you're running Meta ads and need 5-10 different landing pages testing different hooks, angles, and offers — each one targeting a different audience and pain point — you know the bottleneck isn't the ads. It's the pages. Briefing designers, waiting for revisions, paying $2-5K per page. Stitch eliminates the design bottleneck: → Find a high-converting advertorial that's scaling on Meta → Screenshot it and drop it into Stitch (powered by Gemini 3.1) → Stitch redesigns it with your brand's colors, fonts, and imagery using Nano Banana 2 → Edit sections visually — headlines, CTAs, layouts — without touching code → Export the code and paste it into Claude Code → Claude builds the full production site and deploys to Vercel or Netlify in 60 seconds No designer. No $3K per landing page. No Claude Code frontend that looks like a template from 2019. What you get: → Designer-quality landing pages and advertorials built in minutes, not weeks → Visual editing so you actually see the design before you code it → Nano Banana 2 generating on-brand product imagery and hero shots → A repeatable system — new angle, new page, same pipeline Built 100% with Google Stitch 2.0 + Claude Code. I put together a full playbook showing the exact workflow: how to find winning pages, redesign them in Stitch, and deploy with Claude Code. Want it for free? > Like this post > Comment "STITCH" And I'll send it over (must be following so I can DM)

Mike Futia

126,271 Aufrufe • vor 5 Monaten

I genuinely don't understand why everyone isn't using this yet Andrej Karpathy, a co-founder of OpenAI, posted a simple idea that hit 16 million views: stop using AI to write code, use it to build a second brain. You point Claude Code at a folder, drop in any source, an article, a transcript, a PDF, and Claude reads it, links it, and files it into a living wiki of everything you know. It compounds like interest, the more you feed it, the smarter it gets. Here's the whole thing: > Install Obsidian, create a vault, open it in Claude Code > Paste Karpathy's wiki idea file and tell Claude to build it > Claude makes three folders: raw for sources, wiki for its pages, a CLAUDE.md that runs it > Drop any source into raw and say "ingest this" > Ask questions across everything, forever Five minutes to set up, and you never start from a blank chat again. Full step-by-step guide with Claude and Obsidian, link below. Bookmark this

I genuinely don't understand why everyone isn't using this yet Andrej Karpathy, a co-founder of OpenAI, posted a simple idea that hit 16 million views: stop using AI to write code, use it to build a second brain. You point Claude Code at a folder, drop in any source, an article, a transcript, a PDF, and Claude reads it, links it, and files it into a living wiki of everything you know. It compounds like interest, the more you feed it, the smarter it gets. Here's the whole thing: > Install Obsidian, create a vault, open it in Claude Code > Paste Karpathy's wiki idea file and tell Claude to build it > Claude makes three folders: raw for sources, wiki for its pages, a CLAUDE.md that runs it > Drop any source into raw and say "ingest this" > Ask questions across everything, forever Five minutes to set up, and you never start from a blank chat again. Full step-by-step guide with Claude and Obsidian, link below. Bookmark this

Ridark

6,981,577 Aufrufe • vor 2 Monaten

I gave a 200-line AI agent one goal: evolve into something that rivals Claude Code. 🧬 It only has one power—the ability to modify its own source code. The rules are simple: every change must pass CI. Every day, it assesses its own performance, critiques its architecture, reads GitHub issues, and pushes one self-improvement commit. Day 1 starts today. Watch the evolution.

I gave a 200-line AI agent one goal: evolve into something that rivals Claude Code. 🧬 It only has one power—the ability to modify its own source code. The rules are simple: every change must pass CI. Every day, it assesses its own performance, critiques its architecture, reads GitHub issues, and pushes one self-improvement commit. Day 1 starts today. Watch the evolution.

Yuanhao

36,832 Aufrufe • vor 6 Monaten

A week ago I shipped a tiny bash + SQLite messaging layer for CLI AI agents, so Claude Code and Codex could stop using me as a copy-paste relay. Since then: 🌟 5 → 320+ stars 🍴 0 → 15 forks (3 derivative projects, incl. someone porting it to shogi) 🤝 PRs from strangers: Gemini, Antigravity, and now Copilot CLI support The demo that kicked it off (attached): two Claude Code instances in one project, autonomously playing tic-tac-toe — no human in the loop.

A week ago I shipped a tiny bash + SQLite messaging layer for CLI AI agents, so Claude Code and Codex could stop using me as a copy-paste relay. Since then: 🌟 5 → 320+ stars 🍴 0 → 15 forks (3 derivative projects, incl. someone porting it to shogi) 🤝 PRs from strangers: Gemini, Antigravity, and now Copilot CLI support The demo that kicked it off (attached): two Claude Code instances in one project, autonomously playing tic-tac-toe — no human in the loop.

Koichi

19,726 Aufrufe • vor 3 Monaten

I still don't understand why everyone is not using this yet. Thanks to it, a year ago I increased my income to 17,000 dollars a month Andrey Karpathy, co-founder of OpenAI, published a simple idea that got 16 million views: stop using AI to write code, use it to build a second brain You point Claude Code to a folder, drop any source in there (an article, transcript, PDF) and Claude reads it, links it, and saves it into a living wiki of everything you know. It compounds like interest: the more you feed it, the smarter it gets Here is the gist: Install Obsidian, create a vault, open it in Claude Code Paste the file with Karpathy's wiki idea and tell Claude to build it Claude creates three folders: raw for sources, wiki for its pages, CLAUDE which runs everything Drop any source into raw and say "ingest this" Ask questions across everything, forever Five minutes to set up, and you never start with an empty chat again The full step-by-step guide is in the article. Save to bookmarks

I still don't understand why everyone is not using this yet. Thanks to it, a year ago I increased my income to 17,000 dollars a month Andrey Karpathy, co-founder of OpenAI, published a simple idea that got 16 million views: stop using AI to write code, use it to build a second brain You point Claude Code to a folder, drop any source in there (an article, transcript, PDF) and Claude reads it, links it, and saves it into a living wiki of everything you know. It compounds like interest: the more you feed it, the smarter it gets Here is the gist: Install Obsidian, create a vault, open it in Claude Code Paste the file with Karpathy's wiki idea and tell Claude to build it Claude creates three folders: raw for sources, wiki for its pages, CLAUDE which runs everything Drop any source into raw and say "ingest this" Ask questions across everything, forever Five minutes to set up, and you never start with an empty chat again The full step-by-step guide is in the article. Save to bookmarks

Bober_smart

2,810,593 Aufrufe • vor 13 Tagen

this is f**king dangerous Most people treat Claude like a search bar. The ones with a second brain treat it as an intelligence layer on everything they know. Here's the 15-minute setup: → Install Claude Code → Install Obsidian, create a vault → Open it in Claude Code, drop in the CLAUDE.md schema — that one file is the engine → Throw any source in, say "ingest this" Done. From then on, everything you know is queryable by the most capable AI on earth. Claude wires each source against your whole vault and surfaces connections you forgot you had. Build it tonight. full A–Z guide below.

this is f**king dangerous Most people treat Claude like a search bar. The ones with a second brain treat it as an intelligence layer on everything they know. Here's the 15-minute setup: → Install Claude Code → Install Obsidian, create a vault → Open it in Claude Code, drop in the CLAUDE.md schema — that one file is the engine → Throw any source in, say "ingest this" Done. From then on, everything you know is queryable by the most capable AI on earth. Claude wires each source against your whole vault and surfaces connections you forgot you had. Build it tonight. full A–Z guide below.

Kirill

19,358 Aufrufe • vor 1 Monat

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE OPUS 5 + OBSIDIAN Andrej Karpathy (OpenAI co-founder) shared an architecture that turns Claude into a persistent second brain not just a basic chat window how it works: > point Claude Code at an Obsidian vault folder > drop articles, PDFs, or video transcripts into raw > Claude reads them, updates summaries, cross-references everything > the knowledge base compounds like interest, never resets on a new chat the setup: > install create a local vault folder > open it in Claude Code, paste Karpathy's wiki prompt > > let the agent build raw, wiki, and CLAUDE.md folders > drop any file into raw, tell it to ingest > ask questions, get compiled summaries back this skips rag overhead entirely. your vault stays organized on its own run ingest on a schedule and it's loop engineering: sense a new file, plan, write, verify, repeat how do you manage your local knowledge base?

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE OPUS 5 + OBSIDIAN Andrej Karpathy (OpenAI co-founder) shared an architecture that turns Claude into a persistent second brain not just a basic chat window how it works: > point Claude Code at an Obsidian vault folder > drop articles, PDFs, or video transcripts into raw > Claude reads them, updates summaries, cross-references everything > the knowledge base compounds like interest, never resets on a new chat the setup: > install create a local vault folder > open it in Claude Code, paste Karpathy's wiki prompt > > let the agent build raw, wiki, and CLAUDE.md folders > drop any file into raw, tell it to ingest > ask questions, get compiled summaries back this skips rag overhead entirely. your vault stays organized on its own run ingest on a schedule and it's loop engineering: sense a new file, plan, write, verify, repeat how do you manage your local knowledge base?

Mr. Buzzoni

15,609 Aufrufe • vor 16 Tagen

THIS GUY IS BUILDING INSANE CUSTOM SITES FOR $0.23 IN API COSTS WITH THE NEW KIMI K3 currently #1 on the coding arena. the video attached shows a complex, highly detailed website. it was coded entirely by a new model called Kimi K3. early testers are calling it scarily good because it quietly removes the need for complex agent swarms. here is the instant breakdown of what makes it terrifying. 1. native vision in the loop it iterates code while analyzing live screenshots of its own output. it literally looks at the site it builds and corrects the styling autonomously. 2. massive sparse architecture it has 2.8 trillion parameters but only activates 50b per token. this makes it insanely fast and allows for a native 1,000,000 token context window. 3. recursive self-improvement it spends a massive amount of compute on self-verification. it runs unit tests and simulates environments before giving you the final frontend code. 4. brutal economics it costs exactly $3 per million input tokens. the entire custom site in the video cost around $0.23 to generate. the era of orchestrating 12 dumb agents to build a simple web app is over. one smart instance is all you need.

THIS GUY IS BUILDING INSANE CUSTOM SITES FOR $0.23 IN API COSTS WITH THE NEW KIMI K3 currently #1 on the coding arena. the video attached shows a complex, highly detailed website. it was coded entirely by a new model called Kimi K3. early testers are calling it scarily good because it quietly removes the need for complex agent swarms. here is the instant breakdown of what makes it terrifying. 1. native vision in the loop it iterates code while analyzing live screenshots of its own output. it literally looks at the site it builds and corrects the styling autonomously. 2. massive sparse architecture it has 2.8 trillion parameters but only activates 50b per token. this makes it insanely fast and allows for a native 1,000,000 token context window. 3. recursive self-improvement it spends a massive amount of compute on self-verification. it runs unit tests and simulates environments before giving you the final frontend code. 4. brutal economics it costs exactly $3 per million input tokens. the entire custom site in the video cost around $0.23 to generate. the era of orchestrating 12 dumb agents to build a simple web app is over. one smart instance is all you need.

ard

91,882 Aufrufe • vor 1 Monat

19-year-old from china makes $9,000/month designing product sites and ships each one in an afternoon. here's his exact setup the whole thing runs on two tools that each do one job: > brief written by hand: 5 min > Moonchild builds the design system, then every screen from it: 20 min > MCP hands the design to Claude as real structure, not a screenshot: instant > Claude Code reads those exact tokens and builds the live app: 20 min > second Claude session reviews the build for drift: 10 min total: about an hour. screen five still matches screen one. no agency, no dev, no design team the trick is MCP. the design tool passes Claude the actual colors, components and layout, so it builds from the source instead of guessing from a picture. full pipeline, every prompt, in the article above.

19-year-old from china makes $9,000/month designing product sites and ships each one in an afternoon. here's his exact setup the whole thing runs on two tools that each do one job: > brief written by hand: 5 min > Moonchild builds the design system, then every screen from it: 20 min > MCP hands the design to Claude as real structure, not a screenshot: instant > Claude Code reads those exact tokens and builds the live app: 20 min > second Claude session reviews the build for drift: 10 min total: about an hour. screen five still matches screen one. no agency, no dev, no design team the trick is MCP. the design tool passes Claude the actual colors, components and layout, so it builds from the source instead of guessing from a picture. full pipeline, every prompt, in the article above.

Ridark

19,477 Aufrufe • vor 2 Monaten

if you use claude code, this will save you real money. the problem: every time you make an edit, your ai rereads the whole codebase to figure out what changed. tens of thousands of tokens, every turn, for context it already had. this repo fixes it. it’s called code review graph, and it just maps your entire codebase: every file, every function, every connection laid out so you can see the actual shape of your project how to set up (2 min): 1. pip install code-review-graph 2. code-review-graph install - auto-configures Claude Code, Cursor, Codex, Gemini CLI + more 3. code-review-graph build change one function, and it traces exactly what that touches... every caller, every dependent file, every test. your ai only reads what's affected, not the whole repo. and the savings are wild. a task that used to burn ~100,000 tokens (about a dollar) now runs closer to a penny.

if you use claude code, this will save you real money. the problem: every time you make an edit, your ai rereads the whole codebase to figure out what changed. tens of thousands of tokens, every turn, for context it already had. this repo fixes it. it’s called code review graph, and it just maps your entire codebase: every file, every function, every connection laid out so you can see the actual shape of your project how to set up (2 min): 1. pip install code-review-graph 2. code-review-graph install - auto-configures Claude Code, Cursor, Codex, Gemini CLI + more 3. code-review-graph build change one function, and it traces exactly what that touches... every caller, every dependent file, every test. your ai only reads what's affected, not the whole repo. and the savings are wild. a task that used to burn ~100,000 tokens (about a dollar) now runs closer to a penny.

Alvaro Cintas

75,323 Aufrufe • vor 1 Monat

Every serious Claude Code user is using this repo. if you're not, you're leaving 90% of Claude Code's power on the table. It's called claude-code-best-practice - 84 sourced tips, implementation examples for every major feature, workflow comparisons across 8 major repos, and the actual tips from Boris Cherny (creator of Claude Code) compiled in one place. Here's what's actually in it: → 84 tips organized by category -- prompting, planning, CLAUDE.md, agents, commands, skills, hooks, workflows, debugging, utilities, daily habits → best practice + implemented examples for every core concept: subagents, commands, skills, hooks, MCP servers, plugins, settings, memory, checkpointing, CLI flags → workflow comparison table -- Superpowers, BMAD-METHOD, Get Shit Done, OpenSpec, gstack, HumanLayer -- what makes each unique, how many agents/commands/skills each has → orchestration workflow -- Command → Agent → Skill pattern with a live demo → Boris Cherny tips compiled across 3 tweet threads (13 + 10 + 12 tips) and 5 podcast/video appearances → "billion dollar questions" section -- open questions about CLAUDE.md, agents vs commands vs skills, specs -- that nobody has definitively answered yet here's a few of the tips that actually change how you use it: → use subagents with "say use subagents" to throw more compute at a problem -- offload tasks to keep your main context clean → spin up a second Claude to review your plan as a staff engineer before executing → CLAUDE.md should target under 200 lines -- wrap domain-specific rules in ` ` tags so Claude doesn't ignore them as files grow → compress KV context at max 50%, not at the end -- avoid the "agent dumb zone" by doing manual /compact proactively → after a mediocre fix: "knowing everything you know now, scrap this and implement the elegant solution" was #1 trending on GitHub in March 2026. 19.7K GitHub stars. 1.7K forks. MIT license. 100% open source. (link in the comments)

Every serious Claude Code user is using this repo. if you're not, you're leaving 90% of Claude Code's power on the table. It's called claude-code-best-practice - 84 sourced tips, implementation examples for every major feature, workflow comparisons across 8 major repos, and the actual tips from Boris Cherny (creator of Claude Code) compiled in one place. Here's what's actually in it: → 84 tips organized by category -- prompting, planning, CLAUDE.md, agents, commands, skills, hooks, workflows, debugging, utilities, daily habits → best practice + implemented examples for every core concept: subagents, commands, skills, hooks, MCP servers, plugins, settings, memory, checkpointing, CLI flags → workflow comparison table -- Superpowers, BMAD-METHOD, Get Shit Done, OpenSpec, gstack, HumanLayer -- what makes each unique, how many agents/commands/skills each has → orchestration workflow -- Command → Agent → Skill pattern with a live demo → Boris Cherny tips compiled across 3 tweet threads (13 + 10 + 12 tips) and 5 podcast/video appearances → "billion dollar questions" section -- open questions about CLAUDE.md, agents vs commands vs skills, specs -- that nobody has definitively answered yet here's a few of the tips that actually change how you use it: → use subagents with "say use subagents" to throw more compute at a problem -- offload tasks to keep your main context clean → spin up a second Claude to review your plan as a staff engineer before executing → CLAUDE.md should target under 200 lines -- wrap domain-specific rules in ` ` tags so Claude doesn't ignore them as files grow → compress KV context at max 50%, not at the end -- avoid the "agent dumb zone" by doing manual /compact proactively → after a mediocre fix: "knowing everything you know now, scrap this and implement the elegant solution" was #1 trending on GitHub in March 2026. 19.7K GitHub stars. 1.7K forks. MIT license. 100% open source. (link in the comments)

Sukh Sroay

113,759 Aufrufe • vor 4 Monaten

Claude Fable 5 orchestrating Grok 4.5 is now my favorite real workflow. all you need is this free Claude Code plugin that makes Grok the default implementer. Fable writes the specs and reviews every diff, Grok 4.5 does the typing through the Grok CLI. - Grok handles the volume, Fable handles the judgment - Every diff gets cross-vendor review for free - Specs run as parallel agents when they're independent I've been testing it for a few days and the part that sold me is watching Fable refuse to write code. It sends specs down, judges what comes back, and that's it. setup: 1. claude plugin marketplace add DannyMac180/fable-advisor && claude plugin install fable-advisor 2. Install the Grok CLI from then grok login 3. /model fable It's open source, so you can read the agent files and tweak the routing however you want.

Claude Fable 5 orchestrating Grok 4.5 is now my favorite real workflow. all you need is this free Claude Code plugin that makes Grok the default implementer. Fable writes the specs and reviews every diff, Grok 4.5 does the typing through the Grok CLI. - Grok handles the volume, Fable handles the judgment - Every diff gets cross-vendor review for free - Specs run as parallel agents when they're independent I've been testing it for a few days and the part that sold me is watching Fable refuse to write code. It sends specs down, judges what comes back, and that's it. setup: 1. claude plugin marketplace add DannyMac180/fable-advisor && claude plugin install fable-advisor 2. Install the Grok CLI from then grok login 3. /model fable It's open source, so you can read the agent files and tweak the routing however you want.

Alvaro Cintas

100,558 Aufrufe • vor 1 Monat

Claude Code + Meta Ads CLI is f*cking wild 🤯 I just replaced 80% of my Meta Ads reporting workflow inside Claude Code. All without logging into Ads Manager. Perfect for DTC brands and creative agencies who are sick of logging into Ads Manager, exporting CSVs, and rebuilding the same dashboards every Monday. This setup eliminates the entire loop: → Plug Meta's official Ads CLI into Claude Code → Type one sentence describing the report you want → Claude pulls the data, builds the artifact, and saves it to your folder → HTML dashboards, comparison tables, written briefs → Run it weekly, monthly, anytime a client asks for something custom No CSV exports. No Looker setup. No copy-pasting numbers into decks. What you get: → A live dashboard with KPI cards, top 10 ad set ranking, daily spend chart, and sortable table — built in 90 seconds → Week-over-week comparison reports with CTR drops and CPC spikes flagged automatically → Creative fatigue audits that flag dying ads before CPAs blow up → One-page executive briefs with winners, losers, action items, and recommendations → Anomaly reports that surface every metric deviation over 25% Built 100% in Claude Code with the official Meta CLI. No third-party connector means no ban risk. I put together the complete playbook with the 15-minute setup and a step-by-step Loom video showing you the full install. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Claude Code + Meta Ads CLI is f*cking wild 🤯 I just replaced 80% of my Meta Ads reporting workflow inside Claude Code. All without logging into Ads Manager. Perfect for DTC brands and creative agencies who are sick of logging into Ads Manager, exporting CSVs, and rebuilding the same dashboards every Monday. This setup eliminates the entire loop: → Plug Meta's official Ads CLI into Claude Code → Type one sentence describing the report you want → Claude pulls the data, builds the artifact, and saves it to your folder → HTML dashboards, comparison tables, written briefs → Run it weekly, monthly, anytime a client asks for something custom No CSV exports. No Looker setup. No copy-pasting numbers into decks. What you get: → A live dashboard with KPI cards, top 10 ad set ranking, daily spend chart, and sortable table — built in 90 seconds → Week-over-week comparison reports with CTR drops and CPC spikes flagged automatically → Creative fatigue audits that flag dying ads before CPAs blow up → One-page executive briefs with winners, losers, action items, and recommendations → Anomaly reports that surface every metric deviation over 25% Built 100% in Claude Code with the official Meta CLI. No third-party connector means no ban risk. I put together the complete playbook with the 15-minute setup and a step-by-step Loom video showing you the full install. Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

23,688 Aufrufe • vor 3 Monaten

I just built a skill that lets Claude Code watch & analyze ANY video 🤯 Drop in any video file — UGC ads, competitor Meta ads, organic TikToks, screen recordings — and Claude hands you back a full creative teardown. All inside Claude Code. Perfect for media buyers and creative strategists who reverse-engineer competitor ads every week — and lose half a day doing it by hand. If your creative process starts with studying what's already working, you're scrubbing through competitor ads frame by frame, pausing to write down every hook, screenshotting the on-screen text, and by the tenth video you can't remember what made the first one land... This skill solves it: → Drop any video file into Claude Code → Skill routes it through the Gemini API for native video understanding → Returns a full creative teardown — hook breakdown, target audience, angle, beat-by-beat, on-screen text verbatim → Surfaces the steal-worthy patterns you can apply to your own creative → Same skill works on UGC ads, produced video ads, organic TikToks, and Loom recordings No manual scrubbing. No pausing every 5 seconds. No $200/mo ad intelligence platform. What you get: → Native video understanding via Gemini (not just transcripts) → Structured analysis — hook, angle, audience, pain point, CTA → Verbatim on-screen text and dialogue with timestamps → Hook variations generated directly from competitor ads → About 27 cents per 30-minute video Built 100% in Claude Code with the Gemini API. I recorded a full breakdown showing exactly how I built this, and I'm giving away the skill for free. Want the skill? > Like this post > Comment "CLAUDE" And I'll send it over (must be following so I can DM)

I just built a skill that lets Claude Code watch & analyze ANY video 🤯 Drop in any video file — UGC ads, competitor Meta ads, organic TikToks, screen recordings — and Claude hands you back a full creative teardown. All inside Claude Code. Perfect for media buyers and creative strategists who reverse-engineer competitor ads every week — and lose half a day doing it by hand. If your creative process starts with studying what's already working, you're scrubbing through competitor ads frame by frame, pausing to write down every hook, screenshotting the on-screen text, and by the tenth video you can't remember what made the first one land... This skill solves it: → Drop any video file into Claude Code → Skill routes it through the Gemini API for native video understanding → Returns a full creative teardown — hook breakdown, target audience, angle, beat-by-beat, on-screen text verbatim → Surfaces the steal-worthy patterns you can apply to your own creative → Same skill works on UGC ads, produced video ads, organic TikToks, and Loom recordings No manual scrubbing. No pausing every 5 seconds. No $200/mo ad intelligence platform. What you get: → Native video understanding via Gemini (not just transcripts) → Structured analysis — hook, angle, audience, pain point, CTA → Verbatim on-screen text and dialogue with timestamps → Hook variations generated directly from competitor ads → About 27 cents per 30-minute video Built 100% in Claude Code with the Gemini API. I recorded a full breakdown showing exactly how I built this, and I'm giving away the skill for free. Want the skill? > Like this post > Comment "CLAUDE" And I'll send it over (must be following so I can DM)

Mike Futia

41,932 Aufrufe • vor 2 Monaten

here's how the whole thing works. claude code doesn't care what's behind the API. it just sends requests and expects responses. so i pointed it at my own machine instead of anthropic's servers. llama-server runs the model locally. LiteLLM sits in between and translates the API format. claude code thinks it's talking to claude. it's talking to qwen on localhost. the setup: 2x 3090s, 38 layers on GPU, 10 on CPU. 128K context window. generation is only 7 tok/s but the tradeoff is worth it. 128K means the agent can hold an entire project in memory without losing context midtask. claude code alone loads a 17.5K token system prompt on every request. tool definitions, safety rules, agent behavior. that's your baseline before you even say hello. pushed as far as i could tonight. what surprised me most wasn't the speed. it was the iteration quality. first prompt gave me a working particle sim. second prompt, the model read its own 564 lines, understood the architecture, and added trails, explosions, gravity wells, bloom effects. no handholding. 4bit quantized. 45GB on two consumer cards. running a full coding agent autonomously. detailed article coming. full benchmarks, hardware breakdowns, engine debugging, code quality. everything from setup to what broke and why.

here's how the whole thing works. claude code doesn't care what's behind the API. it just sends requests and expects responses. so i pointed it at my own machine instead of anthropic's servers. llama-server runs the model locally. LiteLLM sits in between and translates the API format. claude code thinks it's talking to claude. it's talking to qwen on localhost. the setup: 2x 3090s, 38 layers on GPU, 10 on CPU. 128K context window. generation is only 7 tok/s but the tradeoff is worth it. 128K means the agent can hold an entire project in memory without losing context midtask. claude code alone loads a 17.5K token system prompt on every request. tool definitions, safety rules, agent behavior. that's your baseline before you even say hello. pushed as far as i could tonight. what surprised me most wasn't the speed. it was the iteration quality. first prompt gave me a working particle sim. second prompt, the model read its own 564 lines, understood the architecture, and added trails, explosions, gravity wells, bloom effects. no handholding. 4bit quantized. 45GB on two consumer cards. running a full coding agent autonomously. detailed article coming. full benchmarks, hardware breakdowns, engine debugging, code quality. everything from setup to what broke and why.

Sudo su

37,623 Aufrufe • vor 6 Monaten