正在加载视频...

视频加载失败

返回首页

A PHD JUST EXPLAINED HOW TO BECOME IMMORTAL WITH FABLE + GOD-MODE SECOND BRAIN ASSISTANT. This was science fiction in February, BUT now it's a weekend setup: > step one: build the second brain: every note, every decision, every opinion, the raw material of how you actually think >...

0xMiraqle's profile picture

Miraqle

2,471 subscribers

32,328 次观看 • 1 个月前 •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

One of the smartest things you can do with Fable 5 right now: Re-create your AI second brain to log all your business ideas, personal context, and important data. The first time I built an AI second brain was with Opus, but I recently re-created it with Fable 5, and it blew my mind. Here's exactly how to get started: Step 1. Set up your Obsidian vault Download Obsidian from Obsidian dot md if you haven't already. Then, go ahead and create a clean vault with your most important folders. For example: /ideas → business ideas, content angles, random thoughts /context → who you are, your business, your goals, your stack /data → important numbers, portfolios, metrics /log → daily entries, decisions, lessons learned This is your database. Everything Fable reads lives here. Step 2. Connect Fable 5 to your vault I like this Claude Code prompt: "/goal connect to my Obsidian vault at [path] and act as my second brain orchestrator. Read everything in /context before every session. Log anything new I tell you to /log with today's date." Fable now reads your vault before it answers anything - it knows your business, your goals, your history. Step 3. Build the self-update habit Every time you have an idea, a decision, or a lesson, tell Fable: "Log this to my second brain: [thought]" Step 4. Start querying it You can start sending prompts like: → "What are the most common themes across my last 30 ideas?" → "Based on my context, what should I be prioritising this week?" → "What decisions have I made about my content strategy so far?" Opus was good at this, but Fable is on another level. I feel the depth of reasoning it brings to your data is genuinely unlike anything I've used before. Some might argue it's a bit of overkill to use Fable for a simple second-brain setup, but if you have the means, it's 100% worth it. Build this once, and it'll compound forever.
0:49

One of the smartest things you can do with Fable 5 right now: Re-create your AI second brain to log all your business ideas, personal context, and important data. The first time I built an AI second brain was with Opus, but I recently re-created it with Fable 5, and it blew my mind. Here's exactly how to get started: Step 1. Set up your Obsidian vault Download Obsidian from Obsidian dot md if you haven't already. Then, go ahead and create a clean vault with your most important folders. For example: /ideas → business ideas, content angles, random thoughts /context → who you are, your business, your goals, your stack /data → important numbers, portfolios, metrics /log → daily entries, decisions, lessons learned This is your database. Everything Fable reads lives here. Step 2. Connect Fable 5 to your vault I like this Claude Code prompt: "/goal connect to my Obsidian vault at [path] and act as my second brain orchestrator. Read everything in /context before every session. Log anything new I tell you to /log with today's date." Fable now reads your vault before it answers anything - it knows your business, your goals, your history. Step 3. Build the self-update habit Every time you have an idea, a decision, or a lesson, tell Fable: "Log this to my second brain: [thought]" Step 4. Start querying it You can start sending prompts like: → "What are the most common themes across my last 30 ideas?" → "Based on my context, what should I be prioritising this week?" → "What decisions have I made about my content strategy so far?" Opus was good at this, but Fable is on another level. I feel the depth of reasoning it brings to your data is genuinely unlike anything I've used before. Some might argue it's a bit of overkill to use Fable for a simple second-brain setup, but if you have the means, it's 100% worth it. Build this once, and it'll compound forever.

Miles Deutscher

92,183 次观看 • 21 天前

