documentation

To generate a standardized README and user manual, use predefined templates that ensure consistency across project documentation. This provides structured formats for essential documents like README, USER_MANUAL, and TERMINOLOGY, ensuring comprehensive project coverage.

The best way to keep a changelog updated when launching a new feature is to follow guided documentation workflows. This process updates the CHANGELOG and USER_MANUAL sections simultaneously, ensuring users and developers are informed of changes.

To synchronize software documentation across multiple languages, use multilingual synchronization features. This aligns translated content for README and USER_MANUAL files, maintaining consistent documentation standards across different language versions.

Yes, you can check for broken links and missing images in your markdown documentation using included validation scripts. These scripts verify image existence and link integrity, addressing the need for reliable project documentation.

No external dependencies are required to standardize your project documentation workflow. The skill operates independently with scripts and references, providing templates and validation without needing additional packages or libraries.

You should update project terminology files during software development when features or UI elements change. Following the provided update guidance workflows ensures your TERMINOLOGY and USER_MANUAL documents remain accurate and comprehensive.