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

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

На главную

9 things that took my Claude Code from okay to unreal: 1. Workspace: a repo that explains itself 2. Memory: the files that tell it how you work 3. Brief: plan mode before it touches anything 4. Ticket: one clear task with a finish line 5. Eyes: it opens...

gregisenberg's profile picture

GREG ISENBERG

700,110 subscribers

79,777 просмотров • 16 дней назад •via X (Twitter)

Юмор
LIVE

Anya Rossi• Live Now

Private livecam show

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

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

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

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

You can just tell Claude Code to learn skills and it will. I asked Claude to create an app that uses tldraw and it one shotted it with sqlite db, and then I asked Claude Code to create a skill so that it could read and write on the canvas. 10 minutes later it could do it. Weirrrrdddd times.
0:25

You can just tell Claude Code to learn skills and it will. I asked Claude to create an app that uses tldraw and it one shotted it with sqlite db, and then I asked Claude Code to create a skill so that it could read and write on the canvas. 10 minutes later it could do it. Weirrrrdddd times.

Riley Brown

73,418 просмотров • 8 месяцев назад

Day 3 of 5 building with Claude Fable 5 before it goes paid. Today: an audit of everything you have already made. 1. Fable 5 reads back through all your past Claude chats 2. It flags what worked, what you dropped, and where value is going to waste 3. It ranks the top 10 fixes by effort against impact 4. Then it hands you a concrete plan for the top 3 5. Run that plan on a cheaper model and save Fable 5 for the thinking Comment FABLE for the full guide. Make sure you follow me so I can DM it to you. Day 4 tomorrow.
0:52

Day 3 of 5 building with Claude Fable 5 before it goes paid. Today: an audit of everything you have already made. 1. Fable 5 reads back through all your past Claude chats 2. It flags what worked, what you dropped, and where value is going to waste 3. It ranks the top 10 fixes by effort against impact 4. Then it hands you a concrete plan for the top 3 5. Run that plan on a cheaper model and save Fable 5 for the thinking Comment FABLE for the full guide. Make sure you follow me so I can DM it to you. Day 4 tomorrow.

Charlie Hills

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

This guy literally told Claude to run every day at 4am. Now it opens his website, writes a blog post, and optimizes it for SEO. Every single day. Zero involvement. Here's how Claude computer use actually works: It looks at your screen. Moves your mouse. Clicks buttons. Opens apps. Completes the full task on its own. No code. No workflow builder. No setup. You just tell it what you want done. And the 4am SEO trick? You schedule it once inside Claude Co-work. Claude runs it every night while you sleep. Your site gets fresh content. You wake up and check the results. That's not a chatbot. That's an AI employee.
11:12

This guy literally told Claude to run every day at 4am. Now it opens his website, writes a blog post, and optimizes it for SEO. Every single day. Zero involvement. Here's how Claude computer use actually works: It looks at your screen. Moves your mouse. Clicks buttons. Opens apps. Completes the full task on its own. No code. No workflow builder. No setup. You just tell it what you want done. And the 4am SEO trick? You schedule it once inside Claude Co-work. Claude runs it every night while you sleep. Your site gets fresh content. You wake up and check the results. That's not a chatbot. That's an AI employee.

Julian Goldie SEO

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

Boris Cherny runs Claude Code at Anthropic. His line should stop you mid-scroll: "I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops." The skill moved. From writing prompts to building the loop around them. A loop that works has three things. Drop one and it burns money in circles. 1. A finish line it can prove. Tests pass or they fail. "Looks done" is not a finish line. 2. A checker that did not write the code. A model grading itself always says yes. 3. Brakes set before you start. A step limit. A money ceiling. A stop condition. That is the whole game. The loop does the work. You design the cage it runs in. Full breakdown below.
0:37

Boris Cherny runs Claude Code at Anthropic. His line should stop you mid-scroll: "I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops." The skill moved. From writing prompts to building the loop around them. A loop that works has three things. Drop one and it burns money in circles. 1. A finish line it can prove. Tests pass or they fail. "Looks done" is not a finish line. 2. A checker that did not write the code. A model grading itself always says yes. 3. Brakes set before you start. A step limit. A money ceiling. A stop condition. That is the whole game. The loop does the work. You design the cage it runs in. Full breakdown below.

