Create and modify markdown files with sysdoc repository conventions.
npx skills add https://github.com/sysdoc-rs/claude-skill-sysdoc --skill sysdoc-edit
Please help me install this Agent Skill. Skill: sysdoc-edit Source: https://github.com/sysdoc-rs/claude-skill-sysdoc/tree/main Command: npx skills add https://github.com/sysdoc-rs/claude-skill-sysdoc --skill sysdoc-edit
This Skill ensures your markdown files adhere to the strict conventions required by sysdoc repositories, preventing common errors and maintaining consistency.
XX.YY_title-slug.md).Use the sysdoc-edit skill to initialize a new Software Design Description document.
High-intent search queries and answers about installing and using this skill.
Formatting markdown for sysdoc repositories requires following specific conventions for file naming, using a single H1 per file, and maintaining clear section organization. This ensures structural consistency across technical documentation.
The correct file naming convention for sysdoc markdown sections uses a specific pattern like `XX.YY_title-slug.md`. Adhering to this naming structure ensures proper automated section numbering and hierarchical organization within the repository.
You should use H2 headings for subsections within the same file when content is tightly coupled, but create separate files when sections need distinct numbering or independent referencing. This distinction maintains document clarity and structural integrity.
Initializing a Software Design Description document involves setting up a single H1 per file and configuring the initial heading structure. This establishes the foundational hierarchy required for automated section numbering and sysdoc compliance.
Yes, sysdoc markdown validation requires automated section numbering to maintain structural consistency. Proper numbering relies on correct file naming conventions and appropriate parent section usage within the document hierarchy.
Markdown heading structure fails sysdoc validation when files contain multiple H1 tags or misuse H2 subsections instead of separate files. Correcting these structural violations enforces the required single H1 per file rule and restores formatting compliance.
mcj-coderAutomate project scaffolding with quality gates, CI/CD, and repository structure.
mvillmowFix code formatting in Mojo and Markdown files with automated tools.
revfactoryRead, parse, and convert HWP/HWPX documents to Markdown or other formats.
CallMeLuigiv2Enforce Rust naming, formatting, and lint conventions during code reviews.