THIS GUY BUILT A GOD-MODE SECOND BRAIN IN 3 STEPS THAT GETS SMARTER EVERY SINGLE DAY AND 10X HIS RESEARCH! Everyone hoards notes they never reopen, but he turned the dead pile into a brain that actually reads itself back, in three steps: > download Obsidian, make a vault, and point Claude Code at the folder > create two folders inside, raw-sources for everything you dump in and wiki where Claude writes the organized version, then drop in Andrej Karpathy's prompt > throw in every article, book note, meeting transcript and piece of research you ever saved and forgot Then you stop searching and start asking the wiki, "what are the gaps in my knowledge", "write me a briefing on this topic", and Claude pulls from your whole vault and answers with citations. Everyone copies the folders, but the part that actually matters is what happens next, every answer gets written back into the wiki and a weekly health check hunts for contradictions and outdated info, so it is not storage you query, it is a brain that compounds every day you use it. The full step by step guide with the Karpathy prompt and the .md files is in the article below.👇 P.S. you can send this article straight to your Claude to get the full context
0:56

THIS GUY BUILT A GOD-MODE SECOND BRAIN IN 3 STEPS THAT GETS SMARTER EVERY SINGLE DAY AND 10X HIS RESEARCH! Everyone hoards notes they never reopen, but he turned the dead pile into a brain that actually reads itself back, in three steps: > download Obsidian, make a vault, and point Claude Code at the folder > create two folders inside, raw-sources for everything you dump in and wiki where Claude writes the organized version, then drop in Andrej Karpathy's prompt > throw in every article, book note, meeting transcript and piece of research you ever saved and forgot Then you stop searching and start asking the wiki, "what are the gaps in my knowledge", "write me a briefing on this topic", and Claude pulls from your whole vault and answers with citations. Everyone copies the folders, but the part that actually matters is what happens next, every answer gets written back into the wiki and a weekly health check hunts for contradictions and outdated info, so it is not storage you query, it is a brain that compounds every day you use it. The full step by step guide with the Karpathy prompt and the .md files is in the article below.👇 P.S. you can send this article straight to your Claude to get the full context

Miraqle

15,128 次观看 • 1 个月前

Anthropic Claude Code engineer: "The moment you're reviewing every line Claude writes, you became its tester. You weren't hired for that." this 36 min talk is the clearest breakdown of how to get yourself out of the loop entirely the shift is simple: you stop prompting and start building agents that work instead of you agents that run, check themselves, and keep going while your laptop is closed watch it, then build your own with the step-by-step guide below
36:48

Anthropic Claude Code engineer: "The moment you're reviewing every line Claude writes, you became its tester. You weren't hired for that." this 36 min talk is the clearest breakdown of how to get yourself out of the loop entirely the shift is simple: you stop prompting and start building agents that work instead of you agents that run, check themselves, and keep going while your laptop is closed watch it, then build your own with the step-by-step guide below

Anatoli Kopadze

27,852 次观看 • 1 个月前

YOU CAN BUILD AN AI SECOND BRAIN IN 15 MINUTES. No coding experience. No $1000 course. Here is the entire setup. Step 1: Download Claude Desktop. Step 2: Download Obsidian. Step 3: Create a new vault and start dropping .MD files into it. Step 4: Tell Claude Code to connect to your vault using Karpathy's prompt: That is it. Your entire knowledge base becomes searchable, connectable, and queryable by the most powerful AI model on earth. Every note you have ever written. Every idea you have ever captured. Every resource you have ever saved. Claude reads all of it, finds connections you missed, and surfaces insights from your own thinking that you FORGOT you had. Most people use Claude as a search engine. The people building second brains use it as an INTELLIGENCE LAYER on top of everything they know. That gap is the gap between asking Google a question and having a research partner who has read everything you have ever written. Bookmark this. Build it tonight. Follow CyrilXBT
1:19

YOU CAN BUILD AN AI SECOND BRAIN IN 15 MINUTES. No coding experience. No $1000 course. Here is the entire setup. Step 1: Download Claude Desktop. Step 2: Download Obsidian. Step 3: Create a new vault and start dropping .MD files into it. Step 4: Tell Claude Code to connect to your vault using Karpathy's prompt: That is it. Your entire knowledge base becomes searchable, connectable, and queryable by the most powerful AI model on earth. Every note you have ever written. Every idea you have ever captured. Every resource you have ever saved. Claude reads all of it, finds connections you missed, and surfaces insights from your own thinking that you FORGOT you had. Most people use Claude as a search engine. The people building second brains use it as an INTELLIGENCE LAYER on top of everything they know. That gap is the gap between asking Google a question and having a research partner who has read everything you have ever written. Bookmark this. Build it tonight. Follow CyrilXBT

