markdown

Solid

Documentation and content creation standards

Data & Documents 73 stars 13 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
62
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

## Markdown Content Rules The following markdown content rules are enforced in the validators: 1. **Headings**: Use appropriate heading levels (H2, H3, etc.) to structure your content. Do not use an H1 heading, as this will be generated based on the title. 2. **Lists**: Use bullet points or numbered lists for lists. Ensure proper indentation and spacing. 3. **Code Blocks**: Use fenced code blocks for code snippets. Specify the language for syntax highlighting. 4. **Links**: Use proper markdown syntax for links. Ensure that links are valid and accessible. 5. **Images**: Use proper markdown syntax for images. Include alt text for accessibility. 6. **Tables**: Use markdown tables for tabular data. Ensure proper formatting and alignment. 7. **Line Length**: Limit line length to 400 characters for readability. 8. **Whitespace**: Use appropriate whitespace to separate sections and improve readability. 9. **Front Matter**: Include YAML front matter at the beginning of the file with required metadata fields. ## Formatting and Structure Follow these guidelines for formatting and structuring your markdown content: - **Headings**: Use `##` for H2 and `###` for H3. Ensure that headings are used in a hierarchical manner. Recommend restructuring if content includes H4, and more strongly recommend for H5. - **Lists**: Use `-` for bullet points and `1.` for numbered lists. Indent nested lists with two spaces. - **Code Blocks**: Use triple backticks (`) to create fenced code blocks. Spec...

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

Data & Documents Listed

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.

1 Updated today
virajp
Data & Documents Solid

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.

40 Updated today
arpitbbhayani
Data & Documents Listed

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.

0 Updated 1 months ago
BhangeeF16