Загрузка видео...

Не удалось загрузить видео

На главную

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

EvanLuthra's profile picture

Evan Luthra

395,072 subscribers

36,455 просмотров • 1 месяц назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

New feature in Claude Code 2.1.14 just dropped! You can now search and install plugins from the marketplaces installed in your current Claude Code session. This is huge if you’re building plugins on top of Claude Code’s marketplace layer (Skills, Agents, Hooks, etc). How it works: - Run /plugin - The official Claude marketplace is installed by default - Use the search bar to find the plugin you want - Select one or multiple plugins with space, then press i to install - Go to the Installed tab to browse and enable them With the exponential growth of Skills and Agent-based components running in the CLI, improving plugin discoverability is a big win. Pretty sure more marketplace-related features are coming
0:15

New feature in Claude Code 2.1.14 just dropped! You can now search and install plugins from the marketplaces installed in your current Claude Code session. This is huge if you’re building plugins on top of Claude Code’s marketplace layer (Skills, Agents, Hooks, etc). How it works: - Run /plugin - The official Claude marketplace is installed by default - Use the search bar to find the plugin you want - Select one or multiple plugins with space, then press i to install - Go to the Installed tab to browse and enable them With the exponential growth of Skills and Agent-based components running in the CLI, improving plugin discoverability is a big win. Pretty sure more marketplace-related features are coming

Daniel San

40,994 просмотров • 6 месяцев назад

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 subagents, each in its own context → plan mode before it touches a single file → MCP servers configured by the agent itself via /mcp-config → plugs into Zed, JetBrains, and VS Code → one binary, no Node setup, starts in milliseconds The CLI costs $0. K3 behind it starts at $3 per million tokens. Grab it for free👇
0:17

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 subagents, each in its own context → plan mode before it touches a single file → MCP servers configured by the agent itself via /mcp-config → plugs into Zed, JetBrains, and VS Code → one binary, no Node setup, starts in milliseconds The CLI costs $0. K3 behind it starts at $3 per million tokens. Grab it for free👇

darkzodchi

404,945 просмотров • 1 месяц назад

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.
0:10

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,215 просмотров • 1 месяц назад

🚨 Anthropic just made Claude Code remote-controlled. Meet Channels. You can now: → Connect a persistent local Claude session directly to a Discord or Telegram Bot → Message tasks to your bot on the go → Come back to finished code 🔥 Here’s how to set it up: 1️⃣ Create a bot (via Telegram’s BotFather or the Discord Dev Portal) and copy the token 2️⃣ Inside Claude, run /plugin install telegram@claude-plugins-official (or discord) 3️⃣ Configure the token and relaunch your session with the --channels flag 4️⃣ DM your new bot, grab the 6-character code, and pair it to your session! Message the bot to fetch files, read history, and execute code locally while you are on the go. The flexibility is unmatched. Time to spin up your bot 👀
0:17

🚨 Anthropic just made Claude Code remote-controlled. Meet Channels. You can now: → Connect a persistent local Claude session directly to a Discord or Telegram Bot → Message tasks to your bot on the go → Come back to finished code 🔥 Here’s how to set it up: 1️⃣ Create a bot (via Telegram’s BotFather or the Discord Dev Portal) and copy the token 2️⃣ Inside Claude, run /plugin install telegram@claude-plugins-official (or discord) 3️⃣ Configure the token and relaunch your session with the --channels flag 4️⃣ DM your new bot, grab the 6-character code, and pair it to your session! Message the bot to fetch files, read history, and execute code locally while you are on the go. The flexibility is unmatched. Time to spin up your bot 👀

Charly Wargnier

14,611 просмотров • 4 месяцев назад

OpenAI’s GPT-5.6 Sol model can now run inside Claude Code. There are two ways to do it, and both take minutes to set up, here’s how: Option 1, the official plugin: /plugin marketplace add openai/codex-plugin-cc /plugin install codex@openai-codex /reload-plugins, then /codex:setup That unlocks /codex:review, /codex:adversarial-review, and /codex:rescue. Claude writes, GPT critiques, you ship. Option 2, the proxy. One alias makes Sol your main model: alias claudex=‘CLAUDE_CODE_SUBAGENT_MODEL=gpt-5.6-sol CLAUDE_CODE_ALWAYS_ENABLE_EFFORT=1 claude –model gpt-5.6-sol’ Bonus: Claude Code lets you set subagent model and effort yourself. Sol Ultra runs can burn several times the tokens of a base run, so right-sizing delegated work saves real money.
0:15

