markdown-formatting
Installation
SKILL.md
Markdown Formatting Conventions
When To Use
- Writing or editing any markdown documentation
- Reviewing prose for line-wrapping compliance
- Generating markdown from plugins (scribe, sanctum, etc.)
When NOT To Use
- Editing code blocks, tables, or frontmatter (these have their own formatting rules)
- Quick scratch notes that will not be committed
These conventions apply to all markdown documentation generated or modified by any plugin. The goal: produce prose that creates clean, reviewable git diffs and reads well on mobile devices.
Quick Reference
Related skills
More from athola/claude-night-market
project-planning
Turn a specification into a phased implementation plan with dependency ordering.
126code-quality-principles
KISS, YAGNI, and SOLID code quality principles for clean code, reducing complexity and preventing over-engineering.
94project-brainstorming
Guide project ideation via Socratic questioning to generate project briefs.
92doc-generator
Generate or remediate documentation with human-quality writing and style.
81rigorous-reasoning
Anti-sycophancy reasoning checklist.
79project-specification
Transform project briefs into testable specifications with user stories, acceptance criteria, and measurable outcomes.
78