github-pages-docs

GitHub Pages documentation is generated by creating Markdown files with Jekyll front matter that defines metadata, navigation structure, and layout. This Skill automates that process, producing publish-ready files with consistent formatting, hierarchical organization, and Jekyll configuration built in, eliminating manual setup and formatting inconsistencies.

Yes. This Skill synchronizes documentation with your codebase by embedding references to source code, error code standards, and domain models directly into generated Markdown files. This keeps technical accuracy high and gives developers immediate context without manual cross-linking.

Administrative how-to guides, ubiquitous language definitions, and Domain-Driven Design artifacts. The Skill generates consistently formatted guides for admin procedures, feature management, and complex domain terminology, all structured for immediate publication on GitHub Pages with Mermaid diagrams and hierarchical navigation included.

This Skill suggests a logical file organization structure and applies Jekyll front matter templates automatically, making your Markdown files instantly compatible with GitHub Pages. Files are organized hierarchically for intuitive navigation and ready to deploy to your `docs/` folder without additional configuration.

No. This Skill handles front matter templates, hierarchical navigation structure, and Jekyll metadata automatically. You provide the content intent—admin procedures, domain terms, or DDD artifacts—and receive complete, standards-compliant Markdown with all formatting and publishing configuration pre-applied.

DDD artifacts—ubiquitous language definitions, bounded contexts, and domain models—should be documented when building systems with complex business logic or multiple teams. This Skill generates DDD artifact documentation with consistent structure, ensuring shared terminology and architectural clarity across teams and reducing misalignment.