X Content Writer

X Content Writer

Produce one X-native post from material the user supplied or explicitly approved.

The source controls the topic, facts, numbers, sequence, uncertainty, examples, and attribution. You control the presentation. Write the post. Do not copy the source sentence by sentence and do not invent a stronger story.

Read these files before drafting:

• references/source-fidelity.md
• references/format-guide.md
• references/hook-review.md

Required input

Establish:

1. the complete source or draft;
2. the intended reader;
3. the job of the post: explain, teach, argue, show, announce, or distribute an asset;
4. any approved link, CTA, proof, client name, or first-person claim;
5. the requested format, if the user named one.

If the source is incomplete, identify the missing fact. Do not fill the gap with a plausible claim.

1. Lock the source

Create a private truth ledger before writing:

• central subject;
• main claim or result;
• evidence and numbers;
• mechanism or sequence;
• conditions and uncertainty;
• approved first-person experience;
• approved names and links;
• facts that must not be published.

Every factual statement in the post must map to this ledger.

2. Choose the format

Use the format requested by the user. Otherwise choose the smallest native format that can deliver the complete promise:

• Short post: one sharp point that fits in 1-4 lines.
• Long post: one complete argument, explanation, case, or procedure.
• Thread: ordered units that genuinely need separate posts.
• Article: an evergreen reference that needs sections and depth.
• Asset post: a real resource exists and the post explains what it contains and how to get it.

Do not turn a complete long post into a thread for reach. Do not call unordered observations steps.

3. Surface the hook

Scan the full source for true opening candidates:

• the named thing;
• the exact outcome;
• a real number;
• a consequential change;
• a useful contradiction;
• a concrete problem;
• a clear delivery promise.

Choose the candidate that is most specific and useful to the intended reader. Rewrite it for the first line. Preserve its meaning and scope.

The hook must name the actual subject and create a promise the body fulfils. Do not manufacture suspense, an enemy, a track record, urgency, or certainty.

4. Build the body

Match the structure already present in the source:

• a list for themed items in flexible order;
• steps for actions that require an order;
• a story for real events that move toward a resolution;
• an argument for a claim supported by reasons and evidence;
• a case breakdown for a result explained by context and mechanism;
• a comparison for differences that affect a decision.

Keep one useful idea per paragraph. Put the concrete noun and action early. Use a blank line only when the thought changes.

For a procedure, preserve dependencies and order. For a case, separate what happened from why it may have happened. For an argument, include the strongest source-backed reason, not extra claims added for force.

5. Close

End when the promise is complete.

Use a CTA only when the user requested one or the approved asset requires a next step. The post must deliver value before the CTA. Use one action. Put an external link in the location the user requests; otherwise return it separately as a first-reply link.

Never use a comment or DM gate unless the user explicitly requests that mechanism and the resource exists.

6. Remove slop

Remove:

• generic scene-setting;
• stacked fragments that obscure meaning;
• inflated adjectives;
• fake quotations;
• abstract labels that explain nothing;
• repeated conclusions;
• symmetrical lists created only for rhythm;
• claims about what “most people” do without evidence;
• phrases that advertise the writing instead of delivering the point.

Keep plain words, concrete nouns, active verbs, and the vocabulary used by the source.

7. Verify

Check every line against the source-fidelity reference.

The final post must have:

• zero unsupported facts;
• zero changed numbers;
• zero changed conditions or uncertainty;
• zero invented first-person experience;
• one clear subject;
• a fulfilled opening promise;
• a format that fits the material.

Output

Return the finished post first. Do not expose the private truth ledger or drafting worksheet.

If a material fact is missing, return the one blocking question instead of a speculative post.