How a small team actually uses Claude Code. Our setup, our prompts and the skills we deleted.

Two months of Claude desktop changes, checked against Anthropic's docs: what to use, what to skip, and what Team plans don't get yet.

Our Claude Code chief of staff runs at day's end: 39 runs, 626 owed replies found. How to build yours, and where Claude Duet's morning brief wins.

Claude Code vs Cowork: same agent, different home. Why our team picked the terminal, and how scheduled tasks and Claude Duet run while you're away.

Claude Code works for non-technical people when the work is documents. Our team installs four things. What we took off their plate, and what's still hard.

CLAUDE.md best practices from a 223-line file: what goes in, what belongs in a skill, where nested files go, and a starter template under 25 lines.

Our Claude Code skills and commands went from 41 to 103 in a month. We deleted 52, the one we missed came back better, and the pile grew back anyway.

Claude Code use cases for business that pay off put documents in and get documents out. What our 66 commands do by department, and where each falls short.

Claude Code for project management: ours drafts weekly client updates and retros, refuses to draft while a video link is missing, and never presses send.

Claude Code team setup for people who don't code: one repo, shared settings in git, a /setup command that reads our roster, and what broke on day one.

Five Claude Code prompting lessons from 356 sessions building an interactive guide with SkiFree and a music engine. The biggest: name the reference.

Panel of experts prompting asks AI to simulate specific experts who argue. Copyable templates, what the debate research found, and when it's overkill.