plusxbt

I don't understand why everyone isn't doing this yet: Anthropic's own Claude Code guide lists 7 habits you can stop 1. Stop typing think hard, it's plain text, effort is the control: set /effort or type ultrathink for one turn 2. Delete IMPORTANT and ALL CAPS, shouted rules get over-applied, turn hard rules into a hook or deny rule 3. Cut architecture and file trees from CLAUDE.md, Claude reads the repo, keep only what isn't in there 4. Drop keep going and don't be lazy, it's more likely to cause over-work, give Claude a check to pass, /goal for unattended runs 5. Quit spawning subagents just to save context, most models have a 1M window, keep them for parallel work 6. Stop handing a task to a subagent for a better answer, a fresh reviewer helps because it hasn't seen your reasoning 7. Stop rationing context, it compacts on its own, still /clear between tasks for better, cheaper answers Opus 5.5 runs at medium effort by default, /effort status shows yours In the terminal ultrathink turns rainbow when it can raise that turn to xhigh, v2.1.311+ Full guide in the article below

It's pretty wild that people still run Claude Code bare when these 7 repos have over 1,000,000 GitHub stars combined 1. Load 4 coding rules drawn from Karpathy's post (230K): /plugin marketplace add forrestchang/andrej-karpathy-skills 2. Make Claude write the least code that works (186K): /plugin marketplace add DietrichGebert/ponytail 3. Add 7 design skills with 192 palettes (146K): /plugin marketplace add nextlevelbuilder/ui-ux-pro-max-skill 4. Run Garry Tan's own setup, /office-hours to /ship (141K): paste the install line from github.com/garrytan/gstack, needs Bun 5. Cut Claude's replies to caveman length, code stays exact (118K): /plugin marketplace add JuliusBrussee/caveman 6. Add Addy Osmani's 25 skills, spec to ship (114K): /plugin marketplace add addyosmani/agent-skills 7. Shrink the shell output Claude reads (86K): brew install rtk, then rtk init -g After each marketplace add, run /plugin and install it from the Discover tab gstack adds a Stop hook and Codex reviews of your diffs, rtk patches settings.json: read both READMEs first Full guide in the article below

Everyone is obsessed with making AI smarter. Almost nobody is talking about the fact that their AI keeps forgetting everything they teach it. Claude Code can become something much more interesting than a coding assistant. A second brain that remembers your projects, decisions, people and notes across sessions. Here's how to build it: 1. Create a folder called SECOND BRAIN 2. Open Claude Code inside it 3. Add four folders: MEMORY/, notes/, people/, projects/ 4. Create a CLAUDE.md that tells Claude how to organize and retrieve important information 5. Use @-imports to load your most important memory files at startup 6. Tell Claude to save key decisions as Markdown files, one topic per file 7. Create a custom /brain skill to search your notes and bring relevant context back Now watch the video. Every branch represents stored knowledge. The glowing line visualizes a memory being retrieved. Something you decided weeks ago can become useful context in a completely new session. No vector database. No expensive memory app. Just Markdown files and Claude Code. The crazy part? Your knowledge doesn't have to disappear when the conversation ends. Full SECOND BRAIN setup in the article below.

I still don't get why everyone isn't fixing this: Claude Code silently deletes your chats after 30 days, one line changes it 1. Open ~/.claude/settings.json and add "cleanupPeriodDays": 3650, 0 fails validation 2. Keep secrets out, transcripts sit in ~/.claude/projects as plain text, check the size: du -sh ~/.claude/projects 3. Name work while you still remember it: /rename auth-fix, later in the same repo claude --resume auth-fix 4. Query an old chat without touching it: claude -p --resume <session-id> --fork-session "list the decisions we made" >> decisions.md 5. Export the open chat: /export auth-fix.txt 6. Ask Claude to add a SessionEnd hook that copies transcript_path into your second brain folder, every chat lands there when it exits normally 7. Run /insights: an HTML report on what you work on and where you hit friction, it spends your tokens Plans, checkpoints, subagent logs and /insights reports go in the same sweep, no message shown Transcripts of sessions started or last continued in the desktop app or Cowork are exempt by default Full guide in the article below

