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.

I’ve been using Claude Code’s Concise Output Style and it makes the experience much cleaner I’d combine it with these settings: - Output Style: Concise Straight to the answer, no preambles or unnecessary narration - spinnerTipsEnabled: false No tips while Claude is thinking - awaySummaryEnabled: false No recap when... show more

Daniel San

33,644 subscribers

34,768 views • 12 days 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

Opus 4.6 lets you set the effort level Not every task needs high reasoning. For simpler tasks you can set it to low or medium. Claude thinks less (or skips it entirely), makes fewer tool calls, and gives more concise answers Lower effort = faster responses with fewer tokens!

Opus 4.6 lets you set the effort level Not every task needs high reasoning. For simpler tasks you can set it to low or medium. Claude thinks less (or skips it entirely), makes fewer tool calls, and gives more concise answers Lower effort = faster responses with fewer tokens!

Lydia Hallie ✨

34,173 views • 6 months ago

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 👇

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 views • 3 months ago

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.

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 views • 6 months ago

Marketers. I’m begging you. Stop prompting Claude 12+ times when it can be done in 1. Most marketers open Claude and start typing whatever comes to mind. Several rounds later, you’re editing mediocre output by hand. My team built a prompt auditing tool that reads your work, grades it, and gets you to 95% in minutes. It’s based on the RCTC framework, which answers the 4 questions Claude actually needs to be effective: Role - WHO is this for? Channel - WHERE is this going? Task - WHAT outcome is the output getting to? Constraints - WHAT bad output sounds like? Then automatically edits your work so you’re more effective in Claude, ChatGPT, or Gemini. Comment “GA” and I’ll send you the tool.

Marketers. I’m begging you. Stop prompting Claude 12+ times when it can be done in 1. Most marketers open Claude and start typing whatever comes to mind. Several rounds later, you’re editing mediocre output by hand. My team built a prompt auditing tool that reads your work, grades it, and gets you to 95% in minutes. It’s based on the RCTC framework, which answers the 4 questions Claude actually needs to be effective: Role - WHO is this for? Channel - WHERE is this going? Task - WHAT outcome is the output getting to? Constraints - WHAT bad output sounds like? Then automatically edits your work so you’re more effective in Claude, ChatGPT, or Gemini. Comment “GA” and I’ll send you the tool.

Jesse Pujji

10,773 views • 3 months ago

Claude Code + Nano Banana 2 is f*cking cracked 🤯 I built a skill inside Claude Code that writes JSON image prompts for Nano Banana 2, and the outputs look like they came from a professional photo shoot. One plain-text prompt. Claude rewrites it as structured JSON with lighting, camera, composition, style, and negative prompts. Then fires it off to Nano Banana 2. All inside Claude Code. Perfect for DTC brands and agencies who need high-volume ad creative without booking a shoot. If you're using Nano Banana 2 for product shots and lifestyle images but every generation feels like pulling a slot machine lever — random lighting, inconsistent style, plastic skin, misspelled labels ... This skill fixes the entire output: → You describe what you want in plain English → Claude rewrites it as a structured JSON prompt (lighting, camera angle, lens, depth of field, color grading — all of it) → Fires it to Nano Banana 2 via API → Saves the prompt + image in organized folders → You iterate on the style until it's dialed, then every output matches No more slot machine prompting. No more inconsistent brand imagery. No more burning credits on unusable generations. What you get: - Photo-realistic product shots and lifestyle images on demand - Full control over style, lighting, composition, and camera settings - Saved JSON prompts you can reuse across every campaign - A skill that gets smarter the more feedback you give it Built 100% in Claude Code with a custom skill + Python scripts. I put together a full playbook showing the exact skill, the JSON schema, and the workflow to set this up yourself. Want the full playbook? > Like this post > Comment "BANANA" And I'll send it over (must be following so I can DM)

NOVA

64,046 views • 5 months ago

Claude Code + Nano Banana 2 is f*cking cracked 🤯 I built a skill inside Claude Code that writes JSON image prompts for Nano Banana 2, and the outputs look like they came from a professional photo shoot. One plain-text prompt. Claude rewrites it as structured JSON with lighting, camera, composition, style, and negative prompts. Then fires it off to Nano Banana 2. All inside Claude Code. Perfect for DTC brands and agencies who need high-volume ad creative without booking a shoot. If you're using Nano Banana 2 for product shots and lifestyle images but every generation feels like pulling a slot machine lever — random lighting, inconsistent style, plastic skin, misspelled labels ... This skill fixes the entire output: → You describe what you want in plain English → Claude rewrites it as a structured JSON prompt (lighting, camera angle, lens, depth of field, color grading — all of it) → Fires it to Nano Banana 2 via API → Saves the prompt + image in organized folders → You iterate on the style until it's dialed, then every output matches No more slot machine prompting. No more inconsistent brand imagery. No more burning credits on unusable generations. What you get: - Photo-realistic product shots and lifestyle images on demand - Full control over style, lighting, composition, and camera settings - Saved JSON prompts you can reuse across every campaign - A skill that gets smarter the more feedback you give it Built 100% in Claude Code with a custom skill + Python scripts. I put together a full playbook showing the exact skill, the JSON schema, and the workflow to set this up yourself. Want the full playbook? > Like this post > Comment "BANANA" And I'll send it over (must be following so I can DM)

