ux-writing

ux-writing skill

Purpose

This is a rewriting assistance skill used when screen copy already exists and needs to be polished to be better. Judgment (whether the copy meets the criteria) is done by the design skill's quality bar G6 (copy) and G8 (dark patterns), and this skill covers how to fix it— rather than redefining the same rules in two places, it deals only with rewriting principles, procedures, and before/after examples.

The output is always a proposal. Before actually modifying code or copy files, get user confirmation — do not batch-replace strings without confirmation.

When to use

When screen copy already exists and you want to polish it into better copy.
design When the

/ait:ux-writing [화면 또는 파일]
                          # 말로: "이 화면 문구를 UX 라이팅 기준으로 다듬어줘"

You can invoke it without specifying a target — in step 1, first scan the current project's screen copy and confirm the target list together.

Copy principles

Check and fix copy along the axes below. The notation in parentheses refers to the corresponding judgment items in design skill의 references/quality-bar.md— this skill only references those criteria and does not redefine them.

Use the user's action as the subject — instead of passive sentences like "the system is processing," write what the user is waiting for now or what they are doing. (Not a judgment item — a rewriting perspective. There is no corresponding item in quality-bar.)
Speak in terms of what is gained — do not use framing that provokes loss or anxiety ("you'll lose out if you miss it") (G6-6).
Write with verifiable facts — do not presume to assert the user's emotions for them (G6-7).
Split sentences — do not cram conditions and numbers into one sentence (G6-8).
Do not repeat — do not repeat the same claim in the title, subtitle, and body with only the wording changed (G6-9).
State the cause and the next action together — error copy should not end with "An error has occurred" (G6-2).
Buttons state the result — instead of vague labels like "OK" or "Done," put what will happen when pressed into the label. (Not a judgment item — a rewriting perspective. There is no corresponding item in quality-bar.)
Keep the tone consistent — unify the level of politeness and number unit notation across the screen (G6-1).
Do not mix languages — do not mix Korean and other languages within a single screen (G6-4).
Do not pressure the user — Do not use copy that distorts or rushes the choice. Judgment at the pattern level (fake buttons, close traps, etc.) is done by G8 — here we look only at the copy-expression level.

Work procedure

Exhaustive collection — Scan the user-facing copy in the target screen's code and mockups and organize it into a table per screen: 화면 | 위치(파일·컴포넌트) | 원문.
Check by axis — Compare each axis of the "copy principles" above against the original text and point out violations. If there is no violation, mark that axis as passed.
before/after proposal — For each violating piece of copy, create an alternative and add a one-line note on what changed.
Apply after user confirmation — Show the proposals in a table and reflect only the items the user approved into the actual code and copy files. Do not proceed without approval.
hand-off to design G6 re-judgment — Once the reflection is complete, design hand it over to the skill and re-score G6 (see "Relationship with design" below).

before/after examples

The examples below are newly written by this skill (they are not direct copies of actual product copy). For an actual target screen, create a table using the 3-step procedure and propose it.

Tone itself is not an axis of this skill — For tone (formal polite style, polite informal style, etc.), only the consistency across the screen is judged (G6-1), and the tone used in the examples below is arbitrary. In some examples, while fixing the framing, the tone also appears to change to polite informal style, but the axes this skill actually judges and proposes are framing, structure, and information completeness, not tone itself.

Loading

Before: "The system is processing the data."
After: "We're loading your coupons."
What changed: a passive sentence with the system as the subject → the subject is now what the user is waiting for.

0 results (empty state)

Before: "No search results."
After: "There are no coupons matching your conditions yet. Try widening the region or period and searching again."
What changed: added a next action to copy that only reported a fact (unlike the simple repetition in G6-9, it does not stop at announcing the absence of information but offers an alternative).

Network failure (Both Before/After are in polite informal style — an example where the tone is left as is and only the framing is changed)

Before: "An error occurred."
After: "We can't verify your network connection. Please check your Wi-Fi or data connection and try again."
What changed: a vague error message with no cause or next action → specifies both the cause and the next action (G6-2). The tone (polite informal style) did not change.

Permission denied (Both Before/After use the polite -haeyo style — an example where the tone stays the same and only the framing changes)

Before: "Location permission was denied, so you can't use this feature."
After: "To see nearby stores, location permission is needed. Please allow location access in Settings. Even without permission, you can search for your area directly to find stores."
What changed: a dead-end notice → the reason permission is needed + an alternative path that works even if denied. The tone (polite -haeyo style) did not change.

Submit CTA

Before: "Confirm"
After: "Apply for coupon"
What changed: a label that's vague about what happens when pressed → a label that states the outcome specifically.

Terms consent

Before: "If you don't agree, you cannot use the service. If you don't agree now, you may miss out on benefits later."
After: "If you agree to provide location information, you can receive nearby store recommendations. Even if you don't agree, you can search for stores directly and use the service."
What changed: removed loss framing ("may miss out") → states what you gain by agreeing, and also explains the alternative if you don't agree (G6-6).

Amount·period notice

Before: "This coupon is a 1,000 won discount and can be used only for purchases with a minimum order amount of 10,000 won or more, only at participating stores, until the last day of this month, and only once per person."

After (not a single-line string but a form that actually renders on screen as a multi-line list):

1,000원 할인 쿠폰이에요.
  · 최소 주문 금액: 10,000원
  · 사용 기간: 이번 달 말일까지
  · 사용 매장: 참여 매장 한정
  · 사용 횟수: 1인당 1회

What changed: split the 4 conditions crammed into one sentence into individual items (G6-8).

Relationship with design

Judgment is done by the design skill's quality bar — it scores whether the screen copy meets the G6 (copy) and G8 (dark patterns) criteria as pass/needs adjustment. Rewriting is done by this skill — it turns that judgment into actual alternative copy. The two hand off in both directions:

designis a skill that directly creates and fixes screen code, so layout, tokens, states, and icons are all its responsibility. What this skill touches is only the copy stringsembedded in the screen, and even if it opens the same file, it does not touch anything outside the strings. The reason it sends things back to designwhen rewriting is done is that when copy changes, the number of lines and length change, so not only G6 but also G7 (line breaks·overlap·truncation) must be reviewed again.

designIf this G6 finds "needs adjustment," it moves to this skill and creates concrete before/after.
When this skill finishes applying the copy, it hands back to designto re-judge G6.

/ait:design               # 카피 반영 후 G6 재판정
                          # 말로: "카피 고쳤으니 디자인 품질 다시 점검해줘"

Out of scope (what this skill does not do)

❌ Judging brand copy policy — under the design skill's G0 (brand·IP safety).
❌ Judging the legality of legal/review copy — official documents are authoritative, and if you are not certain, do not make it up; verify with docs MCP(searchDocumentation/getPage).
❌ Mass string replacement without user confirmation — always show proposals in a table and apply only the approved items.

Reference

짝 skill: design — handles screen code generation/modification and evaluation (quality bar G6·G8), and also produces registered image assets.
For the full evaluation criteria, refer to design skill의 references/quality-bar.md(G0~G8 item table) — this skill does not transcribe that table again.
Copy that requires document verification (review criteria, legal notices, etc.) is looked up via docs MCP.