It is becoming f*cking dangerous: one command in Claude Code turns your codebase into a map, 141K stars in 7 months 1. Install with uv, the package has two y's: uv tool install --python 3.13 graphifyy 2. Add the skill to Claude Code: graphify install 3. List tests, docs and images in .graphifyignore: test factories took 6 of the top 10 spots in a repo Graphify reviewed, each image gets its own subagent 4. In a repo you trust, start Claude Code at the root, type /graphify . (tree-sitter parses code with no LLM, Claude still spends tokens running it) 5. Open graphify-out/graph.html and read GRAPH_REPORT.md: most connected nodes first, then surprising connections 6. Ask with words from your code: graphify query "auth token", or trace a path: graphify path "A" "B" --undirected 7. Remind Claude to check the graph: graphify claude install, rebuild the code part on every commit: graphify hook install Every edge is tagged EXTRACTED, INFERRED or AMBIGUOUS: check the source before you trust the last two Official repo: github.com/Graphify-Labs/gra… Full guide in the article below

It is hard to believe, but 66,000 GitHub stars went to a way of running Claude Code without paying Anthropic 1. Open github.com/Alishahryar1/free…, on Mac or Linux run the curl installer from the README 2. Run fcc-server on Linux or open the Free Claude Code app on Mac and Windows, it opens the Admin UI 3. Turn on Proxy Authentication with your own token, by default the proxy is open to your whole network 4. Create an API key at build.nvidia.com, paste it under Providers, NVIDIA NIM, Add key, Save, then click Apply 5. Start the agent with fcc-claude 6. Switch in the native /model picker among providers you set up, 61 in the catalog, free and paid, DeepSeek, Kimi, Groq, Ollama 7. Add Fallback Models so a dead provider rolls to the next one, a failed request can consume usage from more than one Free routes mean other models, not Claude, Anthropic does not support this, and your code goes to the provider unless it is local The README claims 1.3B+ free tokens a month, availability and limits are set by each provider and can change Full guide in the article below

Whoever built this will put video editors out of work: raw footage in a folder, Claude Code hands back final.mp4 1. Paste the setup prompt from github.com/browser-use/video… into Claude Code, it installs itself 2. Export your ElevenLabs key first, the tool is free and open source, you pay for transcription and Claude usage 3. Drop your raw takes into one folder, cd there and run claude, transcription starts right away so test on one short clip 4. Type: edit these into a launch video 5. Read the plan it proposes and say OK, it does not touch the cut before that 6. Wait while it removes umms and dead space, ask for color grade, subtitles and overlays too, each overlay gets its own subagent 7. Approve the preview to get edit/final.mp4, every cut is checked first, up to 3 fix passes 30K+ GitHub stars, MIT license, works for talking heads, montages, tutorials, travel, interviews Claude reads a ~12KB transcript plus PNG filmstrips, frame by frame would be about 45M tokens Full guide in the article below

I still don't get why anyone builds a second brain for Claude Code from scratch when these 7 repos have over 75,000 stars combined 1. Teach Claude Obsidian's formats and tools with 6 skills from its CEO: github.com/kepano/obsidian-s… 2. Run wiki-ingest on text in inbox/, review the plan, get linked notes: github.com/AgriciDaniel/clau… 3. Save decisions and tasks with obsidian-save, load your current state next session with obsidian-world: github.com/eugeniughelbur/ob… 4. Run an unofficial Karpathy-style wiki with ingest, query and lint: github.com/Astro-Han/karpath… 5. Copy a starter vault plus 18 skills and 72 commands: github.com/undefined-ui/seco… 6. Turn your ChatGPT and Claude exports into linked notes, run only step 1 of its README: github.com/charlie947/ai-sec… 7. Split auto-loaded memory from wiki pages read on demand, ignore its tip to keep secrets in memory: github.com/MehmetGoekce/llm-… Pick one, they overlap: all seven work with plain Markdown you can open in any editor Full guide in the article below

It is becoming f*cking dangerous: one line in Claude Code builds a turbofan with 3,597 parts you can cut open and break 1. Install the open source skill (Node 22.20+): npx skills add AirsupHQ/machine-skill -g -a claude-code 2. Add Playwright in its folder: cd ~/.claude/skills/machine && npm i && npx playwright install chromium 3. Open a new Claude Code session in an empty folder and type: /machine a turbofan jet engine, the kind that pushes a widebody off the runway 4. Let Claude write down real dimensions, parts list and physics, then build it 5. Open the HTML file, drag the throttle, try explode, cutaway, x-ray 6. Hit the break button: it throws a fan blade and the solver computes the load the case has to hold 7. Film it from that folder with your file's name (needs ffmpeg): node ~/.claude/skills/machine/scripts/record.mjs turbofan.html out/turbofan.mp4 The makers' estimate: about an hour per machine You get one HTML file: the makers' demo counts 3,597 parts, nearly all blades, yours will differ, and the physics is a small model, not CFD Full guide in the article below