shmidt

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

One of my favorite ways to use Claude Code is to create a ticket Here is why I love it: Claude Code is very good at doing the work, but it must know when it's "done." A ticket gives Claude Code a clear signpost for when to stop Here's how to write it in 4 parts: 1) Give it a job: - "Add a wait list form to the landing page." 2) Give it a proper scope: - Ask for a name, an email, and a company. 3) Tell it the UX you want: - Show a simple success message after a person sends the form. 4) Tell the constraints it needs to follow: - Keep the design the same as the current brand identity. Then add an instruction: make the change small enough to review in the diff view, run the checks, open the app in the desktop preview, and tell me what still needs human review. The catch: a ticket that is not clear makes Claude guess. "Make the app better." "Add AI." "Build the whole thing." You get a diff too big to read, so you cannot tell if it is right. Keep the ticket small enough so that Claude knows exactly what to do
4:07

One of my favorite ways to use Claude Code is to create a ticket Here is why I love it: Claude Code is very good at doing the work, but it must know when it's "done." A ticket gives Claude Code a clear signpost for when to stop Here's how to write it in 4 parts: 1) Give it a job: - "Add a wait list form to the landing page." 2) Give it a proper scope: - Ask for a name, an email, and a company. 3) Tell it the UX you want: - Show a simple success message after a person sends the form. 4) Tell the constraints it needs to follow: - Keep the design the same as the current brand identity. Then add an instruction: make the change small enough to review in the diff view, run the checks, open the app in the desktop preview, and tell me what still needs human review. The catch: a ticket that is not clear makes Claude guess. "Make the app better." "Add AI." "Build the whole thing." You get a diff too big to read, so you cannot tell if it is right. Keep the ticket small enough so that Claude knows exactly what to do

The Startup Ideas Podcast (SIP) 🧃

10,471 просмотров • 16 дней назад

How to set up Claude Cowork so it actually works like an AI chief of staff (not just another chatbot): 1. Most people open Cowork, type a message, and get generic output. It's not a Claude problem. It's a setup problem. Cowork needs context before it can help you. Who you are. How you work. What you're building. Your team. Your priorities. Give it that, and every session feels like picking up a conversation with an executive assistant. 2. The setup has three layers: a) Global instructions (who you are, how you work, what Claude should never do). b) Connectors (Slack, Gmail, Google Calendar, Notion) c) And a folder structure on your computer that acts as Claude's long-term memory. That combination is what takes it from generic to personalized. 3. Skills are the real leverage. A skill is a markdown file that tells Claude exactly how to do one thing well. Write my newsletter. Coach me on a decision. Review a case study. Each skill lives in its own folder with context, examples, and a definition of what success looks like. 4. We built a CEO coach skill in the video below. Gave it business context, leadership style, company goals. Then tested it with a real decision: should we increase our newsletter from once to twice a week? It came back with trade-offs, second-order consequences, and risk assessment. 5. Then we built a multi-agent advisory board. Five subagents, each with a defined persona: a) the operator b) the skeptic c) the customer advocate d) the finance partner e) the legal/risk advisor. You feed it a decision. Each agent evaluates independently. The main agent synthesizes the feedback. It's like having a board meeting on demand. 6. Third skill: a thought leadership content pipeline. Topic scoring, idea capture, distribution cadence, tone calibration. All built from your actual expertise and audience. Designed so an executive can go from idea to published post without starting from scratch every time. 7. The workspace map is what ties it all together. It's a top-level file that shows Claude how to navigate your entire setup. Which folders exist, what skills live where, how to invoke them. Without it, Claude has to search for everything. With it, Claude goes straight to what it needs. 8. Everything you build is portable. The folder structure works in Cowork, Claude Code, and Codex. Push it to a private GitHub repo and you can access it from your phone through Claude Code, or use Claude Dispatch. 9. The pattern is repeatable. Pick a task you do often. Create a folder. Build a skill. Add examples of what success looks like, and what a bad output looks like. Test it. Workshop it. Move on to the next one. Each skill is like onboarding a new employee who never forgets and never needs to be re-trained. The people who invest in this setup now are the ones who will have a 10x advantage when these tools get even better. And they're getting better fast. I sat down with Alex Lieberman on Human In The Loop and we built all three of these live from scratch. Full breakdown in the video below.. I tried to explain this as clear as possible for my non-developer crowd. Send it to someone who should be using Cowork but isn't yet. Or bookmark it to level up when you're ready. Watch 👇🏼
51:23