CyrilXBT

258,722 次观看 • 21 天前

You can build an AI second brain in 15 minutes. No coding experience needed. no $1000 course [Here is how you can do it in 5 mins:] Step 1: Download Claude Desktop. Step 2: Download Obsidian Desktop. Step 3: Create a new vault and start dropping .MD files into it. Step 4: Tell Claude Code to connect directly to your vault using Andrej Karpathy's prompt: That is it. Your entire knowledge base becomes searchable, connectable, and queryable by the most powerful AI model on earth. Every note you have ever written. Every idea you have ever captured. Every resource you have ever saved. Claude can now read all of it, find connections you missed, and surface insights from your own thinking that you forgot you had. Most people are using Claude as a search engine. The people building second brains with it are using it as an intelligence layer on top of everything they know. The gap between those two use cases is the gap between asking Google a question and having a research partner who has read everything you have ever written. Bookmark this. Build it tonight.
1:18

You can build an AI second brain in 15 minutes. No coding experience needed. no $1000 course [Here is how you can do it in 5 mins:] Step 1: Download Claude Desktop. Step 2: Download Obsidian Desktop. Step 3: Create a new vault and start dropping .MD files into it. Step 4: Tell Claude Code to connect directly to your vault using Andrej Karpathy's prompt: That is it. Your entire knowledge base becomes searchable, connectable, and queryable by the most powerful AI model on earth. Every note you have ever written. Every idea you have ever captured. Every resource you have ever saved. Claude can now read all of it, find connections you missed, and surface insights from your own thinking that you forgot you had. Most people are using Claude as a search engine. The people building second brains with it are using it as an intelligence layer on top of everything they know. The gap between those two use cases is the gap between asking Google a question and having a research partner who has read everything you have ever written. Bookmark this. Build it tonight.

Avid

469,078 次观看 • 1 个月前

You can build an AI second brain in 15 minutes. No coding experience needed. no $1000 course [Here is how you can do it in 5 mins:] Step 1: Download Claude Desktop. Step 2: Download Obsidian Desktop. Step 3: Create a new vault and start dropping .MD files into it. Step 4: Tell Claude Code to connect directly to your vault using Andrej Karpathy's prompt: That is it. Your entire knowledge base becomes searchable, connectable, and queryable by the most powerful AI model on earth. Every note you have ever written. Every idea you have ever captured. Every resource you have ever saved. Claude can now read all of it, find connections you missed, and surface insights from your own thinking that you forgot you had. Most people are using Claude as a search engine. The people building second brains with it are using it as an intelligence layer on top of everything they know. The gap between those two use cases is the gap between asking Google a question and having a research partner who has read everything you have ever written. Bookmark this. Build it tonight.
22:22

You can build an AI second brain in 15 minutes. No coding experience needed. no $1000 course [Here is how you can do it in 5 mins:] Step 1: Download Claude Desktop. Step 2: Download Obsidian Desktop. Step 3: Create a new vault and start dropping .MD files into it. Step 4: Tell Claude Code to connect directly to your vault using Andrej Karpathy's prompt: That is it. Your entire knowledge base becomes searchable, connectable, and queryable by the most powerful AI model on earth. Every note you have ever written. Every idea you have ever captured. Every resource you have ever saved. Claude can now read all of it, find connections you missed, and surface insights from your own thinking that you forgot you had. Most people are using Claude as a search engine. The people building second brains with it are using it as an intelligence layer on top of everything they know. The gap between those two use cases is the gap between asking Google a question and having a research partner who has read everything you have ever written. Bookmark this. Build it tonight.

Avid

35,520 次观看 • 1 个月前

