plusxbt

It is becoming f*cking dangerous: Fable 5.2 is already inside Claude Code, and it stays off until you turn it on 1. Update Claude Code to v2.1.321 or newer, the first version with Fable 5.2 2. Type /model fable, or start with claude --model fable 3. Check the Fable row in /model: if it says Requires usage credits, Fable spends credits instead of your plan limits 4. Hand it the ambiguous problems: a root cause hunt, an outage, an architecture call 5. Describe the result you want and let it work out the steps 6. Stop adding "verify your work" to prompts, it checks its own work more often than smaller models 7. Give it a whole task you would normally split into pieces Claude Code docs say it suits tasks larger than a single sitting 1M context window by default, medium effort to start, API price $8 / $40 per million tokens, down from $10 / $50 for Fable 5.1 Full guide in the article below

It is becoming f*cking dangerous: Apple shipped its own plugin for Claude Code that builds, tests and runs your iPhone app 1. Update to Xcode 27 on your Mac, the plugin ships inside Xcode itself 2. Open Claude Code in your project and run /plugin install xcode@claude-plugins-official 3. Open the project in Xcode and allow the agent when Xcode asks the first time 4. Ask Claude to build the app and launch it on the iPhone simulator 5. Let it drive the simulator and check how the app behaves 6. Ask for SwiftUI previews and the build log, it reads the errors and fixes them 7. Run Apple's own skills: VoiceOver and Dynamic Type specialists, XCTest to Swift Testing Author on the listing: Apple Inc., added to Anthropic's official marketplace on Nov 6 Claude Code pulls the plugin from your local Xcode every session, so it updates with Xcode Full guide in the article below

This is getting out of hand: everyone is making showreels with Opus 5.5 and sleeping on the ~450 ready-made motion blocks that make them look pro. HeyGen dropped HyperFrames on GitHub, a set of skills that plug straight into Claude: -> github.com/heygen-com/hyperf… Why are you still asking AI to draw every frame from scratch? Stop treating Claude as a script writer. Start turning it into a full motion studio. Here is the workflow: install the core set once, describe the video in one sentence, and Claude assembles it from ready blocks (kinetic type, captions, 3D camera moves). It works like a LEGO box for video: you never build a brick yourself, you just snap them together. Step-by-step setup: 1. Run npx skills add heygen-com/hyperframes and pick "Core Skills" 2. Type /hyperframes plus your idea, like a 10-second product intro with a fade-in title 3. Add /media-use for music, voiceover and color grading, or paste a Figma link into /figma 4. Move old Remotion, Lottie or Three.js projects over with /remotion-to-hyperframes 5. Run /reverse-any-video on any clip and instantly get it back as an editable project, frame by frame The whole install is one command, and you will never animate a title by hand again. Full step-by-step guide in the article below Make sure to save this post for later

Motion designers are cooked. Opus 5.5 doesn't make videos. it writes the code that draws them I rewound every viral Opus 5.5 video. the same 7 layers sit under all of them: THE 7 LAYERS ┣ 01 picture · 900 still frames = 15 seconds of video ┣ 02 code · one function draws any moment: seek(t) ┣ 03 sound · every big moment lands on a beat ┣ 04 rules · a CLAUDE.md that bans the AI look by name ┣ 05 reference · cut a video you love into frames. steal the style, never the story ┣ 06 words · one line, one paragraph or one night (9,500 characters) ┗ 07 second look · claude scores its own frames, fixes the 3 worst, repeats until 8+ setup takes 10 minutes: /npm i -D playwright && npx playwright install chromium this video is one HTML file claude wrote. every frame drawn in JavaScript, every sound generated in python. 0 cameras, 0 After Effects 6 copy-paste prompts + the full rewind are in the article below ↓ bookmark it before you make your first one

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