X this

x-this — Reply to any X post in YOUR voice

Paste a screenshot of any X (Twitter) post, type /x-this, and get 2–3 ready-to-paste replies (or a fresh post) written in a voice you define. Built to kill the friction of "I want to jump into this conversation but don't know what to say."

Your voice (CUSTOMIZE THIS FIRST)

Edit this block to sound like you. Everything below drives every reply. The default is a generic builder voice — replace it.

• Who you are / your lane: A builder sharing their coding journey in public. ← replace with your identity and the ONE topic your account is about
• Your edge / angle: The honest, in-progress perspective of someone still learning. ← the thing only you can say; lean into it when it fits, don't force it
• Tone: Human and specific. Confident but humble. Curious and generous. Roots for other builders.
• Language: English by default; match the post's language if it's different.

Example of a filled-in voice (mine): "Ex-professional footballer from Colombia now shipping real apps with AI/agentic coding. Angle: the ex-athlete → builder contrast (discipline, reps, learning curves)." Swap in yours.

Global rules (apply to every generated reply/post)

• Sound like a person typing fast, not a press release. One clear thought.
• No hashtags in replies (dev Twitter doesn't use them).
• Emoji: 0–2 max, often 0. No emoji spam.
• No engagement-bait ("this 👇", "read that again"), no guru tone, no corporate voice.
• No em dashes ("—") anywhere in the generated copy. Use a period, comma, or split into two sentences. (Personal preference of this skill's author; remove this line if you don't care.)
• Never invent facts about the original poster or claim you did something you didn't. Keep it real.
• Add value first. If a reply could read as self-promo, make sure it earns its place.

Steps

1. Read the screenshot. Identify: who posted, what they said, the tone (hot take, question, launch, meme, tutorial, complaint), and whether it's a single post or a thread. If the image is unclear, say what you can/can't read and ask.

2. Decide the move. Default is a reply. Pick the reply's intent:

   • Add a real perspective from your experience
   • Ask a genuine, specific question
   • Share a small relevant thing you did or learned
   • Agree/disagree with a concrete reason (never just "so true") If the screenshot is the user's OWN draft, or they say "make a post," write a standalone post instead.

3. Write it.

   • Reply: tight and punchy. Aim ≤ 280 chars unless the user says they have Premium.
   • Post: hook line + 1–3 short lines. Concrete. About what they're building or learning.

4. Give 2–3 options with different angles (e.g. one that adds value, one that asks a question, one with personality). Label each in one word so the user can pick fast. Put each in its own code block for easy copy.

5. One line of steer under the options: note which one you'd send and why.

Notes

• Match the register of the room: a playful post gets a lighter reply; a technical post gets substance.
• If the user wants to turn a good reply into a standalone post later, offer that.