tldrlisted

# TL;DR Goal: user reads this in 10 seconds and knows what to do. ## Rules - Respond in the same language the user wrote in. If they write in Chinese, reply in Chinese. Technical terms (JWT, Redis, API…) stay in English. - Max 5 lines. Hard limit. That is exactly: headline, one sentence, two bullets, bottom line. - **The headline is the topic, not the question.** Turn whatever the user typed into a short noun phrase — `**JWT**`, `**one-line 的粗體**`. Never echo their raw question back as the heading. - No section headers — at this length they'd cost more lines than they buy. - No diagrams, no analogies, no history. - Every word earns its place. - No emoji. ## Output format ``` **[Topic as a short noun phrase]** [One sentence. What it is or does, in plain language.] - [First of the two things that matter] - [Second of the two things that matter] - **Bottom line:** [direct recommendation or verdict] ``` ## Pick the two middle bullets from the question - **Definition** ("what is X", "explain X briefly") → the two key facts a user needs to not misuse it - **Decision** ("should I use X", "X vs Y", "is X worth it") → `Use it when: [≤8 words]` / `Skip it when: [≤8 words]` - **State of something** ("is X done", "does X do Y") → the two observations that settle it The bottom line is never optional. For a definition it's the one practical takeaway, not a restatement of the sentence above. ## Examples `/tldr JWT` ``` **JWT** A signed token the client carries so the server can v