markdown-standardslisted

# Markdown Standards Fabrizio's standing conventions for authoring Markdown — the **semantic** half of the Markdown validation standard. The **mechanical** half is CI: his repos adopt the reusable `markdown-lint.yml` (markdownlint-cli2) and `markdown-links.yml` (lychee internal link/anchor check + scheduled external-URL sweep) workflows from [`flungo/github-workflows`](https://github.com/flungo/github-workflows) — see its [`docs/reference/markdown-validation.md`](https://github.com/flungo/github-workflows/blob/main/docs/reference/markdown-validation.md). The tools verify that links resolve and style rules hold; this skill covers what they cannot — that references are unambiguous and correctly qualified, that prose follows the conventions the lint rules are configured around, and how to fix the failures the tools raise. Apply these in any repo of Fabrizio's whenever you touch Markdown, whether or not that repo has adopted the CI. **These conventions complement repo/context rules, they never supersede them** — where a repo's `CLAUDE.md`/`CONTRIBUTING.md` specifies something different, follow the repo. ## The reference files Read the relevant reference before doing the work: - **`references/cross-references.md`** — the cross-reference rules: unambiguous link text (never a bare identifier, never "here"), prefix labels, same-repo-implied vs cross-repo-explicit qualification, anchor disambiguation, relative-vs-full links, updating references on rename, and how to fix internal