create-doc

To enforce consistent documentation structure, apply a standardized template with mandatory frontmatter and section compliance rules. This ensures all technical contracts and usage guides maintain uniform structure across supported platforms.

Preventing documentation drift requires built-in validation scripts that catch missing fields, placeholder content, and path mismatches before finalizing docs. This approach eliminates unindexed long-lived documentation and maintains repo standards.

To sync new usage guides to a central knowledge index, automatically synchronize document metadata to the central KNOWLEDGE.md index when creating or updating docs. This makes governed docs easily discoverable by agent platforms.

Yes, this documentation validation approach works with React Native, Flutter, and UniApp workflows. It governs technical contracts and usage guides specifically tailored for these supported hybrid platforms within the repository.

To validate mandatory sections and frontmatter, run built-in validation scripts that detect non-compliant structures and missing fields before docs are finalized. This ensures all documents satisfy template-backed structural requirements.

Agent platforms fail to discover workflow documentation when docs are unindexed and lack synchronized metadata. Automatically updating the central knowledge index with new document metadata ensures platforms like Claude Code and Cursor can find them.