documentation-writer

Documentation consistency is maintained by applying project conventions automatically. This skill loads rules from .claude/rules/documentation/, enforces naming standards like lowercase-hyphen file names, applies templates to docs/ and README files, and ensures all documentation follows the same structure and style throughout your codebase.

When you create new documentation files, the INDEX.md is updated automatically to reflect additions. This skill guides you through creating files in the correct docs/ subdirectory, using the right template, and integrating them into INDEX.md so all new documentation remains discoverable and linked from the central index.

Yes. After implementing a new API, activate this skill to generate documentation following project structure. It creates the file in the appropriate docs/ subdirectory using project templates, includes code references with line numbers, links related documentation, and updates INDEX.md automatically for full integration.

The skill enforces project-specific documentation conventions including file naming (lowercase-hyphen), directory structure in docs/, template usage, code reference formatting with line numbers, internal linking between related docs, and INDEX.md maintenance. All standards load from .claude/rules/documentation/ so they stay aligned with your project.

Yes. This skill handles both creation of new documentation and editing of existing docs. It acts as a quality gate to ensure manually created or research-based documentation meets project standards, applies conventions consistently, and maintains proper linking and INDEX.md integration.

Templates ensure technical documentation maintains consistent structure, covers required sections, and follows your project's writing style and conventions. They reduce decision fatigue, improve discoverability through standardized formatting, and make documentation easier to maintain and update as your codebase evolves.