The most valuable AI system you're not running yet: an AI second brain. The concept goes back to Karpathy's knowledge wiki earlier this year, and it's still one of the highest-leverage workflows in AI. Connect your Hermes agent, and it becomes 10x more powerful. Here's how to build it (from scratch): Step 1. Download Obsidian Head to obsidian.md and download the desktop app. Once downloaded, go ahead and create a new Obsidian vault. Vaults are just where notes/text are stored locally. Start dumping everything in here: - Personal goals - Meetings - AI context/preferences The more you put in, the more powerful your second-brain becomes. Step 2. Connect Hermes to your Obsidian vault If you don't have Hermes yet, download the desktop app here: [ Then, paste this prompt: "I want you to connect to my new Obsidian vault and act as my second-brain personal assistant - do everything necessary to set up that connection now." This gives Hermes direct access to everything inside your notes vault. Step 3. Let it self-evolve Every time you add a new note, Hermes will automatically ingest it. Prompt Hermes: "Every day, scan my second brain database. Every time I add a new note, use it to create reusable skills and workflows." Pro tip: Once Obsidian is connected to your agent, you can just prompt it directly to add notes/context/data. This works really well if you're prompting Hermes on the go from Telegram/mobile. Save this and build your second brain system now.
0:24

The most valuable AI system you're not running yet: an AI second brain. The concept goes back to Karpathy's knowledge wiki earlier this year, and it's still one of the highest-leverage workflows in AI. Connect your Hermes agent, and it becomes 10x more powerful. Here's how to build it (from scratch): Step 1. Download Obsidian Head to obsidian.md and download the desktop app. Once downloaded, go ahead and create a new Obsidian vault. Vaults are just where notes/text are stored locally. Start dumping everything in here: - Personal goals - Meetings - AI context/preferences The more you put in, the more powerful your second-brain becomes. Step 2. Connect Hermes to your Obsidian vault If you don't have Hermes yet, download the desktop app here: [ Then, paste this prompt: "I want you to connect to my new Obsidian vault and act as my second-brain personal assistant - do everything necessary to set up that connection now." This gives Hermes direct access to everything inside your notes vault. Step 3. Let it self-evolve Every time you add a new note, Hermes will automatically ingest it. Prompt Hermes: "Every day, scan my second brain database. Every time I add a new note, use it to create reusable skills and workflows." Pro tip: Once Obsidian is connected to your agent, you can just prompt it directly to add notes/context/data. This works really well if you're prompting Hermes on the go from Telegram/mobile. Save this and build your second brain system now.

Miles Deutscher

28,703 次观看 • 6 天前

Most people trying to build a vertical AI business start by building the agent. That's the mistake. Here's the 5-step order that actually works: Step 1) Find a boring pain point - Pick a workflow you already know from your job. - That's your unfair advantage. Step 2) Map the workflow - Literally draw it out. - Every step, every handoff. Step 3) Do the job as a service - Manually. - For real clients. - Before any code. Step 4) Document the edge cases - This is where the real IP lives. - You only find them by doing the work. Step 5) Add vertical agents to replace each step - Now you have proprietary data and a workflow you own. Skip steps 1–4 and you're just building a demo.
4:43

Most people trying to build a vertical AI business start by building the agent. That's the mistake. Here's the 5-step order that actually works: Step 1) Find a boring pain point - Pick a workflow you already know from your job. - That's your unfair advantage. Step 2) Map the workflow - Literally draw it out. - Every step, every handoff. Step 3) Do the job as a service - Manually. - For real clients. - Before any code. Step 4) Document the edge cases - This is where the real IP lives. - You only find them by doing the work. Step 5) Add vertical agents to replace each step - Now you have proprietary data and a workflow you own. Skip steps 1–4 and you're just building a demo.

The Startup Ideas Podcast (SIP) 🧃

14,202 次观看 • 3 个月前

ANTHROPIC JUST GAVE AWAY THE COURSE EVERYONE ELSE CHARGES FOR it is a free 1 hour class on Loop Engineering built around Fable 5 this is the cleanest breakdown of Claude Code and agentic loops out there right now people are selling paid tutorials that cover less than this hour does you watch it once and you understand how to wire Claude into loops that run real work on their own start with the course, then go deeper on the step by step of building the loops yourself if you want the setup that keeps you ahead of everyone still typing code by hand, i put it all in my article below
1:01:16

