Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Sure, everyone loves Claude Code but if you ask non-coders: they're all obsessed with Cowork. JJ Englert at tenex is one of them, and he's giving us the power user's guide to getting started with Claude Cowork. In this ep, JJ walks me through: - How to set up...

50,362 görüntüleme • 3 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

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

566,973 görüntüleme • 3 ay önce

I got curious how compaction works as a PM, so I did some brain surgery on Claude Code: (Anthropic's been doing really interesting work on context editing - they showed Claude Opus playing Settlers of Catan for 75+ minutes in a single thread by constantly editing the context instead of starting fresh. When I saw that Claude Code has a compaction command with optional custom instructions, I wanted to understand what's actually happening.) Abhishek Katiyar and Aman Khan gave me the key tip: Claude Code stores all your conversation history as text files on your computer. Open a new directory and give Claude Code a task. Here's how to watch compaction happening: 1. Go to your user's root directory 2. Press Command+Shift+Period (Mac) to show hidden folders 3. Navigate to ~/.claude/projects/ 4. Find your project folder and use Cursor/VSCode to open it (there's a reason) 5. Install the JSONL Gazelle plugin (open source, thank you Gabor Cselle!) 6. Open the most recent JSONL file - each row is a message in your conversation 7. Run the compact command in Claude Code with custom instructions 8. Watch what happens in the file What I learned: When you compact, Claude Code doesn't just summarize and delete everything. It creates a "compact boundary" in the conversation file, writes a summary of what happened before, but keeps the full original conversation (!!!!) The new thread can still retrieve any details from before compaction if needed. That is so damn cool. Why this matters: What you're getting in Claude Code is similar to what Anthropic ships in their developer SDK - so inspecting your daily tools is how you build real product intuition. The best way to understand AI systems is to open them up and look inside. Everything is text files.

Tal Raviv

57,910 görüntüleme • 6 ay önce

Noah Brier (Noah Brier) uses Claude Code as his second brain—it’s the coolest notetaking setup I’ve ever seen. He has Claude running on a server in his basement hooked up to a VPN. It stores, reads, and writes to thousands of notes in his Obsidian (Obsidian) vault. He does it all from his phone. I had him on the show to tell us exactly how he’s pulling this off. We get into: - The nuts and bolts of the Claude Code-Obsidian setup: Noah set up Claude Code on top of his Obsidian root directory, and he walked me through how he uses it to prep for an upcoming speech—creating a project folder, pulling in relevant research from his notes, saving transcripts from chats with other LLMs, and generating daily progress updates. - The “thinking partner” that lives inside Noah’s second brain: Noah points out that in the hype around AI’s ability to write, the fact that it can read is overlooked. That’s why he has an agent inside Claude Code with strict guardrails to stay in “thinking mode.” It logs his questions, tracks insights, and catches him up on research if he returns to a project after a few days away. - How Noah does deep work on his phone: Noah rigged a home server in his basement, put his Obsidian vault in it—and then runs Claude Code on top. Noah says that being able to think, write, research, and ship code from his phone has fundamentally changed the way he works. This episode of Every 📧’s AI & I is a must-watch for anyone curious about who wants to learn how to use Claude Code to build a true second brain. Watch below! Timestamps: Introduction: 00:01:19 How you can do deep work on your phone: 00:04:28 Why Noah thinks Grok has the best voice AI: 00:06:14 The nuts and bolts of Noah’s Claude Code-Obsidian setup: 00:11:39 Using an agent in Claude Code as a “thinking partner”: 00:23:59 Noah’s Thomas’ English Muffin theory of AI: 00:35:07 The white space still left to explore in AI: 00:44:04 How Noah is preparing his kids for AI: 00:50:41 How he brought his Claude Code setup to mobile: 01:01:54

Dan Shipper 📧

30,792 görüntüleme • 10 ay önce