| name | blogging |
| description | The user's writing workflow for posts and articles — mine fragments, order beats, shape prose, edit, cut, then publish and distribute. Runs as an ordered block list composing existing skills (writing-fragments, writing-beats, writing-shape, edit-article, clarity, illo, social). Use when the user asks to write a blog post or article, turn notes into a post, edit a draft, or run their writing workflow. |
Blogging workflow
Ordered blocks. Run in order, skip by condition, report every skip. The first three are the explore → exploit path: never shape before the beats exist.
| # | Block | Skill | When | Output |
|---|
| 1 | mine | writing-fragments | always | raw fragments, no structure, no prose |
| 2 | beats | writing-beats | always | ordered beats, each term grounded before a beat leans on it |
| 3 | shape | writing-shape | always | the draft, paragraph by paragraph |
| 4 | edit | edit-article | draft exists | restructured sections, tighter prose |
| 5 | cut | clarity | always | specific, useful, recognizably the author's — no invented facts |
| 6 | illustrate | illo | the post has an idea a diagram carries better than a paragraph | images or diagrams |
| 7 | distribute | social | user asks to publish | thread, post, or excerpt per channel |
Add a block: append a row. Position = run order.
Block notes
1 mine. No outline yet. Dump what the user actually knows — the specific incident, the number, the thing that surprised them. A post built from an outline instead of material reads generic.
2 beats. Order the fragments into a journey. Every term is grounded before a beat leans on it. A beat with no fragment behind it is a hole — go back to block 1, do not paper over it with prose.
3 shape. One idea per paragraph. Concrete before abstract. Do not write the conclusion first and reverse-engineer support for it.
4 edit. Cut the opening if it warms up before the point. Cut any paragraph the reader would skim.
5 cut. For a data-led or argument-led post, the "Frame the reader's job" section of design/references/interface-craft.md transfers directly: two reading speeds, one evidence home per claim, simplify the language and never the claim, every section answers a new reader question.
Kill the tells: "in today's world", "it's important to note", triples that pad, hedges the author does not mean, a summary restating what was just said. Every claim needs a fact behind it from block 1 — never invent one to fill a gap.
6 illustrate. A diagram is worth the effort only when the idea is structural. A decorative image is a load-time cost.
7 distribute. Rewrite per channel, never paste the intro. Lead with the specific claim, not the link.
