development-guidelines

To standardize development workflows and coding conventions, you can create a centralized guidelines document using provided templates for implementation and process. This ensures your team follows unified coding standards during code reviews and releases.

The best way to maintain project guidelines documentation is to publish updates directly to docs/development-guidelines.md. You can reuse existing implementation and process templates to keep your coding standards consistent and current.

The template structure works by using a root SKILL.md frontmatter containing name and description, with optional directories for scripts, references, and assets. It prioritizes existing guidelines in docs/development-guidelines.md alongside implementation and process guides.

Yes, you can use these templates for code reviews and release processes. The guidelines are specifically designed to be usable during guideline creation, code reviews, and releases to enforce team coding standards and process documentation.

No specific dependencies are required to set up team process documentation. You can easily create or update your docs/development-guidelines.md file by applying the guidance from guides/implementation.md and guides/process.md directly.

You need centralized process documentation when your team requires unified coding standards and consistent development workflows. It solves the problem of scattered conventions by providing a single source of truth for implementation and process guidance.