What problem does it solve? Writing a clear, well-structured editorial for a competitive programming problem is time-consuming: the solution must be derived step by step, restated without story lore, formatted as a self-contained HTML page, and kept consistent with the official statement, subtasks, and limits. This Skill automates that authoring process while enforcing editorial quality standards. ## Core Features & Use Cases - Derivation-first tutorial writing: Builds the solution as a continuous reasoning flow (observation, consequence, state, transition, correctness, complexity) rather than a compressed summary, with Observation and Lemma cards reserved for pivotal claims. - Themed standalone HTML output: Produces a single browser-openable editorial.html using one of three verbatim themes (space-dark, polygon-light, fb-light) with KaTeX rendering, meta blocks, tags, and optional whole-contest pages. - Bilingual and style control: Supports English or natural Vietnamese prose guided by a glossary (references/vi-glossary.md), calibrates explanation depth to problem difficulty, and strips AI writing patterns. - Use Case: After finishing a Polygon-ready problem package, ask for an editorial and receive editorial/editorial.html with a lore-stripped restatement, derived solution, difficulty estimate, CF-style tags, and time complexity. ## Quick Start Write the editorial HTML for the problem in the current directory using the default theme.
