Add a root EDITORIAL.md editorial charter for the blog and wire it into CLAUDE.md, english-correction, and adversarial-challenge (executes plan-006).
To give the blog a single human-readable editorial charter — house style, tone, front-matter contract, structure, and voice — separate from CLAUDE.md’s build/architecture layer, and to make it enforceable by wiring it into the existing skills: english-correction (voice + British-English, with the recent-post corpus remaining the live tone anchor) and adversarial-challenge (the post contract, defined as front-matter + opening thesis with no length component). Modelled on ../kaplus/EDITORIAL.md for form but rewritten for this Jekyll/Markdown, single-language, web-published site. This executes plan-006.
EDITORIAL.md (new — root editorial charter; not a Claude asset, listed for context)CLAUDE.md (Purpose section: pointer establishing EDITORIAL.md as the editorial layer, enforced by the two skills).claude/skills/english-correction/SKILL.md (Target section: references EDITORIAL.md §10/§11 as the human-readable voice/British-English description, with the recent-post corpus kept as the live anchor).claude/skills/adversarial-challenge/SKILL.md (§4.1 and §6: the post contract is defined by reference to EDITORIAL.md §5, with no length component per §4)plans/plan-006-editorial-guidelines.md, plans/README.md (plan execution bookkeeping — out of changelog scope, listed for context)create new plan to prepare an editorial guidelines for blog. it should ensure style, tone, and adhere to current expression in this blog. refer ../kaplus for example editorial.md