blog-write

Blog write

Target: pivoshenko.dev, posts at site/content/posts/*.mdx.

Goal = bespoke content. The post must contain things only the author could write — numbers, failures, decisions, opinions. Anything the first Google result could say -> delete. Padding is where slop comes from.

Modes

• write — idea/notes -> published MDX. Full flow (1-6).
• edit — existing draft -> improved. Map its headings into sections (step 3), confirm, then 4-6. Present per-section changes; never silently restructure.

Flow

1. Interrogate — raw material before prose

Never draft from a one-line idea. Mine the author first:

• what happened — the incident, the build, the decision
• specifics — numbers, commands, configs, error messages, dates
• the failure — what broke, what was tried and abandoned, what it cost
• the opinion — what they believe that others don't, and why

Source order: user > vault (06 WRITING draft, project/source notes) > repo. Never invent. No raw material for a section -> ask targeted questions, don't pad.

2. Thesis

One sentence the post defends. Reader finishes -> can repeat it back. No thesis -> no post, only notes. Say so and help find one.

3. Outline as dependency graph

Information = DAG. A section may only use concepts established by earlier sections.

• list sections; for each write the main point (a claim, not a heading)
• mark dependencies: section C leans on B's claim -> B comes first
• every section needs an edge to the thesis; no edge -> cut
• check: read points in order, circle any term/claim not yet introduced -> reorder or add setup

Confirm the outline with the user before drafting. Outline is cheap, drafts are not.

4. Draft, section by section

Load pivoshenko-brand/references/voice.md first (that skill's directory, not this one) — that file owns the voice. Non-negotiables from it:

• paragraphs 1-3 lines (~240 chars max); a paragraph that grows -> split
• rhythm: claim, claim, claim, beat
• first person singular; lowercase brand/tool names; posts never articles