system-documentation

To document new code systems, you create a SKILL.md file using a structured template. This ensures comprehensive documentation of the system's purpose, components, and usage, preventing knowledge silos and improving maintainability for other developers.

You should update existing developer guides when code systems are refactored or extended. Regular maintenance of SKILL.md files is mandated to reflect system evolution, ensuring architectural patterns and reusable components remain accurately documented.

The best way to document architectural patterns is by adhering to a structured documentation template within a SKILL.md file. This approach applies to the development lifecycle of reusable components, ensuring major code systems have comprehensive documentation.

Yes, this documentation approach works for complex authentication modules. When a new authentication module is developed, creating a SKILL.md file ensures its purpose, components, and usage are explained to other developers, improving overall system maintainability.

Yes, you can use SKILL.md files for maintaining existing user profile management systems. The process mandates updating documentation when existing systems are extended, ensuring the system evolution is reflected for ongoing developer use.

A limitation of using a structured documentation template is that it requires regular maintenance to reflect system evolution. Without consistent updates during refactoring or extension, the SKILL.md file may become outdated, reducing its effectiveness for developer guides.