OpenAI’s GPT-5.6 Sol model can now run inside Claude Code. There are two ways to do it, and both take minutes to set up, here’s how: Option 1, the official plugin: /plugin marketplace add openai/codex-plugin-cc /plugin install codex@openai-codex /reload-plugins, then /codex:setup That unlocks /codex:review, /codex:adversarial-review, and /codex:rescue. Claude writes, GPT critiques, you ship. Option 2, the proxy. One alias makes Sol your main model: alias claudex=‘CLAUDE_CODE_SUBAGENT_MODEL=gpt-5.6-sol CLAUDE_CODE_ALWAYS_ENABLE_EFFORT=1 claude –model gpt-5.6-sol’ Bonus: Claude Code lets you set subagent model and effort yourself. Sol Ultra runs can burn several times the tokens of a base run, so right-sizing delegated work saves real money.

Alvaro Cintas

90,228 просмотров • 1 месяц назад

Claude Code Scheduled Tasks is now available... here's a solid idea to connect it with Telegram Save this so you don't forget to set it up! First, ask Claude to add a simple Telegram messaging module to your repo. You can use the Telegram Bot Builder Skill from Link: Install command: npx claude-code-templates@latest --skill enterprise-communication/telegram-bot-builder Once the module is in your project, grab your bot credentials from BotFather and add the bot ID to your .env file That's it! ✅ Now every Scheduled Task you create should end with an instruction for Claude to send the task result to Telegram using that module. Claude will handle the delivery automatically on every task it runs
0:18

Claude Code Scheduled Tasks is now available... here's a solid idea to connect it with Telegram Save this so you don't forget to set it up! First, ask Claude to add a simple Telegram messaging module to your repo. You can use the Telegram Bot Builder Skill from Link: Install command: npx claude-code-templates@latest --skill enterprise-communication/telegram-bot-builder Once the module is in your project, grab your bot credentials from BotFather and add the bot ID to your .env file That's it! ✅ Now every Scheduled Task you create should end with an instruction for Claude to send the task result to Telegram using that module. Claude will handle the delivery automatically on every task it runs

Daniel San

91,123 просмотров • 5 месяцев назад

Claude Code Desktop now opens a new window for each session This makes it much easier to visualize multiple Claude Code agents running in parallel My current stack depends on the task: - Ghostty: when starting a project. Bash commands, git, env variables, provider connections. All manual through the terminal with a Claude panel running alongside. - Claude Code Desktop: once everything is configured. GitHub connected, CLAUDE.md, Skills, subagents and Hooks ready. Claude Code runs on its own, no more terminal setup, just panels running and outputs to review. - VSCode: when I need to review code by hand. I use it less and less, but there are moments where I have to confirm Claude got it right. I usually open the Claude extension inside VSCode, but it lacks most of the CLI features so it's limited Solid update. Worth trying once your workflows are already set up 👇
0:16

Claude Code Desktop now opens a new window for each session This makes it much easier to visualize multiple Claude Code agents running in parallel My current stack depends on the task: - Ghostty: when starting a project. Bash commands, git, env variables, provider connections. All manual through the terminal with a Claude panel running alongside. - Claude Code Desktop: once everything is configured. GitHub connected, CLAUDE.md, Skills, subagents and Hooks ready. Claude Code runs on its own, no more terminal setup, just panels running and outputs to review. - VSCode: when I need to review code by hand. I use it less and less, but there are moments where I have to confirm Claude got it right. I usually open the Claude extension inside VSCode, but it lacks most of the CLI features so it's limited Solid update. Worth trying once your workflows are already set up 👇

Daniel San

38,806 просмотров • 2 месяцев назад

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.
0:12

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 просмотров • 5 месяцев назад

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.
0:18

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,402 просмотров • 2 месяцев назад

