# How Do You Break Down a Viral X Post? Pull Out a Short Post's Structure and a Thread's Order, Then Write It Up in Chinese

> Once an X post is in your Beav knowledge base, click Decompose on it to get a topic, a structure template and the original text, with the topic also added to the topic center. Short posts mostly give you a topic and a structure. To learn how a thread unfolds, the suggestion here is to save and decompose its key posts one by one and compare them in a chat. Then drag them into a chat or use AI rewrite to write your own Chinese piece on the same structure, not a translation. What uses quota, and how it compares with reading notes and highlighting in a document.

- Source: https://getbeav.com/en/blog/features/x-twitter-breakdown-structure
- Author: JambaHailar (https://x.com/JambaHailar), Beav
- Published: 2026-11-20
- Last updated: 2026-11-20

> **Key takeaways**
>
> * Once an X post is in your knowledge base, open it and click **Decompose**. You get a topic, a structure template and the original text, and the topic is also added to the topic center. Short posts mostly give you a topic and a structure; shots and clips only appear when the post has a video saved locally.
> * There's no feature that saves a whole thread as one item. To learn how a thread unfolds, my suggestion is to save its key posts by their own links, decompose each, and compare them together in a chat.
> * To write in Chinese, drag the decomposed post into a chat or click **AI rewrite**. You're borrowing the structure and filling it with your own view and examples. Decomposition only starts when you click it and uses model quota.

A short post on X can be reshared tens of thousands of times without saying much. What carries it is usually how a few lines are ordered: open with a claim people want to argue with, give three reasons, end with one thing you can do today. Threads make it even clearer. Each post moves the argument one step, and readers keep scrolling.

When creators in China spot a great post, the first instinct is often to translate it and repost it. That raises permission problems, and it still reads like a translation. The thing worth taking home is the frame: how the angle is chosen, how the points are ordered, how it closes. Pull that frame out, keep it in your library, and reach for it the next time you write. That's the second step of building a material library.

## Who it is for

* Creators who follow industry voices on X and want to make original content for Chinese platforms.
* Writers of short opinion, career, product or startup pieces who want to learn how viral English posts arrange a handful of lines.
* Anyone collecting good posts over a few weeks who wants to compare which structures keep taking off.

## How to use it

![Three steps to turn a viral X post into your own Chinese piece: save it with Add link, click Decompose yourself to get a topic and structure template, then drag it into a chat or use AI rewrite to write on the same structure](https://getbeav.com/blog/features/x-twitter-breakdown-structure-steps-en.webp)

*Save it, decompose it yourself, learn the structure and make it yours.*

1. **Save the post first.*&#x2A; Click &#x2A;*+** next to **Knowledge Base**, choose **Add link** and paste the single post link. Account profiles can't be saved. Details are in [saving good posts from X](https://getbeav.com/en/blog/features/x-twitter-save-to-library).
2. **Open it and click Decompose.** To do several posts on the same topic at once, select them in the list, open the context menu and confirm the item count and model usage. A batch takes up to 100 items. Saving never starts a decomposition.
3. **Read the result.** Expand it to see a topic, a structure template and the original text, and the topic also shows up in the topic center. Shots, clips and music only appear when the post has a video that's already saved locally. The docs don't promise X videos get downloaded, so go by whether the entry actually has a video file. The result is also copied to `decompositions/<title>` in the asset library, and the origin panel keeps the post and its author.
4. **For a thread, save and decompose post by post.** The docs don't describe saving a whole thread in one go. My suggestion: pick the posts where the thread sets up, turns and lands, save each by its own link, decompose each, and keep them in one folder so the order stays clear.
5. **Drag it into a chat and write in Chinese.** With the chat input focused, press `⌘K` (`Ctrl+K` on Windows / Linux) to open the right sidebar, then drag the decomposed post from Knowledge onto the input box and say what your view is, who you're writing for and which platform. Or click **AI rewrite** at the top right of the item, add your requirements and send it yourself.

![Five things you have after breaking down an X post: topic, structure template and original text come from Decompose, shots and clips need a local video, and the thread order is this article's suggested method, each with how it feeds your Chinese piece](https://getbeav.com/blog/features/x-twitter-breakdown-structure-yields-en.webp)

*Illustration. Keep track of what came from Decompose and what's your own method.*

**Short posts: study the structure template.** The structure template from Decompose shows you what's holding the post up. Common ones are "counterintuitive claim plus three reasons", "open with one specific number" and "the failure first, then the fix". Check the original for how the first line hooks you, and write the frame down.

**Threads: compare the order.** Drag the posts you decomposed separately into one chat and ask: "In order, what step does each of these move forward? Which one is the turn?" What you're learning is how each post pushes the last one forward, not its wording. Here's a prompt you can adapt:

```text
These are the key posts from one thread, in the order I dragged them in.
First explain what role each plays in the thread, then use the same order
to write a RedNote image post for product managers in China. Use examples
Chinese readers know, and use my own point of view.
```

**Make it yours, not a translation.** The rewrite first explains how the original is organized, then proposes how the new piece maps onto it, and waits for your go-ahead by default. Data and examples in the original post belong to someone else and aren't your facts. Credit the source when you quote, and ask the author before republishing or publishing a translation. For more on what to keep and what to change in a rewrite, read [AI rewriting that isn't just swapping words](https://getbeav.com/en/blog/features/ai-rewrite-keep-structure).

**What uses quota?** Saving an X post with **Add link** goes through the capture service and uses quota by its rules. Decomposition uses model quota, and a batch asks you to confirm first. Chats and **AI rewrite** run on the chat model and use quota by the usual rules.

## How it compares with the usual ways

|                        | Reading notes by hand                                   | Pasting into a document and highlighting           | Beav Decompose plus a rewrite in chat                                   |
| ---------------------- | ------------------------------------------------------- | -------------------------------------------------- | ----------------------------------------------------------------------- |
| Strength               | Writing it out yourself gives the deepest understanding | The original right there to mark up, very flexible | Structure and original kept on one item, with the source                |
| What you get           | Your own notes                                          | A marked-up document                               | A topic (added to the topic center), a structure template, the original |
| Threads                | Copy them out in order                                  | Paste them in one by one                           | Save and decompose the key posts separately, compare them in one chat   |
| Writing your own piece | Flip back through your notes                            | Switch to another window                           | Drag them into a chat and have the AI write to your view and audience   |
| Cost                   | Free, but slow                                          | Free, but slow                                     | Capture quota to save, model quota to decompose and rewrite             |

If you really want to understand one post, taking notes by hand works best, and deciding which structure suits you is still your call. For the odd post you come across, a few highlights in a document is plenty. Beav fits the long game: posts, their structures and their sources stay in one library, you can compare them once you have enough, and the AI can use them directly when you write.

## Limits and notes

* **Decomposition is manual only.** Saving and phone submission never start one, and shared spaces don't offer Decompose.
* **Short posts mainly give a topic and a structure.** Shots, clips and music only appear when the post has a video saved locally.
* **Threads are handled post by post.** Saving a whole thread at once isn't a documented feature; save each post's own link as suggested here.
* **The structure template is model-generated.** Check it against the original before you rely on it.
* **Learn the structure, don't translate and repost.** Credit what you quote, and ask before republishing or publishing a translation. Beav never posts for you.

## Next steps

* To go all the way from saving and decomposing to drafts for several platforms, read [saving, breaking down and rewriting X posts](https://getbeav.com/en/blog/features/x-twitter-save-breakdown-rewrite).
* For managing the topics you pull out and starting on them, read [where content ideas should live](https://getbeav.com/en/blog/features/topic-pool). For why collecting matters at all, read the series overview, ["Accumulation Is the Moat"](https://getbeav.com/en/blog/features/accumulation-is-the-moat).
* Full reference: [decompose videos and notes](https://getbeav.com/en/docs/workflows/collect-to-create#decompose-videos-and-notes).

*Applies to Beav desktop 2.9 and later.*
