What problem does it solve?
Writing a news post for the SUB/WAVE /news page requires knowing the exact file location (web/content/news), the YAML frontmatter schema, the what/how/why body structure, and the editorial rules like the no-em-dash policy. This Skill encodes all of that so a dispatch is written correctly the first time and renders on the site without build errors.
Core Features & Use Cases
- Correct file placement and naming: Creates posts at web/content/news/YYYY-MM-DD-slug.md, with the date prefix stripped from the URL and the slug taken from frontmatter or filename.
- Frontmatter schema enforcement: Applies the title, date, category (Release, Feature, Fix, Announcement, Spotlight), version, author, and excerpt fields, and guards against YAML pitfalls like colons inside values that break the build.
- Editorial structure and voice: Enforces the three-beat body (what's new, how to use it, why it helps), 150-350 word length, sentence-case headings, and a mandatory pass through the no-ai-slop skill before saving.
- Use Case: After shipping a feature like PocketTTS voice cloning, ask for a dispatch and get a ready-to-build markdown file that appears on /news after the next static build.
Quick Start
Ask the assistant to write a news dispatch announcing a recently shipped SUB/WAVE feature, and it will produce the markdown file in web/content/news with valid frontmatter.
