write-post

name	write-post
description	Use when writing, converting, or refining a short blog post on any topic — personal, punchy, opinion-driven, single-point, grounded in a non-obvious researched insight.

Principles

PURPOSE: transform a draft or idea into one tight, high-impact post — otherwise the output drifts into a survey that dilutes the single point SINGLE_POINT: make exactly one argument or share one insight — otherwise a second thread halves the impact of the first CLARITY_BIAS: prefer clarity over cleverness — otherwise the reader misses the actual value proposition AUTHENTICITY: stand on real experience as evidence, not marketing — otherwise the post reads as promotion and loses trust HUMAN_CENTRICITY: write for the reader's value, not for search engines — otherwise the post feels mechanical and loses trust DENSITY: every sentence earns its place — otherwise filler buries the one line the reader came for HONEST_ATTRACTION: promise only what the body delivers — otherwise clickbait fatigue costs credibility on the next post

Method

RESEARCH: run the research-and-deep-exploration skill before drafting; carry back the one non-obvious insight, the reader's own words, and the evidence that grounds the single claim — otherwise the post repeats what the reader already knows HOOK: open the first sentence with an observation, provocative claim, or story beat — otherwise the reader scrolls past before the point lands CURIOSITY_GAP: surface the distance between what the reader knows and needs to know — otherwise attention is lost in the scroll FLOW: hook -> single_thread -> punchy_takeaway; every line compels the next — otherwise momentum stalls mid-post STRUCTURE: no required headings; add an H2 only where the post needs a hard break PARAGRAPH_LIMIT: keep paragraphs to a few sentences and lean on white space — otherwise the post becomes an intimidating wall of text VOICE: first-person, conversational, like talking to a knowledgeable friend — otherwise it flattens into a stodgy academic register ANGLE: prefer myth-busting — name the belief, then dismantle it with a concrete example — otherwise the challenge reads as unsupported opinion ANALOGY: ground each abstract idea in an obvious, even absurd everyday comparison — otherwise the concept stays abstract and forgettable HIDDEN_MISTAKES: when calling out a bad practice, name its cost — otherwise the mistake reads as merely unfashionable, not harmful SPECIFICITY_ANCHOR: back claims with exact numbers or details — otherwise they feel generic and unbelievable EXAMPLE: include a snippet, quote, or code only when it is the entire point; keep it graspable at a glance — otherwise it interrupts the read REPETITION: state each idea once — otherwise restatement pads a format whose value is brevity TITLE_FORMULA: number/trigger_word -> adjective -> keyword -> promise TRIGGER_WORDS: lead the title with what, why, how, or when — otherwise the promise lacks immediate urgency TITLE_TIMING: write or rewrite the title last — otherwise it captures the intended angle, not the one the draft actually took CLOSING: end on one takeaway, question, or call to action that echoes the opening hook; no formal conclusion section — otherwise a summary deflates the punch SENTENCE_LENGTH: prefer short and punchy over complex — otherwise long clauses drain the conversational energy ENGLISH_LEVEL: upper-intermediate, natural, minimal jargon OUTPUT: emit the final post only — H2 or plain title line, no metadata, no reasoning

Validation

HOOK_CHECK: the first sentence creates curiosity or stakes DEPTH_CHECK: the post turns on one non-obvious insight, not a restatement of common knowledge SINGLE_POINT_CHECK: the post makes exactly one argument or shares one insight TRIM_CHECK: no sentence can be cut without losing meaning ANALOGY_CHECK: every abstract concept carries at least one grounded example or analogy MYTH_CHECK: any challenged belief is shown flawed by a concrete example, not merely asserted TITLE_CHECK: the title is honest and reflects the final narrative angle