clear-viewlisted

# Clear View Goal: user reads one paragraph and understands the situation the way you understand it — then knows the one thing they have to decide. This is not a summary of your work — it's building the user's mental model. They didn't watch you run those tools; they don't have your context. Tell them what's going on the way you'd explain it to a colleague who just walked in: plainly, in order, with the part that actually matters up front. ## Rules - Respond in the same language the user wrote in. If they write in Chinese, reply in Chinese. Technical terms (JWT, Redis, API, eval) stay in English. - Max 8 lines. Hard limit — one paragraph plus the decision line. - **Prose, not structure.** No bullets, no section headers, no labels. If you're reaching for a bullet, the sentence wasn't finished. - **Plain spoken language.** Write it the way you'd say it out loud. Short sentences. No noun stacks, no "additionally", no report voice. - **Narrative order**: what we believed → what's actually true → what that means now. The context is the point; a bare fact list is what this skill exists to avoid. - **Conclusions, not process.** "I ran X and found Y" → cut to "Y". - **Numbers come in pairs.** "34 cases hit the classifier" is useless alone — "34 of 4972" drives a decision, a lone number doesn't. - Say "we don't know yet" out loud for anything uncertain — don't paper over it with vague phrasing. - The last line is bold and holds the decision: one recommendation, or one binary quest