product-design

To standardize project documentation structure, apply a frontmatter-driven spec to create or update docs/project.md, module requirements.md, design.md, and prototype HTML files. This ensures consistent documentation assets and team collaboration efficiency across all modules.

The standard directory layout for module design guidelines organizes files under docs/modules/<module>/, containing requirements.md, design.md, design-server.md, and prototype HTML files. A root docs/project.md file provides overarching project documentation context for all modules.

Yes, you can use this approach to update existing prototype HTML files and task lists. The specification applies to both creating and updating documentation assets, including <module>-task.md files, ensuring existing projects align with standardized template management and docs standards.

No, this documentation standard does not require any specific dependencies or frameworks. It operates independently using a frontmatter-driven spec defined in SKILL.md to enforce the required documentation files and directory structure without external components or tooling.

The best way to manage docs standards for new module onboarding is applying a unified template structure. This guarantees documentation is complete for review by standardizing requirements.md, design.md, and prototype files before the module goes live, improving team collaboration.