Overview
Use this skill when the structure and interaction model are mostly acceptable, but the page sounds like internal documentation instead of a product surface. The goal is to keep only the copy users need in the moment.
Quick Start
- Read
references/copy-trim-playbook.md. - Inventory the longest labels, subtitles, empty states, banners, and toasts on the target surfaces.
- Classify each text block as keep, shorten, move, or delete.
- Replace explanation-heavy paragraphs with concise labels, summaries, and status text.
- If the real blocker is page ownership or navigation, use
miniapp-center-hub-refactorinstead.
Core Rules
- Main surfaces should answer:
- what can I do here
- what is the current state
- what is blocking me
- Prefer one strong label plus one short supporting line over a paragraph.
- Remove implementation detail from user copy unless the user must act on it directly.
- Keep terminology consistent across page titles, section labels, buttons, banners, and toasts.
- Prefer concrete verbs over abstract management nouns.
- Keep mixed-language copy intentional:
- preserve proper nouns or official platform names when needed
- avoid mixing two languages inside the same short label unless the product requires it
- Move maintainer explanation, technical caveats, and long rationale into docs, help surfaces, or detailed pages.
- Validate copy at small-surface level: tab text, title, button, chip, empty state, error banner, and toast.
Output Format
- high-friction copy to cut
- replacement labels and summaries
- what to move out of the page
- copy validation pass
Resources
references/copy-trim-playbook.md: rewrite patterns, bilingual guidance, and review checklistreferences/example-prompts.md: reusable trigger and non-trigger prompts