Menu
Use when asked to write or improve UI text or microcopy - produces interface copy and states (empty, error, loading) from screen context, state and user action, scoped to the current scenario
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | ux-copywriting |
| description | Use when asked to write or improve UI text or microcopy - produces interface copy and states (empty, error, loading) from screen context, state and user action, scoped to the current scenario |
This is a standalone helper skill. It sits outside the SPP pipeline state machine — it does not read or write docs/spp/pipeline-state.md, and it is not a numbered phase or a phase checkpoint. It runs whenever asked, triggered by its own description, independent of any pipeline in progress.
UI text only works with context. "Write nice copy for the product" produces marketing filler — "unlock your dream career", "reach new heights". A working screen doesn't need that; a user landed there to finish a task, understand a status, or see why something failed. This skill asks for the screen, the state, and the user's action first, and writes text that answers that specific situation.
Before writing any copy, gather:
If any of the three is missing, ask for it rather than guessing — a plausible-sounding generic text is worse than no text.
List which states actually apply to this screen. Not every screen needs every state — a synchronous local-storage save has no meaningful loading state; a read-only view has no destructive-action warning. Don't invent states nothing in the scenario needs.
For each state that applies, write text that:
Reject and rewrite any candidate that:
This is a copy pass for the current scenario, not a content or IA project:
Use when specs are approved (phase 4 approved in docs/spp/pipeline-state.md) OR when the user directly asks to turn a spec into an implementation plan outside a running pipeline (e.g. "turn this spec into an implementation plan") - writes implementation plans as bite-sized tasks to docs/spp/05-plans/ for subagent-driven execution
Use after completing a task or major feature, before merging, or when the user asks to review a branch, PR, or work-in-progress diff. Run independent Standards and Spec reviews so clean code cannot hide the wrong behavior and correct behavior cannot hide broken standards.
Diagnose bugs, test failures, build failures, unexpected behavior, and performance regressions before proposing fixes. Build a tight reproduction loop, find the root cause, fix it once, and lock it down with a regression test.
Use when implementing any feature or bugfix, before writing implementation code
Use when starting any conversation - routes each request to a single SPP skill by default, running the full idea-to-deploy pipeline only when the user explicitly asks for "pipeline"
Use when a product is ready to ship, OR when the user directly asks how or where to deploy or to write a deploy runbook - chooses a deploy strategy with the owner in cost-and-consequence terms, then executes it into a repeatable runbook. Self-checks on disk for a fixed release version first — it warns and offers to fix it, it does not block.
