markdown
SolidDocumentation and content creation standards
Install
Quality Score: 83/100
Skill Content
Details
- Author
- GulajavaMinistudio
- Repository
- GulajavaMinistudio/awesome-copilot-id
- Created
- 9 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
documentation-standards
Opinionated standards for writing and maintaining Markdown documentation — writing style, code blocks, tables, CHANGELOGs, and diagrams. Auto-applies when editing any Markdown file.
ape-style-markdown
Apply consistent, professional Markdown formatting rules whenever producing or reformatting Markdown output. Use this skill when generating any Markdown document, when the user asks to reformat or clean up existing Markdown, when producing README files, technical docs, notes, or any other content that will be rendered as Markdown. Trigger even when the request seems simple -- any Markdown output should follow these rules. Do not use this skill for non-Markdown outputs such as plain text, HTML, or code-only responses.
documentation-standards
Use whenever writing, reviewing, or restructuring a Markdown document in this knowledge base: choosing YAML front matter fields, a document type (STD, GUIDE, ADR, COMPETENCY, and so on), or a lifecycle status (Idea through Archived); naming a new file; deciding whether a design or feature doc needs a Mermaid sequenceDiagram or stateDiagram-v2 block and what that diagram must show; formatting cross-references, reference-style links, or anchors; writing or reviewing a table; or resolving which document canonically owns a topic. This is the cross-cutting documentation-formatting authority every stage skill (Design, Documentation, Implementation, and others) defers to for these rules rather than restating them — it is not itself a stage and does not gather requirements or write code.