What problem does it solve? Affiliate articles on catsluvus.com render an "Our Top Picks" card where each product needs a consistent editorial blurb, but the AI writer can drift in structure, voice, and length without a documented standard. This Skill keeps the writer prompt in src/pipeline/writer.ts and the rendered HTML output in sync by codifying the exact blurb format. ## Core Features & Use Cases - Blurb Structure Spec: Enforces a three-sentence, 55-85 word format (feature sentence, tradeoff-plus-fit sentence, closing line) for every product pick. - Closing-Line Template: Mandates the literal prefix "Why we like this pick:" followed by a problem-benefit-buyer pattern of 15-30 words. - Voice and Failure-Mode Rules: Bans AI-slop vocabulary, em dashes, and keyword stuffing, and documents how to detect drift by grep-counting closing lines in published HTML. - Use Case: When tuning the Kimi K2.5 writer prompt or auditing published articles, apply this template so every pickReasons entry stays consistent across articles. ## Quick Start Ask the agent to audit the latest published article's product blurbs against the three-sentence structure and closing-line template defined in this skill.