What Anthropic's Own Teams Do Differently in Claude Code
Anthropic published how its internal teams actually run Claude Code — and the loudest wins came from lawyers, marketers, and data scientists, not senior engineers. Here are the five habits worth stealing, with the real numbers behind each one.
- #claude-code
- #workflows
- #anthropic
- #productivity
Sign in to keep reading
What Anthropic's Own Teams Do Differently in Claude Code — Anthropic published how its internal teams actually run Claude Code — and the loudest wins came from lawyers, marketers, and data scientists, not senior engineers. Here are the five habits worth stealing, with the real numbers behind each one.
Your first guide is free. Sign in with Google or LinkedIn to read the whole library and get new guides as they ship — no cost.
Keep reading
More guides like this one.
Stop Watching AI Demos. Read Their Transcripts.
A finished repo teaches you nothing about how it got finished. Since December 2025 you can read a power user's entire Claude Code session — every prompt, every wrong turn, every correction. Here are the five sessions and write-ups worth studying, and exactly what to look for in each.
The Claude Code Commands You Skip Are All the Same Command
There are over 60 built-in slash commands. Most people use four. Sort the ones you are missing by what they actually do and a pattern appears — almost all of them exist to manage one resource, and it is the one quietly wrecking your long sessions.
A Good Handoff Is Mostly a List of Dead Ends
Compaction and `/resume` both preserve what happened. Neither preserves what you decided against — and the abandoned attempts are the most expensive thing in a long session. Here's the handoff file that fixes it, the prompt that writes it, and the one-liner that generates it from a session you already closed.