How to set up Claude Cowork so it actually works like an AI chief of staff (not just another chatbot): 1. Most people open Cowork, type a message, and get generic output. It's not a Claude problem. It's a setup problem. Cowork needs context before it can help you. Who you are. How you work. What you're building. Your team. Your priorities. Give it that, and every session feels like picking up a conversation with an executive assistant. 2. The setup has three layers: a) Global instructions (who you are, how you work, what Claude should never do). b) Connectors (Slack, Gmail, Google Calendar, Notion) c) And a folder structure on your computer that acts as Claude's long-term memory. That combination is what takes it from generic to personalized. 3. Skills are the real leverage. A skill is a markdown file that tells Claude exactly how to do one thing well. Write my newsletter. Coach me on a decision. Review a case study. Each skill lives in its own folder with context, examples, and a definition of what success looks like. 4. We built a CEO coach skill in the video below. Gave it business context, leadership style, company goals. Then tested it with a real decision: should we increase our newsletter from once to twice a week? It came back with trade-offs, second-order consequences, and risk assessment. 5. Then we built a multi-agent advisory board. Five subagents, each with a defined persona: a) the operator b) the skeptic c) the customer advocate d) the finance partner e) the legal/risk advisor. You feed it a decision. Each agent evaluates independently. The main agent synthesizes the feedback. It's like having a board meeting on demand. 6. Third skill: a thought leadership content pipeline. Topic scoring, idea capture, distribution cadence, tone calibration. All built from your actual expertise and audience. Designed so an executive can go from idea to published post without starting from scratch every time. 7. The workspace map is what ties it all together. It's a top-level file that shows Claude how to navigate your entire setup. Which folders exist, what skills live where, how to invoke them. Without it, Claude has to search for everything. With it, Claude goes straight to what it needs. 8. Everything you build is portable. The folder structure works in Cowork, Claude Code, and Codex. Push it to a private GitHub repo and you can access it from your phone through Claude Code, or use Claude Dispatch. 9. The pattern is repeatable. Pick a task you do often. Create a folder. Build a skill. Add examples of what success looks like, and what a bad output looks like. Test it. Workshop it. Move on to the next one. Each skill is like onboarding a new employee who never forgets and never needs to be re-trained. The people who invest in this setup now are the ones who will have a 10x advantage when these tools get even better. And they're getting better fast. I sat down with Alex Lieberman on Human In The Loop and we built all three of these live from scratch. Full breakdown in the video below.. I tried to explain this as clear as possible for my non-developer crowd. Send it to someone who should be using Cowork but isn't yet. Or bookmark it to level up when you're ready. Watch 👇🏼

JJ Englert

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

Introducing Claude Code Templates 🚀 I originally built this to streamline how I set up new projects with Claude Code…just a small tool to make my own workflow smoother. No install, just run: npx claude-code-templates Right now, it configures Commands, Hooks, MCPs, and settings.json for JavaScript/TypeScript and Python projects. It made things so much easier for me that I decided to share it with the community. Open-source and open to ideas — feel free to contribute! Big thanks to the team at Anthropic and everyone behind Claude Code Community 🙌
0:50

Introducing Claude Code Templates 🚀 I originally built this to streamline how I set up new projects with Claude Code…just a small tool to make my own workflow smoother. No install, just run: npx claude-code-templates Right now, it configures Commands, Hooks, MCPs, and settings.json for JavaScript/TypeScript and Python projects. It made things so much easier for me that I decided to share it with the community. Open-source and open to ideas — feel free to contribute! Big thanks to the team at Anthropic and everyone behind Claude Code Community 🙌

Daniel San

