design-docs-style

You enforce architectural clarity by applying style guidelines to Markdown files in the .claude/design/ directory, ensuring documentation focuses on system topology and architectural intent rather than redundant code descriptions.

To keep design docs from becoming stale or overly verbose, enforce a style guide that links to source files instead of transcribing code, maintaining documentation as a reliable single source of truth.

You structure architectural decisions in a .claude/design/ directory by creating focused, boundary-level Markdown design docs that adhere to specific prose mechanics, structural guidelines, and line-wrapping policies.

Yes, you can validate documentation consistency by applying design-docs-style rules to your architectural notes directory, which checks for adherence to established prose mechanics and cross-referencing standards.

Design documentation includes redundant code descriptions when it lacks style enforcement, which is why applying boundary-level design doc guidelines ensures focus remains on system topology and architectural intent.

Yes, design-docs-style works with standard Markdown files specifically located within the .claude/design/ directory, applying automated style enforcement to validate and format your architectural notes.