---
name: x-create-visuals
description: Use when a user wants images, visual cards, diagrams, covers or a consistent visual style for an X.com/Twitter Post, Article or Thread, including image creation after a draft review and saving, reusing, importing or exporting visual preferences.
---

# Create X.com / Twitter visuals

For a new natural-language request, use `x-assistant` first when installed. If explicitly selected, delegated with `routed_by: x-assistant`, or installed alone, execute directly; do not route back. Respond in the user's language.

Read and execute [the visual workflow](references/visual-workflow.md). It contains the complete creation procedure and portable preference interface. Use [the knowledge guide](references/knowledge-guide.md) for algorithm claims; visual design advice is not evidence of a fixed exposure bonus.

1. Reuse the draft, existing assets and review's `visual_brief`. Specify each image's job and order; the first communicates the most useful supported message with essential conditions. Honor the user's stated purpose.
2. Discover the actual tools before offering production. Explicitly mention available native image generation. Check a preferred provider's availability today; a saved name is not an integration. Offer supplied assets, real screenshots, available AI or a useful mixture.
3. Read private saved preferences. On first use ask only for missing source/provider and style choices, and whether to remember them. On later use offer reuse, a temporary change or a new series style; an explicit choice needs no repeated confirmation. Never persist a temporary change.
4. Produce the requested visuals using available tools. Use real material for evidence and data rendering for exact charts. If production is unavailable, deliver a clearly labeled brief/prompts, not a false completion claim.
5. Inspect the result for text, numbers, source fidelity, order, first-image meaning and style consistency. Deliver actual artifacts and concise alt text; verify any agreed preference save separately. Do not publish automatically.

Preference operations can run alone when that is the user's whole request. Independent installation includes the helper and all necessary instructions; no sibling skill or particular image provider is required.
