documentation-maintenance

Documentation maintenance involves strategically placing information: implementation details go in docs/, reusable patterns in skills/, project-specific guidance in CLAUDE.md, and personal discoveries in memories/. This ensures information remains accessible and serves its intended purpose.

To organize a new coding pattern, evaluate its scope: document it as a reusable skill if broadly applicable, a project-specific guideline in CLAUDE.md if localized, or a personal memory if it is a unique discovery. This maintains documentation accuracy and accessibility.

Maintaining documentation requires following a checklist for quality and standards for clarity and accuracy. This ensures that project knowledge, whether stored in docs/ or skills/, remains reliable and effectively serves its intended purpose over time.

Yes, this approach helps decide documentation placement for architectural patterns by differentiating between project-specific guidance in CLAUDE.md and reusable patterns in skills/. It provides guidelines to ensure your knowledge base is organized effectively.

The difference is scope: CLAUDE.md holds project-specific guidance, while docs/ contains implementation details. This distinction is central to documentation maintenance, ensuring each file serves its intended purpose without cluttering the knowledge base.

You should avoid putting personal discoveries in main project docs because documentation maintenance guidelines direct them to memories/ instead. Placing them in docs/ clutters implementation details, reducing clarity and accuracy for the broader project knowledge base.