28,410 просмотров • 1 год назад

Anthropic engineer: "You're not supposed to watch Claude Code work. You're supposed to wake up and review what it shipped" in 22 minutes she builds the full workflow from scratch, step by step a routine that ships work while you sleep most developers have never seen Claude Code run without them watching watch the session, then save the guide below
21:33

Anthropic engineer: "You're not supposed to watch Claude Code work. You're supposed to wake up and review what it shipped" in 22 minutes she builds the full workflow from scratch, step by step a routine that ships work while you sleep most developers have never seen Claude Code run without them watching watch the session, then save the guide below

Anatoli Kopadze

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

ANTHROPIC JUST QUIETLY SHIPPED A FEATURE THAT LETS CLAUDE SPAWN A WHOLE TEAM OF AGENTS THAT MESSAGE EACH OTHER AND REVIEW EACH OTHER'S WORK. It's a Claude Code feature called agent teams. The team lead spawns multiple agents that share a task list and message each other directly, not subagents reporting back, actual peers. In the demo a QA agent caught three bugs, sent the work back to the front-end and back-end devs, they fixed it, app shipped in one pass. How to run it: 1. Enable it. Needs Claude Code v2.1.32+. Add to settings.json: "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }. Or paste that to Claude and say "add this to my settings." Restart. 2. Prompt in plain English. Start with a goal (agents wake with zero context), then "create a team of 3 using Sonnet," describe each role, its deliverable, and who it messages when done. 3. The rules: each agent owns its own files, define exact outputs, name who talks to who, keep it to 3-5 agents. Use it for complex work with separate parts running in parallel. Skip it for simple or sequential tasks, teams cost 3-4x the tokens. Bookmark this.
16:29

ANTHROPIC JUST QUIETLY SHIPPED A FEATURE THAT LETS CLAUDE SPAWN A WHOLE TEAM OF AGENTS THAT MESSAGE EACH OTHER AND REVIEW EACH OTHER'S WORK. It's a Claude Code feature called agent teams. The team lead spawns multiple agents that share a task list and message each other directly, not subagents reporting back, actual peers. In the demo a QA agent caught three bugs, sent the work back to the front-end and back-end devs, they fixed it, app shipped in one pass. How to run it: 1. Enable it. Needs Claude Code v2.1.32+. Add to settings.json: "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }. Or paste that to Claude and say "add this to my settings." Restart. 2. Prompt in plain English. Start with a goal (agents wake with zero context), then "create a team of 3 using Sonnet," describe each role, its deliverable, and who it messages when done. 3. The rules: each agent owns its own files, define exact outputs, name who talks to who, keep it to 3-5 agents. Use it for complex work with separate parts running in parallel. Skip it for simple or sequential tasks, teams cost 3-4x the tokens. Bookmark this.

Yarchi

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

"I am a Claude Code maximalist. I try to live in it all day if I can." Carl Vellotti 🥞 has gone deeper on Claude Code than any PM I know. In my new episode, he showed me how to connect Claude Code to: → Google Workspace: Prep for meetings → Linear: Create tickets from PRDs → Slack: Share status updates → Reddit: Monitor subreddit discussions He does all of the above using skills and MCPs in his personal Claude Code OS. Some quotes from Carl: "Connecting Claude Code to the apps that you use at work makes it way more powerful." "Why would you need to go to all these websites if you can just get the info right here?" "I use this consult-the-council skill to get Claude, ChatGPT, and Grok to all review my work in one shot." 📌 Watch now: Thanks to our sponsors: Granola - The best AI meeting notes app I've ever used: Replit ⠕ - Create beautiful prototypes and full stack apps:
0:41

"I am a Claude Code maximalist. I try to live in it all day if I can." Carl Vellotti 🥞 has gone deeper on Claude Code than any PM I know. In my new episode, he showed me how to connect Claude Code to: → Google Workspace: Prep for meetings → Linear: Create tickets from PRDs → Slack: Share status updates → Reddit: Monitor subreddit discussions He does all of the above using skills and MCPs in his personal Claude Code OS. Some quotes from Carl: "Connecting Claude Code to the apps that you use at work makes it way more powerful." "Why would you need to go to all these websites if you can just get the info right here?" "I use this consult-the-council skill to get Claude, ChatGPT, and Grok to all review my work in one shot." 📌 Watch now: Thanks to our sponsors: Granola - The best AI meeting notes app I've ever used: Replit ⠕ - Create beautiful prototypes and full stack apps:

Peter Yang

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

How I have Claude automate anything I do on my computer just by showing it: I use the free Clips app and hit record to start recording. Then I just do the action - like navigating to Rippling and approving any unapproved time off - and I’ll often just talk out loud as I do it explaining any add’l details like I would when showing a human. The Clips app captures everything on your screen and everything you say, and transforms it into a format Claude can “see and hear”. You'll then get a link that you can easily share with Claude (or humans too). I’ll paste it to Claude and say something like, "automate this for me every day at 8:00 AM." The link has special metadata that agents like Claude can discover. It exposes APIs to see the full transcript with timestamps and grab screenshots of what was on your screen at any of those timestamps. Once it's created the routine, you can go to the Routines tab in Claude Code desktop app. This also works with the CLI, Claude Cowork, Codex etc. You’ll see your new routine there, and you can just hit Run Now to have it start running it. Video attached shows this step by step. The Clips apps is free and open source - I’ll link to it and the source code in the thread.
1:54

How I have Claude automate anything I do on my computer just by showing it: I use the free Clips app and hit record to start recording. Then I just do the action - like navigating to Rippling and approving any unapproved time off - and I’ll often just talk out loud as I do it explaining any add’l details like I would when showing a human. The Clips app captures everything on your screen and everything you say, and transforms it into a format Claude can “see and hear”. You'll then get a link that you can easily share with Claude (or humans too). I’ll paste it to Claude and say something like, "automate this for me every day at 8:00 AM." The link has special metadata that agents like Claude can discover. It exposes APIs to see the full transcript with timestamps and grab screenshots of what was on your screen at any of those timestamps. Once it's created the routine, you can go to the Routines tab in Claude Code desktop app. This also works with the CLI, Claude Cowork, Codex etc. You’ll see your new routine there, and you can just hit Run Now to have it start running it. Video attached shows this step by step. The Clips apps is free and open source - I’ll link to it and the source code in the thread.

Steve (Builder.io)

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

Here's what the Founder of Claude Code does before he starts ANY project: 1. Plans first, codes never, he goes back and forth with Claude on the plan until it's perfect. No code gets written yet 2. Creates a CLAUDE.md file (a simple doc that Claude reads every session so it knows your project, your rules, your style) 3. Gives Claude a way to verify its own work - For backend: write and run tests - For UI: take screenshots, check in browser Claude should never finish a task without proving it works 4. Sets up project-level permission rules in settings.json instead of skipping permissions entirely. Shared with the whole team 5. Five more preparation steps in VIDEO BELOW 6. Only then switches to auto-accept mode and lets Claude build The part most people miss: he doesn't treat Claude as a magic box that gets things right first try he treats it like a junior dev that needs clear instructions, feedback loops, and guardrails at scale he runs multiple sessions in parallel, uses Opus with thinking enabled because it makes fewer mistakes even though it's slower and relies on background agents that push code for later review his setup is surprisingly simple. no crazy custom tools. just slash commands, subagents, and a clean CLAUDE.md the difference isn't the tool. it's how you set it up before you start ❤️ P.S. for sure 99.5% of readers will scroll down this tweet, but I send it to 0.5% who loves to learn how to improve your workflow daily and control 99.5% in 2 years Hard skills literally mean nothing in our world The most important skills which you can have are: building architectures and orchestrations If you master it and use a creative approach, CONGRATS
9:54