Mike Futia

212,175 views • 6 months ago

Holy shit...Claude Code just killed one of the most annoying terminal problems — flickering. 🤯 Anthropic quietly shipped NO_FLICKER mode and it changes how AI feels inside the terminal: • No more screen flashing • Smooth scrolling + stable viewport • Mouse support (yes… in terminal) • Constant memory/CPU as chats grow • Cleaner selections (no UI junk copied) This isn’t just a UI tweak. They basically virtualized the entire terminal viewport to control rendering themselves. Result? Terminal AI finally feels like a real app — fast, smooth, usable. ⚡ Turn it on: CLAUDE_CODE_NO_FLICKER=1 claude Small launch. Huge UX upgrade. Terminal-native AI is getting scary good.

Holy shit...Claude Code just killed one of the most annoying terminal problems — flickering. 🤯 Anthropic quietly shipped NO_FLICKER mode and it changes how AI feels inside the terminal: • No more screen flashing • Smooth scrolling + stable viewport • Mouse support (yes… in terminal) • Constant memory/CPU as chats grow • Cleaner selections (no UI junk copied) This isn’t just a UI tweak. They basically virtualized the entire terminal viewport to control rendering themselves. Result? Terminal AI finally feels like a real app — fast, smooth, usable. ⚡ Turn it on: CLAUDE_CODE_NO_FLICKER=1 claude Small launch. Huge UX upgrade. Terminal-native AI is getting scary good.

Suryansh Tiwari

32,145 views • 5 months ago

I kept getting distracting while vibe coding… so I made a notch for Claude Code It updates the status, pings you when you need to answer a question and notifies you when the task is done When it detects claude is working it also prevents my macbook from going to sleep I can walk away from my macbook. Or watching a youtube video. And I'll get an alert when it's done.

I kept getting distracting while vibe coding… so I made a notch for Claude Code It updates the status, pings you when you need to answer a question and notifies you when the task is done When it detects claude is working it also prevents my macbook from going to sleep I can walk away from my macbook. Or watching a youtube video. And I'll get an alert when it's done.

Adam Lyttle

523,642 views • 5 months ago

built a dropdown menu with directional detection using Claude today It uses a triangle-based safe zone to keep submenus open while the cursor is moving toward them, so multi-level navigation feels much smoother and satisfying. I know this pattern already exists, but building it myself with Claude as a designer felt different.

built a dropdown menu with directional detection using Claude today It uses a triangle-based safe zone to keep submenus open while the cursor is moving toward them, so multi-level navigation feels much smoother and satisfying. I know this pattern already exists, but building it myself with Claude as a designer felt different.

Masum

51,339 views • 4 months ago

Simplicity is at the heart of great software. This is one of the reasons why Claude Code has been sticky for me. As a builder, I love planning and brainstorming, and this is now a key focus of Claude Code. I use Shift + Tab a lot to cycle between brainstorming, planning, and execution. This functionality provides the appropriate interface for me to either be very involved or less involved as I please. This works particularly well when building out new and complex features or entire new projects. This saves a huge amount of time. It allows me to tune Claude Code to execute and build more effectively. It also builds a loop of trust, and I often (surprisingly) find Claude Code asking for clarifications when it's confused. Coding agents don't normally do that. I have shared before on the power of brainstorming with AI for longer times. Try it and you will not be disappointed. Vibe coding is fun, but pair it with intentional development cycles, and you watch how far you can take a project with coding agents today.

Simplicity is at the heart of great software. This is one of the reasons why Claude Code has been sticky for me. As a builder, I love planning and brainstorming, and this is now a key focus of Claude Code. I use Shift + Tab a lot to cycle between brainstorming, planning, and execution. This functionality provides the appropriate interface for me to either be very involved or less involved as I please. This works particularly well when building out new and complex features or entire new projects. This saves a huge amount of time. It allows me to tune Claude Code to execute and build more effectively. It also builds a loop of trust, and I often (surprisingly) find Claude Code asking for clarifications when it's confused. Coding agents don't normally do that. I have shared before on the power of brainstorming with AI for longer times. Try it and you will not be disappointed. Vibe coding is fun, but pair it with intentional development cycles, and you watch how far you can take a project with coding agents today.

