// 29 tips tagged "documentation"
The companyAnnouncements setting surfaces team messages to every developer at startup, directly in their Claude Code session.
Give Claude your OpenAPI spec and ask for a handcrafted typed API client — clean method names, custom error handling, and TanStack Query hooks, without the ugly auto-gen output.
Ask Claude to read your repo and generate complete GitHub Issue template files in the YAML forms format — bug reports, feature requests, and config.yml all tailored to your actual stack.
Let Claude read your entire codebase and generate a comprehensive onboarding guide that actually reflects the current state of the project.
Ask Claude Code to generate draw.io XML and paste it straight into diagrams.net for a quick, editable architecture overview.
Ask Claude to read your migrations and output a Mermaid ER diagram — it renders natively in GitHub, Notion, and most wikis with zero extra tooling.
Stop writing API clients by hand. If you have an OpenAPI or Swagger spec, Claude can generate a fully-typed client that matches your codebase conventions in minutes.
Undocumented code is technical debt waiting to bite you. Ask Claude to bulk-generate accurate docblocks for your entire codebase in one sweep.
Pipe your git diff directly to Claude and get a properly formatted Keep a Changelog entry — Added, Changed, Fixed, and all.
Once you've settled an architectural debate with Claude, write the decision into CLAUDE.md — or it will suggest the same alternatives again next session.
Claude Code's full codebase context makes it a powerful writing partner for strategy docs, product specs, and meeting notes -- the plans it produces reference your actual technical constraints, not generic boilerplate.
Writing a plan.md before Claude starts building gives you a persistent checkpoint you can hand to a fresh session to continue exactly where you left off.