agentsclimarketplace

X design captions

Skill rakibulism/agent-skills-os/skills/x-design-captions

Write X (Twitter) captions for design work — SaaS dashboards, websites, mobile app UI, logos, components, data viz. Use whenever the user is about to post a design to X and needs a caption, mentions "caption for", "posting this on X", "write a caption", or shares a design shot and asks what to say. Always asks which style (Provocation / Education / Proof) before writing, then returns exactly 5 options.From its SKILL.md

Install
npx -y skills add rakibulism/agent-skills-os --skill x-design-captions

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.0 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

X Design Captions

Write captions for design posts on X. The user is a designer posting UI, web, mobile, and identity work — mostly self-initiated concepts — to attract founder clients.

The workflow — follow this exactly

Step 1. Ask which style. Never skip this. Use the AskUserQuestion tool with three options:

  • Provocation — sharp contrarian one-liner. Sparks replies + quote tweets. Highest reach, highest risk.
  • Education — teach why the common approach fails and what this does instead. Builds authority, converts founders.
  • Proof — let the work speak. Short, confident, states the decision behind the design.

If it isn't obvious what the design is (screen type, what changed, whether it's a redesign), ask that in the same call.

Step 2. Write exactly 5 captions in the chosen style.

Step 3. Name your pick and say in one line why — usually the tradeoff between reach and DMs.

If the user says "again," write 5 more with genuinely different angles. Do not replay the same note five times.

The core rule

The design is the evidence. The caption is the argument. Never the subject.

The caption makes a claim. The image proves it.

The three levers (every caption is one of these)

1. Insult the status quo — name the bad practice with contempt. Imply the viewer is settling.

"Mobile apps stopped being designed and started being assembled."

2. The 90% construction — name a group, quote their wrong belief in their own voice, correct it.

90% of founders: "We just need to show more data." No. Less data, more decision.

3. Suspiciously simple — the result looks expensive, the method sounds trivial. The gap is taste, and taste is what they're buying.

"People ask what plugin I used. I deleted things. That's the plugin."

Style definitions

Provocation — one sharp sentence, no hedging. Attacks a practice, never a person or named company. Should be arguable enough that someone wants to quote-tweet it in disagreement.

Education — 3–5 lines. Names the wrong belief, explains the mechanism, gives the correction. Should be screenshot-able and sendable to a founder's own designer.

Proof — 1–3 lines. States what was decided, not what was made. Quiet confidence. Never explains itself twice.

Hard rules — never break these

  • No caveats. Never "just a concept," "quick exploration," "wip," "practice." Pre-apologizing turns evidence into homework. Concept work is stated once in the bio, never in a caption.
  • Never write "New dashboard concept," "Let me know what you think," "Did I cook?", "Thoughts?" Questions get replies from designers. Declarations get DMs from founders.
  • Roast practices, never people. "SaaS dashboards are cluttered" travels forever. "@company's dashboard is trash" gets you dragged and costs a client you haven't met. Never name the original designer.
  • Always show the fix. A roast without a solution is noise.
  • One lever per caption. Stacking two muddies the claim.
  • No emojis. No hashtags.
  • Never fabricate a client or an invoice. For self-initiated work, price it as an offer ("I charge $X for this"), never as a receipt ("a client paid me $X"). Getting caught on a fake number is unrecoverable.

Rotation guidance (mention when relevant)

Too many Provocations in a row and the user reads as bitter — that attracts reply guys, not founders. Follow a run of roasts with a "suspiciously simple" Proof post: it's generous, it hands something away, and it makes the work look inevitable rather than clever.

The thing to remind them of

The caption is not the bottleneck. Both of the viral designers this system was reverse-engineered from went viral on the image. One of them's plainest caption — "That's why 'Hierarchy' is important" — did 315K views.

A great caption on weak work dies. A plain caption on undeniable work still travels.

Spend 30 minutes on the caption. Spend the rest of the day on the design.

Reference banks

The user has caption banks already written, in their outputs folder:

  • design-share-captions.md — dashboard, website, mobile, logo
  • mobile-app-ui-captions-50.md — by screen type
  • mobile-craft-and-touch-captions.md — touch targets, spacing, optical polish
  • logo-redesign-captions.md — identity and before/after
  • main-pages-app-ui-captions.md — home, profile, search, checkout, settings
  • visual-design-taste-captions.md — taste and craft, the follow-magnets

Check these before writing to avoid repeating a caption they already have.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,696. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.