elvis

81,765 views • 10 months ago

THIS GUY IS RUNNING CLAUDE CODE ON A NINTENDO 3DS imagine vibe coding a startup from a handheld console that came out in 2011 he built a native SSH terminal for it from scratch in C. GPU-rendered, custom VT100 parser with full truecolor. even added a Nerd Font bitmap atlas so it looks exactly like his desktop terminal the 3DS connects to his Mac over SSH and runs Claude Code straight from it you can now play pokemon while you vibe code all on the same system

THIS GUY IS RUNNING CLAUDE CODE ON A NINTENDO 3DS imagine vibe coding a startup from a handheld console that came out in 2011 he built a native SSH terminal for it from scratch in C. GPU-rendered, custom VT100 parser with full truecolor. even added a Nerd Font bitmap atlas so it looks exactly like his desktop terminal the 3DS connects to his Mac over SSH and runs Claude Code straight from it you can now play pokemon while you vibe code all on the same system

Om Patel

77,692 views • 4 months ago

I’ve been using 60% Apple-style corner smoothing all the time. But whenever I explain it to Codex or Claude Code, they often miss the point. So I made a skill that anyone can use with their AI agents: npx skills add gabrielobholz/corner-smoothing-skill Now I can simply say: “Create a rectangle with radius: 32 and smoothing: 60” and get the shape I actually mean.

I’ve been using 60% Apple-style corner smoothing all the time. But whenever I explain it to Codex or Claude Code, they often miss the point. So I made a skill that anyone can use with their AI agents: npx skills add gabrielobholz/corner-smoothing-skill Now I can simply say: “Create a rectangle with radius: 32 and smoothing: 60” and get the shape I actually mean.

Gabriel

95,841 views • 2 months ago

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 views • 5 months ago

Claude Code + Higgsfield MCP is f*cking cracked 🤯 I built an entire DTC ad campaign inside Claude Code using the new Higgsfield MCP. One product URL → hero static, animated hero shot, 2 UGC clips with a creator wearing the product. 5 assets. One Claude conversation. 3 Higgsfield models. All inside Claude Code. Perfect for DTC brands and agencies who need full campaign packages without booking a shoot or briefing a designer. If you're spending hours every week generating statics in one tool, briefing a motion designer for the hero clip, then chasing a UGC creator for the talking-head shots — this MCP eliminates the entire pipeline: → Drop a product URL into Claude Code → Claude pulls the brand brief — voice, hero SKUs, visual style, target customer → Generates the hero static with ChatGPT Images 2.0 → Animates it into a 5-second cinematic opener with Seedance 2.0 → Generates a UGC creator with GPT Image 2 → Drops her in the product and generates 2 native UGC video clips with Seedance 2.0 No tab-switching between tools. No copy-pasting prompts between platforms. No briefing 3 different vendors for one campaign. What you get: → A complete campaign package — static, animation, UGC — from one product URL → Brand-specific outputs that pull from a real brief, not generic AI slop → Claude making creative decisions between every step (which variation wins, which creator fits the persona, which clip needs a re-spin) → A repeatable pipeline you can run for any product in your catalog Built 100% in Claude Code with the Higgsfield MCP. I recorded a full walkthrough showing exactly how this works: the MCP setup, every prompt, every model, the full campaign output. Want the full video walkthrough? > Like this post > Comment "MCP" And I'll send it over (must be following so I can DM)

Mike Futia

29,759 views • 4 months ago

Most video tools can generate clips. Very few can maintain identity. That has been the real bottleneck in AI video creation. Kling O1 changes that. For the first time, creators can carry a character, style, and visual language across scenes without constant fixes. You can reference past clips, assets, or images and the output stays consistently on-model. No visual drift. No rework loops. No “this doesn’t look like the last shot” moments. It feels less like prompting a tool and more like working with a creative collaborator that remembers context. The impact is practical, not theoretical: → Faster production cycles → Lower iteration costs → Noticeably higher output quality This is what mature AI tooling looks like. Not louder features. Not bigger claims. Just reliability where it actually matters. Consistency is no longer the problem.

