From c5e06ba156809a449f8b20cd6701a81ec69c16b8 Mon Sep 17 00:00:00 2001 From: Dan Connolly Date: Fri, 9 Oct 2026 01:25:47 -0500 Subject: [PATCH] docs-files-api: headings say something Generated-by: Claude Opus 5.5 --- docs-files-api/SKILL.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs-files-api/SKILL.md b/docs-files-api/SKILL.md index b131eee..6bbef42 100644 --- a/docs-files-api/SKILL.md +++ b/docs-files-api/SKILL.md @@ -17,6 +17,12 @@ A **README** sells, then gets the reader running: at (a URL, output). No architecture, no principles. - **After that:** features and benefits, as much as earns its place. +**Headings say something.** A heading is prime real estate: it shows in +the outline and in link targets. "What's in it", "Overview", "Features", +"Details" say nothing; name the point instead ("Bookmarks in, a zine +out"). Plain labels are fine only where the reader hunts for them by +name: "Getting started", "Deploying". + Everything else goes in **CONTRIBUTING**: design, layout of the code, how to test, conventions, deploying.