pipeline: EDITORIAL.md voice charter + fresh-eyes copy-edit stage
One written standard for every audience-facing word: concise, to the point, inspiring delight through specificity — with word budgets per copy type (reviews had drifted from a ~370-word median to 500-1000+). All writing skills now reference the charter, and daily-pipeline gains a stage-4 copy-edit pass: a subagent that didn't write the day's copy tightens it against the charter, prose only, diff reviewed before commit. Digest gains a copy-edit line. Claude-Session: https://claude.ai/code/session_01WZaczDJjL3xZ3u5spsN5AL
This commit is contained in:
@@ -63,7 +63,7 @@ Take the find's 2-3 sentence body and expand it to a full review:
|
||||
- 3-5 paragraphs covering: what it is, the specific problem it solves, the concrete details that make it earn its place, and any honest limitations (surfaced by step 3).
|
||||
- Reference the hero asset inline where it helps (relative `./hero.<ext>`; use `astro:assets` `<Image>` for JPG sources — plain Markdown images have rendered small on JPGs).
|
||||
- Don't pad. If the find body is already complete, the review is just it + a blockquote summary + maybe one paragraph on context.
|
||||
- Match the voice of existing reviews under `src/content/reviews/` — informative, concise, no sales tone.
|
||||
- Write to `EDITORIAL.md` (the voice charter): concise, to the point, delight through specificity. Budget: **250–450 words, hard ceiling 600** — narrative subjects (travel, history, story-led pieces) may earn up to ~800 when the story itself is the delight. Budgets are ceilings, not targets.
|
||||
|
||||
Interactive mode: show the proposed body and wait. Autonomous mode: proceed.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user