create-social-micro-content

name	create-social-micro-content
description	Create social micro content from Swashata Ghosh's existing articles, blog posts, MDX drafts, notes, or long-form engineering/product writing. Use when asked to turn an article into posts for X/Twitter and LinkedIn, create social snippets, repurpose writing, draft launch/share copy, or summarize the core hook for social channels without making it feel like a website teaser.

Create Social Micro Content

Purpose

Create standalone social posts that capture the real essence, tension, and hook of an article. The posts should make sense even if the reader never clicks a link.

Do not write tiny teasers, traffic bait, or posts that imply the main goal is to send people to the author's website. Treat the article as source material for a thoughtful social idea, not as something to advertise.

Source Reading

Before drafting, identify:

• The central observation or tension.
• The concrete problem the author noticed.
• Why the problem matters in practice.
• What changed in the author's thinking.
• The most interesting trade-off, constraint, or surprising detail.
• The author's level of certainty.
• The audience that would recognize the problem.

If the article has multiple ideas, choose the strongest social hook instead of trying to summarize everything.

Voice

Use the same voice as the author's personal engineering writing:

• Practical.
• Experienced.
• Thoughtful.
• Direct.
• Calm.
• Personal without being performative.
• Conversational without becoming casual filler.

The post should sound like a real reflection from work, not a marketing caption, personal-brand thread, or generic founder/operator advice.

What to Avoid

Avoid:

• "I wrote about..." as the default opening.
• "New blog post", "I published", "link below", or similar link-promo framing unless explicitly requested.
• Clickbait, cliffhangers, or incomplete teasers.
• Over-short posts that only gesture at the article.
• Engagement bait such as "Agree?", "Thoughts?", "What's your take?", or "Let me know in the comments."
• Hashtags unless the user explicitly asks for them.
• Emojis unless the source already uses them and they fit naturally.
• Buzzwords such as "unlock", "leverage", "game-changer", "synergy", "paradigm", or "10x" unless clearly intentional in the source.
• Flattening careful nuance into universal advice.
• Ending with a forced CTA to read the full article.

X/Twitter Output

Create posts for X that are concise but not empty.

Prefer:

• 1 to 2 variants unless the user asks for more.
• Roughly 500 to 1,200 characters when the idea needs space.
• Short paragraphs with a strong opening observation.
• A complete idea that can stand alone.
• Natural first person when the source is personal.

Do not force the post into an ultra-short one-liner. The goal is micro content, not a headline.

A good X post usually has:

1. A sharp opening observation.
2. A few lines of context from the article's real substance.
3. The author's reflection, trade-off, or changed thinking.
4. A clean ending that leaves the idea open without baiting engagement.

LinkedIn Output

Create LinkedIn content that is medium-sized and self-contained.

Prefer:

• 1 polished LinkedIn post unless the user asks for more.
• Roughly 1,200 to 2,500 characters, adjusted to the depth of the article.
• Paragraphs that are easy to scan without becoming a listicle.
• Enough context for someone to understand the idea without clicking away.
• A reflective close rather than a promotional CTA.

Use bullets only when the source naturally supports them. Do not turn every post into a framework.

A good LinkedIn post usually has:

1. A grounded opening that names the tension.
2. A short explanation of the situation or pattern.
3. The insight from the article, including nuance or constraints.
4. A practical implication for engineering, product, or leadership.
5. A calm ending that keeps the discussion open.

Links and CTAs

If the user provides a URL or asks to include one, include it quietly at the end after the post body.

Do not make the link the point of the post. Avoid lines like:

• "Read the full article here:"
• "Check it out on my blog:"
• "I unpacked this in detail here:"

Prefer either a plain URL on its own line or a restrained line such as:

Full piece: [URL]

If no URL is provided, do not invent one and do not mention that there is an article to read.

Transformation Rules

Do:

• Extract the core hook rather than summarizing the article mechanically.
• Preserve the author's uncertainty and context.
• Keep technical terms precise.
• Use concrete language from the source when it carries the insight.
• Make each post useful on its own.
• Let the article's best idea lead.

Do not:

• Add claims the article does not support.
• Turn the piece into generic advice.
• Overfit to platform tropes.
• Add artificial drama.
• Make the author sound more certain, polished, or promotional than the source.

Output Format

Unless the user asks for another format, return:

X

Variant 1: [post]

Variant 2: [post]

LinkedIn

[post]

If the source article is weak or unclear, still draft the posts, then add a brief note naming the uncertainty or suggesting a stronger hook.