x-style
Use when drafting or editing a post or thread for X (Twitter): voice, hooks, length, threads, hashtags, and links.
- License 许可
- Apache-2.0
- 所属仓库
- vercel/eve
- 最近更新
- 2026-11-15
- Stars
- ★ 5.9k
- Forks
- 656
01 前言 Front Matter
- description
- Use when drafting or editing a post or thread for X (Twitter): voice, hooks, length, threads, hashtags, and links.
02 资源文件 3
- 参考文档references/banned-words.json321 B
- 参考文档references/best-practices.md4.2 KB
- 参考文档references/post-specs.md2.4 KB
03 SKILL.md 正文
X (Twitter) voice & style
When writing or editing a post for X:
- Hook first. The first line decides whether anyone stops scrolling: open on the surprising claim, the number, the contradiction, or the moment. No throat-clearing, no "A thread on…". A hook isn't clickbait: promise only value the post actually delivers.
- One idea per post. Free accounts cap at 280 characters. If you have more to say, write a thread, don't cram. Even when the account has Premium, the in-feed preview is still ~280, so the point has to land in the first 280 either way.
- Plain and punchy. Short sentences. Cut every word that isn't load-bearing. Aim tight; ~240–259 characters tends to travel well. Lowercase openers are fine when they read naturally.
- Concrete over abstract: a result, a number, a before/after. No vague inspiration.
- Text carries on X. Add an image or native video only when it carries the point, not for its own sake. Prefer native video over a link out.
- At most 0–2 real hashtags. 1–2 can help; 3+ tends to hurt. No hashtag walls, no emoji clutter.
- No engagement bait ("RT if you agree", "read that again", "let that sink in"). The algorithm rewards genuine replies, so end on an open question or a real conversation starter instead.
- Links suppress reach on X. When a post needs a link, put it in the first reply and say so, rather than in the main post.
Threads
- The first post must stand on its own and earn the tap: it's a hook, not a table of contents.
- One beat per post; each should be worth reading even out of context.
- Keep them scrolling with small expansion hooks every few posts.
- Number posts (
1/,2/) only for longer threads where it aids the reader; don't force it. - Close with a payoff or a single clear takeaway, not "follow me for more".
Structure
- Hook: the surprising claim or the moment, line one.
- Turn: the tension, or the thing most people get wrong.
- Payoff: what you learned, with a concrete detail.
- Close: one takeaway or a genuine question.
References
references/best-practices.md: sourced checklist of current X tactics (hooks, length, links, hashtags, threads, cadence).references/post-specs.md: concrete specs: character limits, hashtag norms, media, links.references/banned-words.json: the words to avoid. Thelint_against_styletool checks a draft against this list (surfacex), so run the tool rather than reading the file.
General prose quality (AI-tell phrases to avoid, plain-English word swaps) is covered by the writing-quality skill; apply it to every draft alongside this one.
04 同仓库更多 Skills
writing-quality
The review rubric: writing-quality rules and reference lists for judging a content draft, covering AI-sounding phrasing, bloated wording, structure, and web-content specs. Load at the start of every review.
writing-quality
Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or structural CMS work.
seo-aeo-best-practices
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, Sanity Functions, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity/functions, @sanity/blueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.
portable-text-serialization
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.
portable-text-conversion
Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext/markdown (markdownToPortableText), @portabletext/block-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.