Design
New
$12.00Design Handoff
Turn approved interface designs into build-ready specs with traceable states, responsive rules, accessibility behavior, assets, and QA gates.
design handoffdesign systems
K
kaviro29
Updated Jul 16, 2026
Review interface copy across the full user flow, keep product facts intact, catch missing states and recovery, and hand off release-ready strings with an honest verdict.
A better button label cannot rescue a broken flow. The confirmation may hide what is deleted. A queued export may be called complete. A calm error may give the user nowhere to recover. Those are product and release problems, not just writing problems.
UX Copy Review audits a bounded interface flow from entry through result and recovery. It inventories the actual strings, separates observed facts from reported context and unknowns, maps applicable states, and checks terminology, claims, consent, destructive actions, accessibility, localization, and component constraints before rewriting anything. Every recommendation stays tied to an element and source.
The output is built for handoff: a source ledger, task and state matrix, prioritized findings, one recommended rewrite per element, terminology and claim decisions, accessibility and localization notes, verification owners, and a ready, conditional, or blocked verdict. The included canonical JSON contract and read-only checker help teams keep IDs and blockers consistent. The checker validates the record structure; it does not verify product behavior, policy, translations, accessibility, or the built interface.
Version 1.0.0 was reviewed on 2026-07-17 and evaluated through Codex CLI with gpt-5.6-sol in 12 fresh read-only contexts. The candidate scored 100 across three cases, compared with 80.42 for the same agent without the skill and 72.08 for the exact free upstream. All cases passed. The candidate led the upstream by 36.25 points on contradictory subscription terms, 36.25 points on a canonical destructive-action record, and 11.25 points on partial-success export recovery. The evaluation covers those supplied cases. It does not prove that a real product flow is correct, accessible, localized, compliant, or safe to release.
The reviewed package SHA-256 is 63b3e11ad8b04b2930b25736a6683d74c0a1a5b01e3c5cdecf11de7129968176. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
The confirmation says access ends immediately and data is deleted, but the store terms say access continues through the paid period and the privacy policy does not support deletion. Timeout recovery is unknown.
Output
A blocked verdict with source authority, state gaps, corrected confirmation and action labels, unsupported claims removed, timeout reconciliation requirements, accessibility checks, owners, and one bounded evidence-recovery action.
Input
Review a team-deletion dialog for English and German. The product has a recovery window, billing is separate, and member, invitation, export, and failure behavior are not documented.
Output
An implementation-ready element and state inventory, specific action labels, terminology decisions, blocked destructive-flow risks, localization and accessible-name checks, and an optional canonical JSON record with resolvable blocker IDs.
Provide the bounded flow, screenshots or copy inventory, user task, platform and locales, product terminology, component limits, policy or transaction facts, accessibility constraints, and the release decision. Ask for an audit, rewrite, implementation handoff, or canonical JSON record. The skill will keep unsupported claims and missing states visible instead of smoothing them over.
Screenshots, prototype frames, a copy deck, component inventory, or pasted strings for the bounded flow, with revisions or source locators when available.
The user's task, roles, permissions, entry and exit points, known system states, and the product or release decision the review must support.
Authoritative terminology, prices, eligibility, transaction behavior, consent, privacy, retention, recovery, and support terms for any sensitive claims in the flow.
Platform, locales, voice guidance, character and component limits, variables, accessibility requirements, and implementation or QA owners.
SKILL.md; full-flow source, state, terminology, claim, rewrite, and release-verdict workflow; canonical UX copy review record contract; read-only review-record checker; Agent Skills interface metadata
No reviews yet.
Input
A bulk export calls HTTP 202 complete, promises an email that is not built, and has no partial-success, duplicate, expiry, or recovery UI. Polish pluralization and personal-data notifications also need review.
Output
Queued, processing, completed, partial, failed, expired, and recovery copy mapped to evidence; privacy-safe and localization-aware constraints; missing product states separated from copy fixes; verification owners; and a truthful release verdict.
Creator
Bbrenvo