ANTHROPIC JUST GAVE AWAY THE COURSE EVERYONE ELSE CHARGES FOR it is a free 1 hour class on Loop Engineering built around Fable 5 this is the cleanest breakdown of Claude Code and agentic loops out there right now people are selling paid tutorials that cover less than this hour does you watch it once and you understand how to wire Claude into loops that run real work on their own start with the course, then go deeper on the step by step of building the loops yourself if you want the setup that keeps you ahead of everyone still typing code by hand, i put it all in my article below

Atlas

30,921 次观看 • 17 天前

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this
0:24

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,186 次观看 • 1 个月前

Your Claude has a tell, and almost nobody uses it. Make it start every reply with your name. One line in custom instructions, no code. The moment it stops saying your name, its context window is full. That is the exact point the output starts drifting, and you do not notice. Name stops? Start a fresh chat. It has killed about 90% of my “why has Claude gone weird” moments. Miners sent a canary down the pit to catch the gas they could not see. Same trick, for your context. Comment GUIDE and I’ll send you the exact canary setup.
0:48

Your Claude has a tell, and almost nobody uses it. Make it start every reply with your name. One line in custom instructions, no code. The moment it stops saying your name, its context window is full. That is the exact point the output starts drifting, and you do not notice. Name stops? Start a fresh chat. It has killed about 90% of my “why has Claude gone weird” moments. Miners sent a canary down the pit to catch the gas they could not see. Same trick, for your context. Comment GUIDE and I’ll send you the exact canary setup.

Charlie Hills

22,956 次观看 • 23 天前

YOUR AI IS FORGETTING EVERYTHING YOU TAUGHT IT YESTERDAY. That is why most outputs still feel generic. The people getting real leverage in 2026 fixed this with one setup: Obsidian + Claude Code. Obsidian stores your thinking. Claude Code reads the patterns. Your notes become permanent context the agent can access anytime: Daily thoughts. Projects. Ideas. Contradictions. Questions you keep returning to. Then the real unlock: Custom slash commands. `/context` loads your recent thinking instantly. `/emerge` finds hidden ideas across your notes. `/challenge` tests your beliefs against your past writing. `/trace` maps how your thinking evolved over time. One critical rule: The AI never writes to the vault. You write. The agent reads. That is what keeps the system valuable. At first it feels like note-taking. Eventually it feels like a second brain.
0:49

YOUR AI IS FORGETTING EVERYTHING YOU TAUGHT IT YESTERDAY. That is why most outputs still feel generic. The people getting real leverage in 2026 fixed this with one setup: Obsidian + Claude Code. Obsidian stores your thinking. Claude Code reads the patterns. Your notes become permanent context the agent can access anytime: Daily thoughts. Projects. Ideas. Contradictions. Questions you keep returning to. Then the real unlock: Custom slash commands. `/context` loads your recent thinking instantly. `/emerge` finds hidden ideas across your notes. `/challenge` tests your beliefs against your past writing. `/trace` maps how your thinking evolved over time. One critical rule: The AI never writes to the vault. You write. The agent reads. That is what keeps the system valuable. At first it feels like note-taking. Eventually it feels like a second brain.

Dami-Defi

41,141 次观看 • 2 个月前

I just built a self-improving second brain in Claude Code 🤯 A brain that runs your brand: every tool reads from it, it's wired to your live data, and it gets smarter every week. All running on the Claude Agent SDK. Perfect for DTC brands and agencies whose AI output sounds generic because every new chat starts from zero. If you're re-explaining your brand to AI every single time — re-pasting the voice guidelines, re-describing the customer you've described a hundred times, re-uploading the same positioning doc you uploaded yesterday, and still editing for an hour to strip out the generic phrasing... A brand second brain fixes the entire loop: → Build 3 foundation files once: brand DNA, voice, and customer → Every skill you create reads from them automatically → Wire in live data — your ad account, competitor ads, customer reviews → A weekly routine refreshes the brain with what's actually working → Every output comes back on-brand on the first pass No re-briefing AI on every chat. No hour of editing to undo generic phrasing. No brain that goes stale the week after you build it. What a second brain gives you: → The exact 3-file foundation that runs the whole system → The skill structure that makes every tool brand-aware by default → The live-data wiring that keeps it grounded in reality → The weekly self-improvement loop that keeps it sharp → The cold-start sequence to stand it all up from zero Built 100% in Claude Code. I put together the full playbook with the file structure, the wiring, and the exact setup. Want it for free? > Like this post > Comment "BRAIN" And I'll send it over (must be following so I can DM)
0:24

