plusxbt

This is getting out of hand: Karpathy shared one text file, and Claude Code turns your PDFs into a wiki it maintains for you 1. Make a folder and open Claude Code inside it 2. Create raw/ for your sources and wiki/ for the pages 3. Paste Karpathy's LLM Wiki idea file and ask Claude to write CLAUDE.md for your topic 4. Put a PDF, transcript or article in raw/ 5. Tell Claude to ingest it: a summary page, index.md and related pages updated, a new entry in log.md 6. Ask anything: it answers from wiki/ with citations, good answers can be saved as new pages 7. Ask for a lint pass now and then: contradictions, stale claims, orphan pages One source might touch 10-15 pages, so your knowledge is compiled once and kept current, not re-derived on every question Full guide in the article below

You are making a painful mistake if you still use Claude Code's default answers: one Markdown file rewrites how it talks to you 1. Type /output-style to see the four built-in styles besides Default 2. Run /output-style concise: every answer leads with the result, no preamble 3. Switch to explanatory: short ★ Insight blocks show why Claude wrote that code 4. Pick learning: Claude leaves TODO(human) spots for you to write yourself 5. Create your own: save diagrams-first.md in ~/.claude/output-styles with your rules 6. Add keep-coding-instructions: true so Claude still codes the same way 7. Restart Claude Code, run /output-style diagrams-first and ask it to explain your app It sets Claude's role, tone and format for every response in the session, so you stop repeating the same request in each prompt Full guide in the article below

It is becoming f*cking dangerous: the creator of Claude Code says one habit makes the final result 2-3x better 1. Give Claude a way to check its own work: tests, a bash command, a browser 2. Say "Prove to me this works" and have Claude diff the behavior of main vs your feature branch 3. Spin up a second Claude to review the plan as a staff engineer 4. End every correction with "Update your CLAUDE.md so you don't make that mistake again" 5. Check CLAUDE.md into git so the whole team shares the lessons 6. Set an agent Stop hook on long tasks, it runs the verification for you Boris calls it probably the most important thing for great results in Claude Code His own setup: Claude opens a browser, tests the UI and keeps iterating until the code works Full guide in the article below

I don't understand why everyone isn't using this yet: Claude Code can audit your CLAUDE.md and catch rules meant for older models 1. Update Claude Code to v2.1.283 or newer: claude update 2. Open your project and run /doctor prompt-audit 3. It reads CLAUDE.md, AGENTS.md, rules, skills and commands in .claude/ and ~/.claude/ 4. It flags instructions aimed at older models 5. It finds references to files and commands that don't exist 6. It catches files that contradict each other 7. You get a report with proposed edits, nothing changes until you ask Claude to apply them One folder only: /doctor prompt-audit .claude/skills/deploy Anthropic's docs: keep each CLAUDE.md under 200 lines, and if two rules contradict each other, Claude may pick one arbitrarily Full CLAUDE.md and folder setup in the article below

It is becoming f*cking dangerous: one prompt turns Claude Code into a FULL crypto trading agent that switches tactics when the market flips Zero code. Copy, paste, fill in exchange, pairs, timeframe, capital: Time: 1 min to paste Action: drop into Claude Code One-strategy bots trade a flat day and a dump the same way. This one does not Regime Detector: labels each bar SIDEWAYS, CHOPPY or DUMP via ADX+ATR, swaps playbook Kill Switch: equity falls 15% below peak, positions close, halt survives restarts Backtest Gate: 3+ years with fees, slippage and unseen data, blocks any strategy that lost or fell >15% Nightly Review: writes a tweaks report overnight, nothing changes without your OK Paper Mode: sim orders on live prices, no real money until you set LIVE=true Old way: code and test every rule by hand Now: one prompt, Claude Code builds the bot, tests risk, shows diff before running Passed backtest = survived the past, not a profit guarantee. Stay on paper until you trust it Full prompt in the reply below, bookmark this

