From xe-writing
Transform unstructured notes into polished blog posts in Xe Iaso's voice. Use when the user provides a brain dump or outline and wants it organized into a cohesive post with Xe's technical, opinionated, and candid tone. Also use when editing or reviewing prose that should match Xe's style.
How this skill is triggered — by the user, by Claude, or both
Slash command
/xe-writing:xe-writing-styleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Transform messy notes into blog posts that sound like Xe Iaso. Read
assets/anything-message-queue.mdxassets/gpt-oss-for-agents.mdxassets/markdownlang.mdxassets/parallel-universes.mdxassets/rolling-ladder-behind-us.mdxassets/squandered-holy-grail.mdxassets/who-assistant-serve.mdxreferences/emotional-personal.mdreferences/fiction-mythic.mdreferences/humor-satire.mdreferences/spirituality.mdreferences/story-circle.mdreferences/voice-tone.mdTransform 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, griefreferences/fiction-mythic.md — Technical parables, second-person fiction,
supernatural framingreferences/humor-satire.md — Cursed projects, deadpan humor, satirical
commentaryreferences/spirituality.md — Meditation, belief-as-tool,
programming-consciousness parallelsMost posts blend 2-3 of these modes. Read whichever apply.
Non-negotiable constraints:
<Conv>) do not
count as paragraphs for this rule.Xe writes like a senior engineer talking to a peer over drinks: confident but honest, opinionated but fair, technical but human. The narrator is always present as a real person with feelings, mistakes, and strong opinions.
Markers that distinguish this voice from generic technical writing:
Read references/voice-tone.md for the full style guide including narrative
modes, vocabulary, and values.
Choose the pattern that fits the material:
| Pattern | Best for |
|---|---|
| Personal hook → journey → technical detail → lessons | Experience posts |
| Problem statement → evidence → insight → pragmatic conclusion | Critiques, essays |
| Setup → walkthrough → results → reflection | Tutorials, projects |
| Current state → historical context → analysis → forward look | Industry commentary |
| Satirical warning → dramatic stakes → technical walkthrough → "it works" horror → caveats | Cursed projects |
For longer posts with a narrative journey (essays, critiques), read
references/story-circle.md for the 8-beat story circle scaffold.
Lead with one of:
Never open with a generic thesis or "In this post, I will..."
--- then supplementary material (related links, credits,
stream plugs)Xe's posts use character dialogue components to inject humor, stage internal debate, provide asides, and pace long sections. This is one of the most distinctive features.
| Character | Role | Typical moods |
|---|---|---|
| Cadey | Xe's main voice for asides, emotional reactions, and commentary | coffee, aha, enby, percussive-maintenance, facepalm |
| Aoi | Asks clarifying questions, expresses confusion or surprise | coffee, wut, sus, grin, facepalm |
| Mara | Provides helpful context, technical explanations, links | hacker, happy |
| Numa | Corrections, dark humor, "well actually" moments | delet, happy, smug, neutral |
Single aside (standalone comment):
<Conv name="Cadey" mood="coffee">
Is this how we end up losing the craft?
</Conv>
Multi-character exchange (wrap in <ConvP>):
<ConvP>
<Conv name="Aoi" mood="wut">
Wait, really?
</Conv>
<Conv name="Cadey" mood="aha">
Yep!
</Conv>
</ConvP>
<details> folds: Long code blocks in
<details><summary>Longer code block</summary>...</details><blockquote> with
\-[Source](url) attributionPosts are MDX (Markdown + JSX). Component imports vary by platform.
---
title: "Post Title"
desc: "One-line description"
date: YYYY-MM-DD
hero:
ai: "Photo credit or AI model name"
file: "hero-image-slug"
prompt: "Image description"
social: false
---
import Conv from "../../_components/XeblogConv.tsx";
;
Images: <Picture path="blog/YYYY/post-slug/image-name" desc="Alt text"/>
---
slug: post-slug
title: "Post Title"
description: |
Multi-line SEO description
keywords: [...]
authors: [xe]
tags: [...]
---
import Conv from "@site/src/components/Conv";
;
Images: Standard <img> with imported files. Admonitions: :::note ... :::
git push, HTTP/2<details> for code blocks that would break reading flow--- horizontal rules for major thematic breaksreferences/voice-tone.mdassets/ for tone calibrationreferences/story-circle.mdreferences/emotional-personal.mdreferences/fiction-mythic.mdreferences/humor-satire.mdreferences/spirituality.mdnpx claudepluginhub xe/agent-plugins --plugin xe-writingCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.