I just built a self-improving second brain in Claude Code 🤯 A brain that runs your brand: every tool reads from it, it's wired to your live data, and it gets smarter every week. All running on the Claude Agent SDK. Perfect for DTC brands and agencies whose AI output sounds generic because every new chat starts from zero. If you're re-explaining your brand to AI every single time — re-pasting the voice guidelines, re-describing the customer you've described a hundred times, re-uploading the same positioning doc you uploaded yesterday, and still editing for an hour to strip out the generic phrasing... A brand second brain fixes the entire loop: → Build 3 foundation files once: brand DNA, voice, and customer → Every skill you create reads from them automatically → Wire in live data — your ad account, competitor ads, customer reviews → A weekly routine refreshes the brain with what's actually working → Every output comes back on-brand on the first pass No re-briefing AI on every chat. No hour of editing to undo generic phrasing. No brain that goes stale the week after you build it. What a second brain gives you: → The exact 3-file foundation that runs the whole system → The skill structure that makes every tool brand-aware by default → The live-data wiring that keeps it grounded in reality → The weekly self-improvement loop that keeps it sharp → The cold-start sequence to stand it all up from zero Built 100% in Claude Code. I put together the full playbook with the file structure, the wiring, and the exact setup. Want it for free? > Like this post > Comment "BRAIN" And I'll send it over (must be following so I can DM)

Mike Futia

17,831 次观看 • 1 个月前

A DOCTOR BUILT AN AI-QUERYABLE DATABASE OF EVERY DISEASE HE KNOWS IN OBSIDIAN. THE SAME STACK CAN RUN AN ENTIRE COMPANY ON ONE PERSON'S BRAIN Zoomed out, his vault looks like a constellation. Every disease linked to its symptoms, every symptom to the conditions it shows up in, every treatment to what it treats. Adding a new case is one note that wires itself into the rest. It's a personal database, and the structure has nothing to do with medicine. It's just nodes and links. Once you see that, the same setup runs anything: > a startup that needs to remember every customer, decision, and meeting; > a school whose curriculum links to every lecture and student question; > a business where SOPs, clients, and vendors all sit in one queryable graph. Drop Claude on top, and the vault stops being a map. It becomes something you can ask, in plain English, across everything you've ever written down. Full Claude + Obsidian build in the article below. Bookmark this
0:21

A DOCTOR BUILT AN AI-QUERYABLE DATABASE OF EVERY DISEASE HE KNOWS IN OBSIDIAN. THE SAME STACK CAN RUN AN ENTIRE COMPANY ON ONE PERSON'S BRAIN Zoomed out, his vault looks like a constellation. Every disease linked to its symptoms, every symptom to the conditions it shows up in, every treatment to what it treats. Adding a new case is one note that wires itself into the rest. It's a personal database, and the structure has nothing to do with medicine. It's just nodes and links. Once you see that, the same setup runs anything: > a startup that needs to remember every customer, decision, and meeting; > a school whose curriculum links to every lecture and student question; > a business where SOPs, clients, and vendors all sit in one queryable graph. Drop Claude on top, and the vault stops being a map. It becomes something you can ask, in plain English, across everything you've ever written down. Full Claude + Obsidian build in the article below. Bookmark this

Yarchi

32,476 次观看 • 1 个月前

