Loading video...

Video Failed to Load

Go Home

1. Create a folder named ⁠second-brain⁠ on your PC 2. Open Claude Code inside this folder and install ⁠GWS CLI⁠ (to get access to your Gmail, Calendar, and Drive) 3. Create a subfolder named ⁠memory⁠ inside the main folder 4. Create a ⁠CLAUDE.md⁠ file in the main folder and...

46,743 views • 1 month ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

It is becoming f*cking dangerous: I don't understand why everyone still isn't doing this, thanks to this I reached an income of $12,000 as early as 3 months ago Andrej Karpathy, co-founder of OpenAI, shared a straightforward concept that blew up with over 23 million views: stop relying on AI strictly for coding and start using it to construct your own personal knowledge engine Point Claude Code to a folder, toss in raw materials (whether it's an article, a video transcript, or a PDF) and Claude processes everything, links relevant topics together, and organizes it into a self-updating wiki of your personal knowledge. It acts like compound interest: the more information you add, the more capable it becomes Here is the exact breakdown: Set up Obsidian, create a fresh vault, and open it using Claude Code Supply Karpathy's wiki layout prompt and instruct Claude to build the architecture Claude automatically sets up three components: a ⁠raw⁠ directory for source files, a ⁠wiki⁠ directory for processed pages, and a ⁠CLAUDE.md⁠ control file to run the system Dump any document into the ⁠raw⁠ folder and run "ingest this" Query your entire knowledge repository at any time, indefinitely It takes just five minutes to configure, eliminating the need to ever start a conversation with a completely blank context window again Check the link below for the complete step-by-step walkthrough on setting up Claude with Obsidian Bookmark this post for later

Bober_smart

83,847 views • 23 days ago

I don't f*cking understand why designers aren't running this crazy setup Graphify, the Claude Code skill that turns any folder into a knowledge graph, is past 136k stars on GitHub. give Claude one folder, plug in 6 repos, and it stops making the same purple-gradient AI site. designer, founder, indie hacker, doesn't matter: it learns your brand, builds, screenshots and fixes before you look. here's the whole setup: > make a folder called DESIGN, open Claude Code in it, drop in brand PDFs, logos, screenshots, sites you love > uv tool install graphifyy, then graphify install, then /graphify . -> the whole pile becomes one graph. Claude knows your brand instead of guessing > claude plugin marketplace add nextlevelbuilder/ui-ux-pro-max-skill, then claude plugin install ui-ux-pro-max@ui-ux-pro-max-skill -> 192 palettes, 74 font pairings, so a bank site stops looking like a crypto casino > npx impeccable install, then /impeccable init -> 62 rules that catch AI-looking design the second it's written > claude mcp add figma -- npx -y figma-developer-mcp --figma-api-key=YOUR-KEY --stdio -> paste a Figma link, get that exact layout > npx shadcn@latest add REACT-bits/SplitText-TS-TW -> 215+ free animated components, the page actually moves > claude mcp add playwright npx @playwright/mcp@latest -> it opens the page in a real browser and checks its own work > /schedule "every Friday, run /impeccable audit and send me a fix list" -> now it runs on a routine 15 minutes of setup, and you never ship a generic AI site again. bookmark this and test asap

kiosa

32,957 views • 12 days ago

EVERYONE'S TRYING TO SOLVE AI TEAM MEMORY WITH SERVERS, VECTOR DATABASES, AND ORCHESTRATION PLATFORMS. THIS OPEN SOURCE TOOL DOES IT WITH ONE FOLDER IN YOUR REPO. Every dev on your team runs Claude Code. When one agent screws something up, the rest have no idea. They just repeat the mistake next week. It's called teamlore. When your agent gets corrected or breaks something, it writes a small lore file into a .lore/ folder. That file ships with your PR, gets reviewed like normal code, and after merge every teammate's agent automatically recalls it when they touch that part of the repo. No server. No datab No accounts. No SaaS bill. Just a folder in git. Which means code review catches bad lessons before they poison the team, git blame tells you when a rule was added and why, and the whole thing works offline. One command to install: npx teamlore init Companion command: npx teamlore scarmap. Turns your team's history of mistakes into a visual heat map of the codebase. Every red zone is a place your team has been burned before. Which means every red zone is a place your agents should slow down. Here's the wildest part. The teamlore repo's own .lore/ folder contains every mistake Claude made while building teamlore itself. Dogfooded end-to-end. You can literally open the folder and read the receipts. The author's public invitation: "Would love for someone to try and break it." Available on npm. Repo just launched. 100% open source. (link in the comments)

Harman

35,140 views • 3 months ago

Claude Cowork is f*cking cracked for Meta Ads 🤯 Point it at a folder with your ad export, your brand context, and your brief template —> ... and it analyzes your account like a senior creative strategist + saves a finished brief directly to your computer. All inside Claude Cowork. Perfect for DTC brands and agencies who are still manually digging through ad reports trying to figure out why performance shifted. If you're running Meta Ads and pulling weekly reports that tell you what happened but not why — CPAs creeping up, CTRs dropping... You're killing creatives on gut feel because mapping performance back to hook type, angle, and offer framing takes hours you don't have. Claude Cowork eliminates the entire loop: → Drop your Meta Ads CSV export into a project folder → Add a brand context file and your brief template → Claude reads all three files and audits across 4 lenses: hook performance, offer angles, fatigue signals, next test recommendations → Asks clarifying questions if it needs them → Saves a finished creative brief as a real .md file directly to your folder No copy-pasting data into chat windows. No manually tagging creatives in a spreadsheet. No "here are your metrics" summaries that tell you nothing new. What you get: → Pattern analysis across every creative — which hook structures are converting and why → Creative fatigue signals before CPAs blow up → Competitor intelligence layered in from the Meta Ad Library → A data-backed brief your creative team can execute immediately Set it up once, drop in a fresh CSV every week and run the same prompt. I put together a full playbook with the exact folder setup, the prompts, and the brief template to get this running in under 30 minutes. Want it for free? > Like this post > Comment "ADS" And I'll send it over (must be following so I can DM)

Mike Futia

86,067 views • 8 months ago