Here's what the Founder of Claude Code does before he starts ANY project: 1. Plans first, codes never, he goes back and forth with Claude on the plan until it's perfect. No code gets written yet 2. Creates a CLAUDE.md file (a simple doc that Claude reads every session so it knows your project, your rules, your style) 3. Gives Claude a way to verify its own work - For backend: write and run tests - For UI: take screenshots, check in browser Claude should never finish a task without proving it works 4. Sets up project-level permission rules in settings.json instead of skipping permissions entirely. Shared with the whole team 5. Five more preparation steps in VIDEO BELOW 6. Only then switches to auto-accept mode and lets Claude build The part most people miss: he doesn't treat Claude as a magic box that gets things right first try he treats it like a junior dev that needs clear instructions, feedback loops, and guardrails at scale he runs multiple sessions in parallel, uses Opus with thinking enabled because it makes fewer mistakes even though it's slower and relies on background agents that push code for later review his setup is surprisingly simple. no crazy custom tools. just slash commands, subagents, and a clean CLAUDE.md the difference isn't the tool. it's how you set it up before you start ❤️ P.S. for sure 99.5% of readers will scroll down this tweet, but I send it to 0.5% who loves to learn how to improve your workflow daily and control 99.5% in 2 years Hard skills literally mean nothing in our world The most important skills which you can have are: building architectures and orchestrations If you master it and use a creative approach, CONGRATS

Ronin

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

Claude Code + computer use is f*cking cracked 🤯 Build a landing page → Claude opens Chrome, looks at it, spots every issue, and fixes it — without you describing a single thing. All inside Claude Code. Perfect for DTC brands and agencies who are still vibe-coding landing pages and advertorials in Claude Code, then manually opening them in Chrome, spotting 15 things wrong, and describing every visual issue back to Claude one at a time. If you're building pages in Claude Code and your workflow looks like this — build the page, open it in Chrome, spot broken spacing, go back to Claude, type "the CTA button is too low and the hero image is cut off," wait for the fix, open Chrome again, find 3 new issues, describe those too ... Claude Code + computer use eliminates the entire loop: → Claude writes the full landing page or advertorial → Opens Chrome and navigates to it → Spots layout issues, broken spacing, off-brand colors, missing elements → Fixes everything and re-checks until the page looks right → Tests your Shopify product pages by clicking through like a real customer → Walks through your checkout flow and flags friction before customers hit it → You only see the finished, visually verified result No describing what you see on screen. No "the CTA button needs more contrast" back-and-forth. No being the eyeballs for an AI that can't see. What you get: → Landing pages and advertorials Claude builds AND visually QAs before you ever look at them → Product pages Claude clicks through — testing layout, images, and CTAs like a real user → HTML dashboards Claude opens and verifies the charts actually render → Checkout flows Claude walks through step by step to catch friction → All of it happening in one session — build, test, fix, done One prompt. Claude builds it, checks it, and fixes it. You just review the finished page. I put together a full playbook with the exact setup, the prompts, and 5 DTC workflows that use Claude Code + computer use. Want it for free? > Like this post > Comment "CLAUDE" And I'll send it over (must be following so I can DM)
0:20

Claude Code + computer use is f*cking cracked 🤯 Build a landing page → Claude opens Chrome, looks at it, spots every issue, and fixes it — without you describing a single thing. All inside Claude Code. Perfect for DTC brands and agencies who are still vibe-coding landing pages and advertorials in Claude Code, then manually opening them in Chrome, spotting 15 things wrong, and describing every visual issue back to Claude one at a time. If you're building pages in Claude Code and your workflow looks like this — build the page, open it in Chrome, spot broken spacing, go back to Claude, type "the CTA button is too low and the hero image is cut off," wait for the fix, open Chrome again, find 3 new issues, describe those too ... Claude Code + computer use eliminates the entire loop: → Claude writes the full landing page or advertorial → Opens Chrome and navigates to it → Spots layout issues, broken spacing, off-brand colors, missing elements → Fixes everything and re-checks until the page looks right → Tests your Shopify product pages by clicking through like a real customer → Walks through your checkout flow and flags friction before customers hit it → You only see the finished, visually verified result No describing what you see on screen. No "the CTA button needs more contrast" back-and-forth. No being the eyeballs for an AI that can't see. What you get: → Landing pages and advertorials Claude builds AND visually QAs before you ever look at them → Product pages Claude clicks through — testing layout, images, and CTAs like a real user → HTML dashboards Claude opens and verifies the charts actually render → Checkout flows Claude walks through step by step to catch friction → All of it happening in one session — build, test, fix, done One prompt. Claude builds it, checks it, and fixes it. You just review the finished page. I put together a full playbook with the exact setup, the prompts, and 5 DTC workflows that use Claude Code + computer use. Want it for free? > Like this post > Comment "CLAUDE" And I'll send it over (must be following so I can DM)

