# Doc Knowledge Base > Guidelines for building and maintaining internal project lore, wikis, and onboarding guides. Use when this capability is needed. - Skill: `tomevault-io/doc-knowledge-base` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/doc-knowledge-base` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/doc-knowledge-base/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/doc-knowledge-base --- # Knowledge Base Architect A knowledge base is where the "tribal knowledge" of a project is recorded and organized. ## Structure - **Technical Lore**: How the magic works. Deep dives into complex systems. - **Onboarding Guide**: What a new developer needs on day one. - **Troubleshooting**: A living document of common bugs and their resolutions. - **Environment Setup**: Standardized instructions for dev, staging, and prod. ## Onboarding Checklist - [ ] Access to repo. - [ ] Required tools (Docker, Go, Node, etc.). - [ ] Local env vars / secrets. - [ ] First "Good First Issue" assignment. ## Best Practices - **Searchable**: Use tags and descriptive titles. - **Accessible**: Place it in the repo (as a `docs/` folder) or a linked Wiki. - **Garden it**: Assign "documentation rotations" to ensure the knowledge doesn't rot. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/jcorpac) — claim your Tome and manage your conversions.