THIS IS AN ABSOLUTE GOLDMINE Anthropic documented one of the strongest tricks in Claude Code The idea: Sonnet 5.5, Haiku 5.5 and Opus 5.5 in one setup, and each model only gets the work it's BEST at Opus stays on the hard calls, and it typically costs LESS than running Opus the whole time One command starts it: claude --model sonnet --advisor opus Who does what: > Sonnet 5.5 drives the main session and takes the routine work: writing and fixing code > Haiku 5.5 runs as read-only subagents (search, grep, docs), each in its own context window, sending back only a summary > Opus 5.5 is the advisor, called at decision points, and it sees the FULL conversation including every tool call and result > Opus isn't called every turn, so routine turns run at Sonnet prices, not Opus prices Claude decides when to call Opus, and it TENDS to do it at three moments: > Before it commits to an approach > When an error keeps coming back > Before it calls a task done Sonnet codes. Haiku scouts. Opus advises The math: per token Opus costs 2x Sonnet and 40x Haiku, so every routine job kept off Opus runs at half the price or less The full tree: Sonnet 5.5: main session, writes and edits code Search: read-only Haiku 5.5 subagent that maps the repo Grep: read-only Haiku 5.5 subagent that finds call sites Docs: read-only Haiku 5.5 subagent that reads API docs Opus 5.5: advisor that sees the whole conversation and every tool result when called Paste the tree plus this prompt into Claude Code Set up my Claude Code project to match this tree: 1. Make Sonnet 5.5 the main model and Opus 5.5 the advisor (advisorModel in settings) 2. Add three read-only subagents in .claude/agents/ (model: haiku, tools: Read, Grep, Glob): search (repo map), grep (call sites), docs (API docs) 3. Add one rule to CLAUDE.md: consult the advisor before committing to an approach, when an error repeats, and before calling a task done Before touching anything, show me the full diff and wait for my OK Bookmark this setup, you'll want it every session Step 3 lives in CLAUDE.md, the full CLAUDE.md guide is in the article below

I don't understand why everyone isn't doing this yet Anthropic documented a Claude Code feature where the STRONGEST model only kicks in at key moments instead of running the whole time The setup: Agent Teams in Claude Code Rather than one session doing everything, the work splits across a team: Lead (Opus 5.5, high effort): the main session, creates the tasks and runs the team Teammates (Sonnet 5.5, medium effort): each owns its own files, UX or backend Advisor (Fable 5.1): consulted before picking an approach, on a repeated error, before done Shared task list: teammates claim tasks, file locks stop two of them grabbing the same one Start the lead from the terminal: claude --advisor fable Then tell it: Spawn three teammates, one on UX, one on the backend, one playing devil's advocate. Use Sonnet for each teammate Paste this to set up your workspace: In settings.json, add CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 to the env block, set effortLevel to high Define roles in .claude/agents/ with model sonnet and effort medium, plus a devil's advocate role Give each teammate its own set of files to avoid overwrites Add a TaskCompleted hook that blocks a task from being marked done if checks fail Show me every config change before applying it The CLAUDE.md map your agents read, full guide in the article below > code.claude.com/docs/en/agen…

Build an absolute monster. Merge six Claude Code pieces into one system, it works the NIGHT SHIFT while you sleep Opus 5.5 + subagents + routines + web search + Playwright + CLAUDE.md Six pieces. One system. Nobody at the keyboard Opus 5.5 -> the main model that plans every task Subagents -> independent workers in .claude/agents/, each with its own role and context, returning only a summary Routines -> scheduled cloud agents on a cron, the system runs at night while your laptop is closed Web search -> scans public pages and forums for real complaints Playwright -> opens a real browser, clicks through every screen, catches bugs CLAUDE.md + memory files -> the map the agent reads on launch, every step and cost logged Give it one goal before bed: find a real gap people complain about and have a working prototype by 7 AM One hard rule: nothing spent, nothing published, nobody contacted without your yes Start the routine at 11:40 PM and go to sleep. Here is how one night can look: 12:10 AM: web search pulls ~1,900 public posts with the same complaint, gig drivers tracking income across 3 apps 1:00 AM: it maps the paid tools people already use and the 2 complaints they keep repeating 2:30 AM: Opus 5.5 plans 9 screens and one database without asking a question 4:10 AM: subagents write the code and a landing page draft 5:45 AM: Playwright clicks through every screen and logs bugs 7:20 AM: the memory log holds every step Morning: a working prototype and a landing draft waiting for your yes, $0 spent beyond tokens, nothing published A subagent with no payment or email tool physically CANNOT buy or send anything. The rules in CLAUDE.md apply to every session The biggest mistake: treating AI like a chat for answers. Give yours a GOAL, a DEADLINE and HARD RULES You write zero code. Playwright does the clicking. You're asleep the whole time Everyone is waiting for AGI. The night shift already exists Bookmark this. Full breakdown of the CLAUDE.md map in the article below

It is becoming f*cking dangerous: when Anthropic shipped CLAUDE.md, they didn't even realize they were opening a Pandora's box 1. Make an empty folder on your computer, call it SECOND BRAIN 2. Open Claude Code inside it 3. Add subfolders: MEMORY/, notes/, people/, projects/ 4. Drop a CLAUDE.md in the root with one rule: save every key fact to MEMORY, one topic per file 5. Add @-links in CLAUDE.md so key files load into context every session 6. Run claude mcp add to connect Playwright MCP, now Claude controls a real browser 7. Build a skill in .claude/skills/ so one command runs the entire routine Folder setup: about 5 minutes Your Claude becomes a second brain: it keeps every key fact between sessions, loads your main files by itself and drives a real browser Full guide in the article below