Mike Futia

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

Anthropic fucking killed it (again). biggest ai product launch of the year so far. claude can now control your entire computer autonomously. anything you can do on a computer - claude can. your very own digital employee. - any app, browser, file, spreadsheet, tool claude can intelligently access and operate. - claude controls your entire screen (like a human), no connectors. this is a huge step-up in intelligence. - best part: you can text claude to do things from your phone and it'll do work on your computer! - in the last week anthropic has shipped 9 features that have built up to this: a fully automated digital human. unreal
1:13

Anthropic fucking killed it (again). biggest ai product launch of the year so far. claude can now control your entire computer autonomously. anything you can do on a computer - claude can. your very own digital employee. - any app, browser, file, spreadsheet, tool claude can intelligently access and operate. - claude controls your entire screen (like a human), no connectors. this is a huge step-up in intelligence. - best part: you can text claude to do things from your phone and it'll do work on your computer! - in the last week anthropic has shipped 9 features that have built up to this: a fully automated digital human. unreal

Ejaaz

2,036,724 просмотров • 5 месяцев назад

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: 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. Claude reads it, links it, 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: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.
1:48

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: 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. Claude reads it, links it, 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: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.

CyrilXBT

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

karpathy just broke the internet with something called auto research it’s basically an ai research agent that runs experiments for you 24/7 you give it a goal like “make this model better” “find a higher converting landing page” “lower customer acquisition cost” then it runs a loop: 1) plan an experiment 2) edit the code or config 3) run a short test on a gpu 4) read the metrics 5) keep the winner 6) try again over and over while you sleep by the morning you wake up to the best version actual tested improvements think of it like a robot research intern that runs hundreds of experiments and only keeps the winners this is link to his repo for your to mess around with it in the latest episode of The Startup Ideas Podcast (SIP) 🧃 i break down: • what auto research actually is • how it works step by step • 10 business ideas you can build with it • how to install it and start using it this one is saucy because tools like this change how startups get built watch
24:21

karpathy just broke the internet with something called auto research it’s basically an ai research agent that runs experiments for you 24/7 you give it a goal like “make this model better” “find a higher converting landing page” “lower customer acquisition cost” then it runs a loop: 1) plan an experiment 2) edit the code or config 3) run a short test on a gpu 4) read the metrics 5) keep the winner 6) try again over and over while you sleep by the morning you wake up to the best version actual tested improvements think of it like a robot research intern that runs hundreds of experiments and only keeps the winners this is link to his repo for your to mess around with it in the latest episode of The Startup Ideas Podcast (SIP) 🧃 i break down: • what auto research actually is • how it works step by step • 10 business ideas you can build with it • how to install it and start using it this one is saucy because tools like this change how startups get built watch

GREG ISENBERG

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

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.
1:15

New on Claude Code Desktop We’re shipping new features for Claude Code on desktop that let you preview running apps, auto-review code, and auto-fix and merge PRs to help close the development loop. - Server previews: Claude starts dev servers and previews your running app in the desktop interface. It reads console logs, catches errors, and keeps iterating on its own. - Local code review: Claude examines your local diffs and leaves inline comments before you push — an immediate second set of eyes on every change. - PR monitoring: Claude tracks CI status after you open a PR. With auto-fix, it attempts to resolve failures automatically. With auto-merge, PRs land as soon as checks pass. You can move on to your next task while Claude handles the last one. - Session mobility: Move sessions from CLI to desktop, and from desktop to the cloud. Start work at your desk, pick it up from the web or your phone.

Ado

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