My project has 39,205 lines of code, and Cursor can't answer questions about it. Cursor's context seems to be capped at around 10,000 tokens. Unfortunately, this is not enough for any decent-sized project. If you have a large codebase, check out Augment Code. This thing is faaaast! I'm currently using their Visual Studio Code plugin, but you can also use them on JetBrains, Neovim, and even Vim. (I'm a Neovim fan, but Copilot's implementation for Neovim is nowhere as good as Augment Code.) Augment Code was gracious enough to sponsor this post. After you install their extension and run it for the first time, it will index your entire codebase. This is why it can answer questions as fast as it does, regardless of the size of your codebase. Augment Code supports chat and completions like every other AI coding assistant, but its killer feature is "Next Edit." When you make a change, two things happen: 1. The model analyzes the change to determine the ripple effects across your *entire* codebase. 2. The model suggests everything you need to update to ensure everything works correctly. This is pretty wild!
0:19

My project has 39,205 lines of code, and Cursor can't answer questions about it. Cursor's context seems to be capped at around 10,000 tokens. Unfortunately, this is not enough for any decent-sized project. If you have a large codebase, check out Augment Code. This thing is faaaast! I'm currently using their Visual Studio Code plugin, but you can also use them on JetBrains, Neovim, and even Vim. (I'm a Neovim fan, but Copilot's implementation for Neovim is nowhere as good as Augment Code.) Augment Code was gracious enough to sponsor this post. After you install their extension and run it for the first time, it will index your entire codebase. This is why it can answer questions as fast as it does, regardless of the size of your codebase. Augment Code supports chat and completions like every other AI coding assistant, but its killer feature is "Next Edit." When you make a change, two things happen: 1. The model analyzes the change to determine the ripple effects across your *entire* codebase. 2. The model suggests everything you need to update to ensure everything works correctly. This is pretty wild!

Santiago

247,833 просмотров • 1 год назад

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)
0:14

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 просмотров • 4 месяцев назад

herdr 0.7.0 is out, and it's a major one: it introduces plugins! the idea is simple: herdr stays lean, and everything custom gets extended through plugins. shareable, scoped, built however you want, to fit your own flow. with this release we're also shipping a few examples of what the plugin system can do. first up: a telegram plugin. herdr already controls your agents and knows their status, so the plugin just hooks into agent events and pings telegram the moment one needs you. notification lands → `herdr --remote` or ssh from your phone → straight back to the agent that needs you.
0:18

herdr 0.7.0 is out, and it's a major one: it introduces plugins! the idea is simple: herdr stays lean, and everything custom gets extended through plugins. shareable, scoped, built however you want, to fit your own flow. with this release we're also shipping a few examples of what the plugin system can do. first up: a telegram plugin. herdr already controls your agents and knows their status, so the plugin just hooks into agent events and pings telegram the moment one needs you. notification lands → `herdr --remote` or ssh from your phone → straight back to the agent that needs you.

herdr

93,374 просмотров • 2 месяцев назад

No way I'm sharing this for free I just found a tool that lets you drop a whole video template into Claude and it breaks it down for you clip by clip. then Claude can swap the character for a new one rewrite the entire script in your tone even make the video longer if you want. the crazy part is it does it all in one go from your conversation. RT + comment "tool" and I'll send you the link
0:15

No way I'm sharing this for free I just found a tool that lets you drop a whole video template into Claude and it breaks it down for you clip by clip. then Claude can swap the character for a new one rewrite the entire script in your tone even make the video longer if you want. the crazy part is it does it all in one go from your conversation. RT + comment "tool" and I'll send you the link

Ahmad

31,959 просмотров • 3 месяцев назад

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
0:16

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,946,976 просмотров • 1 месяц назад

Claude Design + Shopify is f*cking ridiculous 🤯 You can now publish pages from Claude Design → Claude Code → Shopify. Built 100% with Claude Design, Claude Code, and the Shopify CLI. Perfect for DTC brands and agencies who want to skip the design → dev handoff entirely. Here's how it works: → Design any landing page in Claude Design → Export as a zip and drop it into Claude Code → Install the Shopify + Shopify AI Toolkit plugins → Prompt Claude to convert the HTML into a Shopify page template + push to live theme → Claude uploads the images, deploys the files, and creates a published page No more handing designs off to a dev and waiting 2 weeks for a Shopify page. What you get: - A workflow that turns any Claude Design page into a real Shopify page template - Editable sections so your marketing team can swap copy, images, and CTAs without code - Images uploaded straight to Shopify Files automatically - A files-only deploy that only touches what's new in your live theme - A repeatable pipeline you can use every time you design a new landing page This is essentially the design-to-deploy pipeline brands have been waiting for. I put together a step-by-step playbook for going from Claude Design → published Shopify page. Every install, every plugin, every command, and the exact prompt that runs the whole thing. Want the playbook for free? > Like this post > Comment "SHOP" And I'll send it over (must be following so I can DM)
0:17

