Company Playbook
The playbook is a living reference for how the team builds, ships, and maintains software. It captures standards, tooling decisions, and reusable patterns so that every contributor works from the same foundation.
What is in the playbook
| Section | Purpose |
|---|---|
| Best Practices | Code quality, PR workflow, naming conventions |
| Commands Reference | CLI commands for every tool in the stack |
| Skills Catalog | Custom Claude Code skills used by the team |
| MCP Configuration | Model Context Protocol server setup |
| Templates & Snippets | Starter code for common patterns |
| Project Setup Checklist | End-to-end guide for new projects |
Why a playbook
- Onboarding — new team members get productive faster when standards are documented.
- Consistency — shared conventions reduce friction during code review.
- Automation — Claude Code skills and MCP servers multiply what a single developer can do.
- Institutional memory — decisions and their rationale are preserved even as the team changes.
How to contribute
- Open a branch and edit the relevant MDX file in
app/docs/playbook/. - Follow the existing heading structure and tone.
- Submit a pull request with a short description of what changed and why.
- After review, merge to
main— the docs deploy automatically via Vercel.
Principles
- Prefer explicit over implicit. Write things down rather than relying on tribal knowledge.
- Keep it current. Outdated docs are worse than no docs. Update pages when tools change.
- Be concise. Every sentence should earn its place. Link to external references for deep dives.
- Show, do not just tell. Include code samples, command examples, and screenshots where useful.