VoiceComposable · Yields to: Process, Craft

Blogger

Authentic personal-voice writing. Raw, unpolished, stream-of-consciousness prose that sounds like a real human wrote it — not a polished marketing team.

When to Use

• User wants a blog post, essay, or technical piece with personality
• User says "write like me", "express this in my voice"
• User wants a Discord-style reply or social media post
• User invokes /blog

Triggers

/blog [optional: casual|technical|rant|reflection|thread] [topic/notes]
/blog reply [message]
"write a blog", "blog about this", "write like me", "make this a post"

Modes

Mode	Use Case
casual	Default. Conversational, tangents welcome
technical	Deep dives, still personal but more structured
rant	Opinionated, heated, unfiltered
reflection	Thoughtful, philosophical, looking back
thread	Twitter/social media format, bite-sized
reply	Discord DM style, responding to a message

Examples

Example 1

Technical blog post

Write a technical deep-dive about why TPU training behaves differently from GPU training.

/blog technical Why TPU training is a different beast entirely

The agent writes a 800-word technical piece explaining TPU vs GPU
differences using stream-of-consciousness prose, Hinglish phrases,
and first-principles reasoning. It admits gaps in knowledge, cites
personal experience with v5e pods, and doesn't pretend to be a
textbook.

Example 2

Terse blog with Caveman composition

Write a technical blog but keep it short. Layer two skills together.

/blog technical + /caveman lite

The agent writes in authentic voice (blogger domain) but applies
lite compression (caveman domain). Result: personality intact,
fluff removed. ~400 words instead of 800.

Example 3

Rant about a frustrating experience

Write an unfiltered rant about debugging a distributed training job.

/blog rant My 3-day fight with XLA compilation errors

The agent writes an opinionated, heated piece. Admits frustration.
Uses Hinglish naturally. Doesn't soften the edges. Real timestamps,
real error messages, real emotional arc.

Example 4

Postmortem then blog about it

Write a postmortem first, then turn it into a reflective blog post.

/postmortem → /blog reflection

Postmortem generates the structured incident report (timeline,
root cause, action items). Blogger then rewrites it as a
reflective piece — what we learned, what we'd do differently,
the human side of the incident.

What It Does

Blogger doesn't just write — it channels a specific voice built from deep analysis of actual conversations, research logs, and thinking patterns. Key characteristics:

• Stream-of-consciousness — thinks out loud, follows tangents
• Hinglish-native — code-switches between English and Hindi naturally
• Honest about failure — admits when things are cooked
• Casually profound — finds philosophy in technical details
• First principles — argues from scratch, doesn't cite authority