Anthropic Engineer Andrej Karpathy: "The biggest mistake in AI right now - people are forcing agents to work instead of mastering the model first We made that mistake in 2016 at OpenAI - It cost us 5 years " what Karpathy actually means: step 1 → stop forcing your agent to do everything, understand the model underneath first step 2 → demos are easy - products take a decade. self-driving proved it - if you skip the foundation, everything breaks step 3 → the agent is not the product. the foundation is. build that - and agents emerge on their own "you building agents right now - you're at the forefront. not OpenAI. not DeepMind. you " watch - bookmark, then read article below ↓
5:39

Anthropic Engineer Andrej Karpathy: "The biggest mistake in AI right now - people are forcing agents to work instead of mastering the model first We made that mistake in 2016 at OpenAI - It cost us 5 years " what Karpathy actually means: step 1 → stop forcing your agent to do everything, understand the model underneath first step 2 → demos are easy - products take a decade. self-driving proved it - if you skip the foundation, everything breaks step 3 → the agent is not the product. the foundation is. build that - and agents emerge on their own "you building agents right now - you're at the forefront. not OpenAI. not DeepMind. you " watch - bookmark, then read article below ↓

codila

1,904,782 次观看 • 1 个月前

CEO of Nvidia said something that stopped me cold: "You may or may not lose a job to an AI, but you will absolutely lose a job to someone who uses AI" this 41 minutes is the most important talk on AI you'll watch this year so the question is not whether AI is coming for your job it's whether you're the one using it or the one being replaced by someone who does Nvidia already has hundreds of thousands of agents running inside the company right now agents are not the future, they are how the best teams work today I wrote a step by step guide on how to build your first AI agent with Claude Code you can find it in the article below
41:34

CEO of Nvidia said something that stopped me cold: "You may or may not lose a job to an AI, but you will absolutely lose a job to someone who uses AI" this 41 minutes is the most important talk on AI you'll watch this year so the question is not whether AI is coming for your job it's whether you're the one using it or the one being replaced by someone who does Nvidia already has hundreds of thousands of agents running inside the company right now agents are not the future, they are how the best teams work today I wrote a step by step guide on how to build your first AI agent with Claude Code you can find it in the article below

Anatoli Kopadze

14,627 次观看 • 1 个月前

THIS CHINESE DEVELOPER’S NEURAL NETWORK VISUALIZATION IS EXACTLY HOW YOUR OBSIDIAN VAULT SHOULD WORK every node connects to every other node and the whole thing gets smarter the more data flows through it, same way a real knowledge system should work but almost nobody builds it like that most people throw everything into folders and tags and call it a second brain but what they actually built is an archive that gets harder to use every month claude reads across everything you ever captured and finds the connection you need right when you need it here’s how to build the version that actually compounds ↓
0:32

THIS CHINESE DEVELOPER’S NEURAL NETWORK VISUALIZATION IS EXACTLY HOW YOUR OBSIDIAN VAULT SHOULD WORK every node connects to every other node and the whole thing gets smarter the more data flows through it, same way a real knowledge system should work but almost nobody builds it like that most people throw everything into folders and tags and call it a second brain but what they actually built is an archive that gets harder to use every month claude reads across everything you ever captured and finds the connection you need right when you need it here’s how to build the version that actually compounds ↓

leopardracer

231,513 次观看 • 2 个月前

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch
35:25

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

193,219 次观看 • 3 个月前

CLAUDE JUST TURNED OBSIDIAN INTO A BRAIN THAT NEVER FORGETS (FOR $0) Someone connected Claude straight to their Obsidian vault. Now the AI reads and writes every note they own. Every client, every idea, every project. Instant recall. Runs on Claude + Obsidian. One evening. Zero code. The numbers are insane: - Notion AI: $10/month forever - A "second brain" course: $500 to $2,000 - An assistant to organize your notes: $3,000/month - This setup: $0 - Time to build: one evening - Skill required: copy the steps The opportunity is even wilder: People sell Notion "second brain" templates for $99 to $499. You just built something better for free, and it never forgets. One free vault can hold the entire memory of your business: clients, content, SOPs, ideas. One person + Claude + Obsidian + one evening = an infinite memory that never forgets. Save and watch the clip.
13:03