Claude Design + Shopify is f*cking ridiculous 🤯 You can now publish pages from Claude Design → Claude Code → Shopify. Built 100% with Claude Design, Claude Code, and the Shopify CLI. Perfect for DTC brands and agencies who want to skip the design → dev handoff entirely. Here's how it works: → Design any landing page in Claude Design → Export as a zip and drop it into Claude Code → Install the Shopify + Shopify AI Toolkit plugins → Prompt Claude to convert the HTML into a Shopify page template + push to live theme → Claude uploads the images, deploys the files, and creates a published page No more handing designs off to a dev and waiting 2 weeks for a Shopify page. What you get: - A workflow that turns any Claude Design page into a real Shopify page template - Editable sections so your marketing team can swap copy, images, and CTAs without code - Images uploaded straight to Shopify Files automatically - A files-only deploy that only touches what's new in your live theme - A repeatable pipeline you can use every time you design a new landing page This is essentially the design-to-deploy pipeline brands have been waiting for. I put together a step-by-step playbook for going from Claude Design → published Shopify page. Every install, every plugin, every command, and the exact prompt that runs the whole thing. Want the playbook for free? > Like this post > Comment "SHOP" And I'll send it over (must be following so I can DM)

Mike Futia

58,078 просмотров • 3 месяцев назад

SOMEONE TURNED 33 PILES OF DEAD BOOKMARKS INTO A GRAVITY MAP CLAUDE REBUILDS ITSELF EVERY NIGHT - AND IT RUNS ON THE 80% OF CLAUDE NOBODY TOUCHES most people drive Claude Code like a chatbot with file access - type a prompt, watch it edit, move on. that's maybe 20% of the tool this is the opposite. she's not typing at Claude. she's running it - loops on a mac mini overnight, claude linking every node while she sleeps the gravity map in the video is just the 80% maxed out: 1 system that organizes itself, not a human babysitting a chat box the other 80% is a steering layer Anthropic shipped quietly on june 18 - 7 ways to instruct the model, and a stack of commands almost nobody opens /context to see your bloat. /clear between tasks. path-scoped rules, subagents, hooks - conventions that load themselves the exact second they matter i stopped typing at Claude months ago - now i configure it once and it shows up already running the work, 10x cleaner a prompt helps for 1 message. the steering layer pays you back every session, for life the people who learn it stop being users and become operators - everyone else is still arguing about which model is smartest the article below is the full map - all 4 layers, every file and command, start to finish
0:19

SOMEONE TURNED 33 PILES OF DEAD BOOKMARKS INTO A GRAVITY MAP CLAUDE REBUILDS ITSELF EVERY NIGHT - AND IT RUNS ON THE 80% OF CLAUDE NOBODY TOUCHES most people drive Claude Code like a chatbot with file access - type a prompt, watch it edit, move on. that's maybe 20% of the tool this is the opposite. she's not typing at Claude. she's running it - loops on a mac mini overnight, claude linking every node while she sleeps the gravity map in the video is just the 80% maxed out: 1 system that organizes itself, not a human babysitting a chat box the other 80% is a steering layer Anthropic shipped quietly on june 18 - 7 ways to instruct the model, and a stack of commands almost nobody opens /context to see your bloat. /clear between tasks. path-scoped rules, subagents, hooks - conventions that load themselves the exact second they matter i stopped typing at Claude months ago - now i configure it once and it shows up already running the work, 10x cleaner a prompt helps for 1 message. the steering layer pays you back every session, for life the people who learn it stop being users and become operators - everyone else is still arguing about which model is smartest the article below is the full map - all 4 layers, every file and command, start to finish

KingWilliam

12,305 просмотров • 1 месяц назад

SOMEONE BUILT A CLAUDE CODE PLUGIN THAT REFUSES TO WORK UNTIL YOU DO PUSH-UPS OR SQUATS its called workout gate and it is exactly as cursed as it sounds when the hook fires, it blocks your prompt, opens your webcam, and makes you exercise to keep coding > it counts your reps live through the webcam with mediapipe, no honor system rounding down > only releases your prompt once you actually finish the reps > quit halfway and the leftover reps get saved as debt for your next session > chill, demo and hardcore presets, plus prompt based, time based or random triggers > tracks stats, streaks and personal records right in the claude code statusline we automated the coding, now we're automating the part where we actually take care of ourselves
0:12