GPT 5.6 SOL IS HERE! How to run your personal + business life with GPT 5.6 Sol + Codex (full 49 min masterclass) We tested it for 30 days and the video it's the CLEAREST look at the FUTURE of work: Here's what's possible once you set it up: 1. Your inbox becomes cards every morning, each with a summary and a reply drafted in your own voice. Y 2. Your Slack, meeting notes, and company updates can turn into one daily feed with a clear next action. It learns what you care about over time and rewrites its own prompts to get sharper. 3. You can give your agent its own email address, so your other tools and even your team's Slack bot email it directly and it just handles things. 4. You can have it watch you do a task once and turn it into a skill it repeats forever. 5. You can set a long goal and walk away. You can have it run for 20 hours straight, and fine-tune your own models, something that was out of reach for non-engineers 12 months ago. How to start: Open Codex, give it access to your computer, and ask it to suggest things it could do for you based on how you already work. Full episode on The Startup Ideas Podcast (SIP) 🧃 (thanks Dan Shipper 📧 for sharing your entire workflow and review of GPT 5.6) Start with one boring task, get it working, and build from there. You'll learn exactly how to make something similar. GPT 5.6 Sol is impressive. Sol (according to openAI benchmarks) is the best coding model out right now. It set a new state of the art on Terminal-Bench 2.1 at 88.8%, and its "ultra mode" hits 91.9%, beating Claude Opus 4.8, Fable 5, and even Mythos 5 this masterclass is 100% free, like always. For more The Startup Ideas Podcast (SIP) 🧃 Watch
49:16

GPT 5.6 SOL IS HERE! How to run your personal + business life with GPT 5.6 Sol + Codex (full 49 min masterclass) We tested it for 30 days and the video it's the CLEAREST look at the FUTURE of work: Here's what's possible once you set it up: 1. Your inbox becomes cards every morning, each with a summary and a reply drafted in your own voice. Y 2. Your Slack, meeting notes, and company updates can turn into one daily feed with a clear next action. It learns what you care about over time and rewrites its own prompts to get sharper. 3. You can give your agent its own email address, so your other tools and even your team's Slack bot email it directly and it just handles things. 4. You can have it watch you do a task once and turn it into a skill it repeats forever. 5. You can set a long goal and walk away. You can have it run for 20 hours straight, and fine-tune your own models, something that was out of reach for non-engineers 12 months ago. How to start: Open Codex, give it access to your computer, and ask it to suggest things it could do for you based on how you already work. Full episode on The Startup Ideas Podcast (SIP) 🧃 (thanks Dan Shipper 📧 for sharing your entire workflow and review of GPT 5.6) Start with one boring task, get it working, and build from there. You'll learn exactly how to make something similar. GPT 5.6 Sol is impressive. Sol (according to openAI benchmarks) is the best coding model out right now. It set a new state of the art on Terminal-Bench 2.1 at 88.8%, and its "ultra mode" hits 91.9%, beating Claude Opus 4.8, Fable 5, and even Mythos 5 this masterclass is 100% free, like always. For more The Startup Ideas Podcast (SIP) 🧃 Watch

GREG ISENBERG

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

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this
13:23

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

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

Most people use Claude Code like a chatbot. That is the mistake. The real power is not in better prompts. It is in controlling the session. /init gives the project memory. /memory keeps the rules alive. /clear removes old context. /compact saves the important parts. /context shows where the tokens go. /rewind fixes bad turns. /plan stops blind edits. /model matches the brain to the task. Claude Code gets 10x better when you stop letting the conversation run itself. Memory. Context. Boundaries. Rollback. Planning. That is the system. Stop asking Claude Code to “just do it”. Teach it what to remember, what to forget, and when to stop. Bookmark this before your next session turns into 40 messages of context debt.
0:33

Most people use Claude Code like a chatbot. That is the mistake. The real power is not in better prompts. It is in controlling the session. /init gives the project memory. /memory keeps the rules alive. /clear removes old context. /compact saves the important parts. /context shows where the tokens go. /rewind fixes bad turns. /plan stops blind edits. /model matches the brain to the task. Claude Code gets 10x better when you stop letting the conversation run itself. Memory. Context. Boundaries. Rollback. Planning. That is the system. Stop asking Claude Code to “just do it”. Teach it what to remember, what to forget, and when to stop. Bookmark this before your next session turns into 40 messages of context debt.

Fluixo

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