documentation-standards

Documentation standards provide clear guidelines for file placement, naming conventions, and structure across internal development docs, user-facing docs, project root, and Claude skills. This ensures consistency and makes documentation easier to maintain and navigate across all repositories.

Standards codify Markdown formatting rules, frontmatter usage, relative linking, and syntax-highlighted code blocks. Consistent cross-reference standards maintain link integrity and guide users between documentation categories—internal guides, user docs, and skill references.

Documentation standards specify placement rules for each documentation type: user guides go in user-facing docs, development guides in internal development folders, project-level information in the root, and AI skill references in the skills directory. This prevents scattered documentation.

Standards define ongoing maintenance procedures, file naming conventions, table of contents structure, and migration guidance. Following these workflows ensures contributor changes align with existing documentation organization and formatting rules.

Standards are designed for PRPM repositories specifically, covering internal development docs, user-facing documentation, project root, and Claude skills. Adapting them to other projects requires customizing placement rules and cross-reference patterns for your repository structure.