SOMEONE BUILT A CLAUDE CODE PLUGIN THAT REFUSES TO WORK UNTIL YOU DO PUSH-UPS OR SQUATS its called workout gate and it is exactly as cursed as it sounds when the hook fires, it blocks your prompt, opens your webcam, and makes you exercise to keep coding > it counts your reps live through the webcam with mediapipe, no honor system rounding down > only releases your prompt once you actually finish the reps > quit halfway and the leftover reps get saved as debt for your next session > chill, demo and hardcore presets, plus prompt based, time based or random triggers > tracks stats, streaks and personal records right in the claude code statusline we automated the coding, now we're automating the part where we actually take care of ourselves

Om Patel

670,732 просмотров • 2 месяцев назад

one of my favorite ways to use claude code skills right now - combining remotion with claude-in-chrome for motion video creation. the workflow is addictive. the clip you see here was produced with minimal prompting effort let me know if you would like me to write a full break down of this process. you describe to claude code what you want, claude code writes the remotion components, opens the remotion studio (via browser) with claude-in-chrome, sees the actual rendered output, and iterates on it in real time. need the arrows pointing to the center of the bubbles instead of the edge? just say it. need the layout shifted to the center? say it. claude sees the preview, adjusts the code, re-renders. then when you're happy you tell claude code to render the final video. but skills are what make this possible. remotion knowledge + browser automation + the taste to iterate visually. no copy pasting screenshots back and forth. no "can you try moving it 10px to the right" over chat. it just looks and fixes. this is the kind of workflow that makes you realize how much further claude code can go beyond just writing code in a terminal. i didn't touch any code while working on the clip you see if you haven't tried combining skills together like this - start experimenting. the skills combos is where the magic is at.
0:16

one of my favorite ways to use claude code skills right now - combining remotion with claude-in-chrome for motion video creation. the workflow is addictive. the clip you see here was produced with minimal prompting effort let me know if you would like me to write a full break down of this process. you describe to claude code what you want, claude code writes the remotion components, opens the remotion studio (via browser) with claude-in-chrome, sees the actual rendered output, and iterates on it in real time. need the arrows pointing to the center of the bubbles instead of the edge? just say it. need the layout shifted to the center? say it. claude sees the preview, adjusts the code, re-renders. then when you're happy you tell claude code to render the final video. but skills are what make this possible. remotion knowledge + browser automation + the taste to iterate visually. no copy pasting screenshots back and forth. no "can you try moving it 10px to the right" over chat. it just looks and fixes. this is the kind of workflow that makes you realize how much further claude code can go beyond just writing code in a terminal. i didn't touch any code while working on the clip you see if you haven't tried combining skills together like this - start experimenting. the skills combos is where the magic is at.

elvis

46,494 просмотров • 6 месяцев назад

I just built a complete SEO audit plugin in Claude Code that replaces your $200/mo Ahrefs subscription 🤯 One Claude Plugin audits any store: technical SEO, product schema, content, Core Web Vitals, and AI-search readiness. Parallel agents, a 0-100 score, and a dashboard that renders right in the panel. All inside Claude Code. So I pointed it at Ridge .com, one of the sharpest DTC operators out there. It came back 56/100, and what stood out wasn't a knock on them at all: Ridge has a better AI-commerce setup than 99% of stores. A real llms.txt, an agent-discovery sitemap, a live MCP endpoint, genuinely ahead of the curve. And even on a store that dialed-in, the audit surfaced fixable gaps in ~90 seconds: → Room to add product structured data → A mobile Core Web Vitals score worth tightening → A thin meta description on a high-traffic collection Perfect for e-comm operators and SEO agencies who are sick of paying $200/mo for tools that bury the real issues, running quarterly audits that take a week, and shipping reports nobody can act on. So I put together the full playbook to build your own. The complete guide to building this Plugin in Claude Code: branded to you, tuned to exactly how you audit, repeatable across every client. The kind of audit you run in minutes and hand over as a deliverable that looks like it cost thousands. What's inside: → The architecture (orchestrator + parallel sub-agents) → How to fetch any store past Cloudflare → The 0-100 scoring + falsifiable-findings framework → How to ship the HTML dashboard for client demos → The full build, start to finish Want the playbook for free? > Like this post > Comment "SEO" And I'll send it over (must be following so I can DM)
0:17