CLAUDE JUST TURNED OBSIDIAN INTO A BRAIN THAT NEVER FORGETS (FOR $0) Someone connected Claude straight to their Obsidian vault. Now the AI reads and writes every note they own. Every client, every idea, every project. Instant recall. Runs on Claude + Obsidian. One evening. Zero code. The numbers are insane: - Notion AI: $10/month forever - A "second brain" course: $500 to $2,000 - An assistant to organize your notes: $3,000/month - This setup: $0 - Time to build: one evening - Skill required: copy the steps The opportunity is even wilder: People sell Notion "second brain" templates for $99 to $499. You just built something better for free, and it never forgets. One free vault can hold the entire memory of your business: clients, content, SOPs, ideas. One person + Claude + Obsidian + one evening = an infinite memory that never forgets. Save and watch the clip.

shmidt

57,347 次观看 • 1 个月前

Figma Capture + Claude Fable 5 = clone any competitor's landing page in minutes 🤯 Figma just dropped a Chrome extension that copy/pastes any live website into Figma as editable layers. Point Claude Code — running the new Fable 5 model — at the capture, and it rebuilds the whole page in YOUR brand: structure, copy, design system, photography. All inside Claude Code. Perfect for DTC brands and agencies who keep losing weeks rebuilding proven landers from scratch. If you're still cloning competitor pages the old way, You're screenshotting their site and praying the AI guesses the structure right. You're rebuilding sections by hand because the fonts and spacing never come out true. You're paying a designer $3K to recreate a page that already exists. This workflow eliminates the entire loop: → Capture the competitor's landing page with Figma's new Chrome extension — editable layers, not screenshots → Claude Code reads the page structure through the Figma MCP: every section, every headline, in order → It rebuilds the page in YOUR brand — your colors, your fonts, your voice (it even respects your banned-words list) → GPT Image 2 generates on-brand product photography from the layer names → Claude places every image automatically — finished page, ready to ship No screenshots. No guessing at structure. No design invoice. What you get: → A pixel-structured clone of any proven lander, rebuilt in your brand → Every line of copy rewritten in your voice → 16 on-brand images generated and placed for ~$2 in API costs → Start to finish in about 15 minutes Built 100% with Figma + Claude Code on Claude Fable 5. I put together a step-by-step playbook showing you exactly how to set it up. Want access for free? > Like this post > Comment "CLONE" And I'll send it over (must be following so I can DM)
0:34

Figma Capture + Claude Fable 5 = clone any competitor's landing page in minutes 🤯 Figma just dropped a Chrome extension that copy/pastes any live website into Figma as editable layers. Point Claude Code — running the new Fable 5 model — at the capture, and it rebuilds the whole page in YOUR brand: structure, copy, design system, photography. All inside Claude Code. Perfect for DTC brands and agencies who keep losing weeks rebuilding proven landers from scratch. If you're still cloning competitor pages the old way, You're screenshotting their site and praying the AI guesses the structure right. You're rebuilding sections by hand because the fonts and spacing never come out true. You're paying a designer $3K to recreate a page that already exists. This workflow eliminates the entire loop: → Capture the competitor's landing page with Figma's new Chrome extension — editable layers, not screenshots → Claude Code reads the page structure through the Figma MCP: every section, every headline, in order → It rebuilds the page in YOUR brand — your colors, your fonts, your voice (it even respects your banned-words list) → GPT Image 2 generates on-brand product photography from the layer names → Claude places every image automatically — finished page, ready to ship No screenshots. No guessing at structure. No design invoice. What you get: → A pixel-structured clone of any proven lander, rebuilt in your brand → Every line of copy rewritten in your voice → 16 on-brand images generated and placed for ~$2 in API costs → Start to finish in about 15 minutes Built 100% with Figma + Claude Code on Claude Fable 5. I put together a step-by-step playbook showing you exactly how to set it up. Want access for free? > Like this post > Comment "CLONE" And I'll send it over (must be following so I can DM)

Mike Futia

46,721 次观看 • 1 个月前