diff options
| -rw-r--r-- | prompts/skills/blog-writing-style/references/gemtext-conventions.md | 13 | ||||
| -rw-r--r-- | prompts/skills/compose-blog-post/SKILL.md | 2 |
2 files changed, 6 insertions, 9 deletions
diff --git a/prompts/skills/blog-writing-style/references/gemtext-conventions.md b/prompts/skills/blog-writing-style/references/gemtext-conventions.md index 6c2178c..dfb2ecf 100644 --- a/prompts/skills/blog-writing-style/references/gemtext-conventions.md +++ b/prompts/skills/blog-writing-style/references/gemtext-conventions.md @@ -28,7 +28,7 @@ italic (`*text*`). Gemtexter will not render these. Never use `**...**` or ## Post structure (in order) 1. `# Title` (first line) -2. `> Published at YYYY-MM-DDTHH:MM:SS+02:00` (ISO 8601 with timezone) +2. `> Published at YYYY-MM-DDTHH:MM:SS+02:00` (ISO 8601 with timezone) — **do not write this line manually**; Gemtexter inserts it automatically on `--generate` (using the file mtime) when it is missing. Leave it out of the `.gmi.tpl`. 3. Optional: ASCII art in a fenced code block (triple backticks) — only if it fits the topic (diagram, device, logo). 4. Short intro paragraph(s) @@ -41,14 +41,11 @@ italic (`*text*`). Gemtexter will not render these. Never use `**...**` or ## Table of Contents -Add a hand-written TOC after the intro/first image, before the first `##`: +Use the Gemtexter TOC macro — do **not** hand-write the TOC. Place this single line after the intro/first image, before the first `##` section: -- Heading: `## Table of Contents` then a blank line -- List with `* ⇢` and indentation by section level: - - `* ⇢ Post title` (one arrow = document title) - - `* ⇢ ⇢ Section name` (two arrows = each `##` section) - - `* ⇢ ⇢ ⇢ Subsection name` (three arrows = each `###` subsection) -- List every `##` and `###` in the same order as in the body. +`<< template::inline::toc` + +On `--generate`, Gemtexter expands it into the `## Table of Contents` heading plus `* ⇢` entries by section level (`#` → one arrow, `##` → two arrows, `###` → three arrows), skipping headings inside code blocks. Because it is generated from the headings, it never goes stale. ## Links diff --git a/prompts/skills/compose-blog-post/SKILL.md b/prompts/skills/compose-blog-post/SKILL.md index 0dd8367..9282f84 100644 --- a/prompts/skills/compose-blog-post/SKILL.md +++ b/prompts/skills/compose-blog-post/SKILL.md @@ -18,7 +18,7 @@ Compose a blog post in gemtext for the foo.zone gemfeed. **Only write or modify 2. **Decide filename and date.** Use `YYYY-MM-DD-slug.gmi.tpl` for the template file. Ask for the publish date and slug if the user doesn't specify them. -3. **Author the content following the foo.zone gemtext conventions.** All format/structure rules live in the shared [`blog-writing-style` gemtext conventions](../blog-writing-style/references/gemtext-conventions.md) — follow them for: post structure & order (`# Title`, `> Published at …`, intro, TOC, body, related posts, E-Mail line, back-to-main-site), Table of Contents (`⇢` arrows by section level), links (inline project links after the mentioning paragraph), images & ASCII diagrams (web resize, Unicode box-drawing, fixed-column `│` divider with an `awk` alignment check), multi-part series (cross-links, shared hero, `DRAFT-…` handling, dated-filename ordering), and format constraints (no Markdown bold/italic; `##`/`###` only; no HTML). +3. **Author the content following the foo.zone gemtext conventions.** All format/structure rules live in the shared [`blog-writing-style` gemtext conventions](../blog-writing-style/references/gemtext-conventions.md) — follow them for: post structure & order (`# Title`, intro, TOC, body, related posts, E-Mail line, back-to-main-site) — do NOT write the `> Published at …` line, Gemtexter inserts it automatically on `--generate` (using the file mtime) when it is missing; Table of Contents uses the `<< template::inline::toc` macro (Gemtexter expands it from the headings — never hand-write the `⇢` entries), links (inline project links after the mentioning paragraph), images & ASCII diagrams (web resize, Unicode box-drawing, fixed-column `│` divider with an `awk` alignment check), multi-part series (cross-links, shared hero, `DRAFT-…` handling, dated-filename ordering), and format constraints (no Markdown bold/italic; `##`/`###` only; no HTML). 4. **Ask when unclear.** If the topic, date, slug, or need for ASCII art / images / related posts is missing, ask the user before writing. |