I just built a complete SEO audit plugin in Claude Code that replaces your $200/mo Ahrefs subscription 🤯 One Claude Plugin audits any store: technical SEO, product schema, content, Core Web Vitals, and AI-search readiness. Parallel agents, a 0-100 score, and a dashboard that renders right in the panel. All inside Claude Code. So I pointed it at Ridge .com, one of the sharpest DTC operators out there. It came back 56/100, and what stood out wasn't a knock on them at all: Ridge has a better AI-commerce setup than 99% of stores. A real llms.txt, an agent-discovery sitemap, a live MCP endpoint, genuinely ahead of the curve. And even on a store that dialed-in, the audit surfaced fixable gaps in ~90 seconds: → Room to add product structured data → A mobile Core Web Vitals score worth tightening → A thin meta description on a high-traffic collection Perfect for e-comm operators and SEO agencies who are sick of paying $200/mo for tools that bury the real issues, running quarterly audits that take a week, and shipping reports nobody can act on. So I put together the full playbook to build your own. The complete guide to building this Plugin in Claude Code: branded to you, tuned to exactly how you audit, repeatable across every client. The kind of audit you run in minutes and hand over as a deliverable that looks like it cost thousands. What's inside: → The architecture (orchestrator + parallel sub-agents) → How to fetch any store past Cloudflare → The 0-100 scoring + falsifiable-findings framework → How to ship the HTML dashboard for client demos → The full build, start to finish Want the playbook for free? > Like this post > Comment "SEO" And I'll send it over (must be following so I can DM)

Mike Futia

55,495 просмотров • 2 месяцев назад

Karpathy method + Claude Code reading your whole Obsidian vault is the smartest second brain on earth. The method is simple and brutal. If you can’t build a thing from scratch, you don’t know it. Tutorials are fake learning and your brain deletes them in 3 days. Most people ignore this. They build a second brain that just sits there, folders of notes nobody reopens, dead text. Point Claude Code at the vault and it wakes up. 5,000 notes, one mind. It reads all of it and answers in your own words and your own proofs, not a model’s guess. Then the loop closes. Want to understand neural nets? Skip the 3-hour video and ask Claude Code to build a tiny one. 200 lines from scratch. Watch it train, break a layer, watch it fail, fix it. It clicks in 20 minutes instead of 3 weeks. The second it lands the note gets written. One idea per file, linked to 10 others, dropped into the vault while the memory is still hot. Now it compounds. Month 1: is 60 notes. Month 6 is 900. Every new note pulls in old ones, so you ask anything and the answer comes from your brain, not the internet. Before: 40 tabs, 6 half read PDF, 0 retained. After: build it once, own it for life. Setup takes 4 minutes. Plain text, no lock-in. A second brain nobody reads is a graveyard. Yours just started thinking.
0:13

Karpathy method + Claude Code reading your whole Obsidian vault is the smartest second brain on earth. The method is simple and brutal. If you can’t build a thing from scratch, you don’t know it. Tutorials are fake learning and your brain deletes them in 3 days. Most people ignore this. They build a second brain that just sits there, folders of notes nobody reopens, dead text. Point Claude Code at the vault and it wakes up. 5,000 notes, one mind. It reads all of it and answers in your own words and your own proofs, not a model’s guess. Then the loop closes. Want to understand neural nets? Skip the 3-hour video and ask Claude Code to build a tiny one. 200 lines from scratch. Watch it train, break a layer, watch it fail, fix it. It clicks in 20 minutes instead of 3 weeks. The second it lands the note gets written. One idea per file, linked to 10 others, dropped into the vault while the memory is still hot. Now it compounds. Month 1: is 60 notes. Month 6 is 900. Every new note pulls in old ones, so you ask anything and the answer comes from your brain, not the internet. Before: 40 tabs, 6 half read PDF, 0 retained. After: build it once, own it for life. Setup takes 4 minutes. Plain text, no lock-in. A second brain nobody reads is a graveyard. Yours just started thinking.

West Lord

591,602 просмотров • 1 месяц назад