dotfiles/claude-code/skills/md-syntax/SKILL.md
Guidelines for markdown syntax and formatting rules
npx skillsauth add jimweller/dotfiles md-syntaxInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
STARTER_CHARACTER = 📏
Follow these rules when creating or editing markdown files.
bash, yaml, json, text, hcl, go, etc. Never use bare ```##, ###, etc.) not **Bold** on its own line# Title at the top# Title/md-lint to format and lint after writing the fileAlways specify language
CORRECT with language
#!/bin/bash
INCORRECT without language
#!/bin/bash
INCORRECT bold as headding
**Status: Not Implemented**
Some description...
CORRECT use appropriate heading level
### Status
Not Implemented
Some description...
Always include a single trailing newline so the file ends in a blank line
INCORRECT no trailing newline
The End.
CORRECT trailing newline
The End.
Always add an empty line between different markdown styles like paragraphs, headings, lists, codeb blocks, block quotes etc
INCORRECT no empty line after headding
## Hello
There
CORRECT empty line after headding
## Hello
There
INCORRECT no empty line before list
Hello there
- thing 1
- thing 2
CORRECT empty line after headding
Hello there
- thing 1
- thing 2
testing
Search saved session transcripts for past decisions, actions, errors, and context that has left the current conversation window.
data-ai
Review a PRD for defects via Claude opus subagent.
development
Markdown authoring guidelines for formatting, code blocks, and structure. Use when writing or editing markdown files.
development
--- name: md-style description: README style guide for concise, direct documentation. Use when writing or editing README files. ß--- <!-- markdownlint-disable-file MD041 --> # README Style Guide Write concise, direct README files for experienced engineers. ## Principles - **No fluff** - Skip tables of contents, verbose explanations, development history - **No roadmaps** - Document current state only, not plans or decisions. Readme is an engineering specification. Not a project plan or chan