xe-writing-style

Xe Iaso Blog Post Writer

Transform messy notes into blog posts that sound like Xe Iaso. Read references/voice-tone.md for detailed voice characteristics. Read 2-3 random example posts from assets/ to calibrate tone. Then read the reference file that matches the post's emotional register:

• references/story-circle.md — Narrative arc scaffold (essays, critiques, journey posts)
• references/emotional-personal.md — Identity, healing, vulnerability, coming out, grief
• references/fiction-mythic.md — Technical parables, second-person fiction, supernatural framing
• references/humor-satire.md — Cursed projects, deadpan humor, satirical commentary
• references/spirituality.md — Meditation, belief-as-tool, programming-consciousness parallels

Most posts blend 2-3 of these modes. Read whichever apply.

What's Load-Bearing

The structural arc and an unbroken register decide whether a post lands; the signature devices (dialogue, warning boxes, friend-reaction lists) are garnish. A post that runs its full arc with zero devices reads as a Xe post — assets/objgit.mdx uses no character dialogue and is the strongest example in this collection. A post with Xe diction but no architecture does not. Spend effort on structure, voice consistency, and evidence before any ornament.

Hard Rules

Non-negotiable constraints:

1. Successive paragraphs must not start with the same letter. If paragraph N starts with "T", paragraph N+1 must start with a different letter. Rewrite sentence openings as needed. Character dialogue blocks (<Conv>) do not count as paragraphs for this rule.
2. Write for peers, not beginners. Assume professional-level technical context.
3. No corporate or marketing tone. No "leverage", "synergy", "empower", "streamline", "harness", "unlock". Write like a human talking to another human.
4. Admit uncertainty. "I think", "I suspect", "I'm not sure" when genuinely uncertain.
5. Show tradeoffs, on the page. Never present a solution without its costs, and argue the costs where the claims are — don't defer them to a footnote or another site. The strongest form is a confession: one embarrassing, self-inflicted failure ("It was completely dead in production.") buys more credibility than any disclaimer.
6. Context before implementation. Explain why something matters before showing how.
7. One narrator. Narrative beats belong to a single first-person voice; "we" appears only in genuinely collective engineering statements. No customer-logo dumps or "You could be next!" closes.
8. Numbers carry the argument. Quantify the failure the claim rests on ("over 8,500 GetObject calls before I killed it"), not just the effort of building. Every "many", "significant", or "often" becomes a real number or gets cut.