Most video tools can generate clips. Very few can maintain identity. That has been the real bottleneck in AI video creation. Kling O1 changes that. For the first time, creators can carry a character, style, and visual language across scenes without constant fixes. You can reference past clips, assets, or images and the output stays consistently on-model. No visual drift. No rework loops. No “this doesn’t look like the last shot” moments. It feels less like prompting a tool and more like working with a creative collaborator that remembers context. The impact is practical, not theoretical: → Faster production cycles → Lower iteration costs → Noticeably higher output quality This is what mature AI tooling looks like. Not louder features. Not bigger claims. Just reliability where it actually matters. Consistency is no longer the problem.

Darshal Jaitwar

141,038 views • 8 months ago

AI coding agents re-explore the same codebase every single session. Repowise indexes a repo once and gives Claude Code, Codex, or any MCP agent a real dependency graph, git history, and a bug-predictive code health score. No re-grepping the same files. No stale docs. No guessing which file is about to break. The loop is simple: measure every file > locate where the risk concentrates > generate the exact refactoring plan to fix it Indexing a repo takes under 30 seconds and updates automatically on every commit. Paired benchmarks show up to 96% fewer tokens spent loading context and 70% fewer agent tool calls, at the same answer quality.

AI coding agents re-explore the same codebase every single session. Repowise indexes a repo once and gives Claude Code, Codex, or any MCP agent a real dependency graph, git history, and a bug-predictive code health score. No re-grepping the same files. No stale docs. No guessing which file is about to break. The loop is simple: measure every file > locate where the risk concentrates > generate the exact refactoring plan to fix it Indexing a repo takes under 30 seconds and updates automatically on every commit. Paired benchmarks show up to 96% fewer tokens spent loading context and 70% fewer agent tool calls, at the same answer quality.

Simplifying AI

17,561 views • 26 days ago

HE DESCRIBED A SITE TO CLAUDE CODE AND WALKED AWAY FOR 8 MINUTES What came back looked like a studio spent weeks on it. The setup that made it work: > Two design skills installed - Claude stops using safe boring defaults. > Visual references instead of text descriptions. > One detailed prompt with the concept, Claude asks clarifying questions before building. First version already solid -> review pass, one batch of fixes, done. What used to take a designer and a developer and several weeks of handoffs now takes a single session and no coding experience. Full walkthrough in the article below ↓

HE DESCRIBED A SITE TO CLAUDE CODE AND WALKED AWAY FOR 8 MINUTES What came back looked like a studio spent weeks on it. The setup that made it work: > Two design skills installed - Claude stops using safe boring defaults. > Visual references instead of text descriptions. > One detailed prompt with the concept, Claude asks clarifying questions before building. First version already solid -> review pass, one batch of fixes, done. What used to take a designer and a developer and several weeks of handoffs now takes a single session and no coding experience. Full walkthrough in the article below ↓

slash1s

52,905 views • 2 months ago

Claude cannot watch a YouTube video, Instagram reel, Tiktok, or local file video. Same problem is with ChatGPT and Gemini. It reads the transcript and pretends it did. This FREE AI TOOL fixes this issue It extracts only the important frames, transcribes the audio, and hands Claude a clean folder it can genuinely read and understand. No uploading to a server. Runs entirely on your machine. Here is what makes it smarter than everything else doing this: → Detects scene changes instead of grabbing one frame per second like every other tool → Removes near-duplicate frames so Claude is not reading the same shot 40 times → Handles A-B-A cuts, if a shot already appeared, it does not send it again → A 10-minute static screencast collapses to 1 frame instead of 600 → A fast-cut reel catches every visual change instead of missing frames between samples → Transcribes audio with Whisper and auto-detects the language → Saves the full soundtrack so audio models can actually hear it too → Works with Claude, ChatGPT, and Gemini The result: fewer frames, cheaper context, better understanding. Claude actually sees the video instead of guessing from a transcript.

Claude cannot watch a YouTube video, Instagram reel, Tiktok, or local file video. Same problem is with ChatGPT and Gemini. It reads the transcript and pretends it did. This FREE AI TOOL fixes this issue It extracts only the important frames, transcribes the audio, and hands Claude a clean folder it can genuinely read and understand. No uploading to a server. Runs entirely on your machine. Here is what makes it smarter than everything else doing this: → Detects scene changes instead of grabbing one frame per second like every other tool → Removes near-duplicate frames so Claude is not reading the same shot 40 times → Handles A-B-A cuts, if a shot already appeared, it does not send it again → A 10-minute static screencast collapses to 1 frame instead of 600 → A fast-cut reel catches every visual change instead of missing frames between samples → Transcribes audio with Whisper and auto-detects the language → Saves the full soundtrack so audio models can actually hear it too → Works with Claude, ChatGPT, and Gemini The result: fewer frames, cheaper context, better understanding. Claude actually sees the video instead of guessing from a transcript.

Kanika

22,770 views • 1 month ago

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

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 views • 4 months ago