{"id":21397,"plugin_id":"plugins_6aad979cf8348191812bd2ac0cce6181","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:16:54.038Z","digest":"739432417845df88ee75632e54442cbfdc24d831662fd173f5786aea6178f816","against":null,"payload":{"description":"Review and repair product-interface language and terminology across navigation, buttons, CTAs, forms, errors, recovery, empty states, onboarding, settings, status messages, AI warnings, and feature names. Use when the primary task is UX writing, microcopy, interface labels, product terminology consistency, or expectation-setting inside a product. Do not use for general prose humanization, brand/company/product-name creation, translation, or visual interface design.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":279}],"name":"review-interface-language-and-naming","skill_md_contents":"---\nname: review-interface-language-and-naming\ndescription: Review and repair product-interface language and terminology across navigation, buttons, CTAs, forms, errors, recovery, empty states, onboarding, settings, status messages, AI warnings, and feature names. Use when the primary task is UX writing, microcopy, interface labels, product terminology consistency, or expectation-setting inside a product. Do not use for general prose humanization, brand/company/product-name creation, translation, or visual interface design.\n---\n\n# Interface Language and Naming Review\n\nMake interface language clear, concise, natural, consistent, expectation-setting and recovery-oriented without changing approved product behavior.\n\n## Establish the language contract\n\n1. Inspect the actual interface strings with route, component, state, trigger and consequence. Identify product voice, audience, locale, terminology source, feature names, behavior and legal/compliance constraints.\n2. Separate approved product terminology from editable microcopy. Do not rename a product, feature, business concept or regulated term without the required authority.\n3. Apply the shared [Product Quality Principles](../../shared/expert-system/product-quality-principles.md): language must support purpose, agency, responsibility, familiarity, flexibility, simplicity, craft and appropriate delight.\n4. Mark missing behavior or unclear system truth as a specification gap. Copy cannot repair an interaction whose next step, failure state or consequence is undefined.\n\n## Review dimensions\n\nCheck as applicable:\n\n- navigation labels and information scent;\n- button/CTA labels that describe the resulting action rather than vague intent;\n- form labels, hints, validation, input expectations and accessible names;\n- errors that state what happened, avoid blame and provide a real next step;\n- recovery, retry, cancellation, undo and destructive-action language;\n- empty, loading, success, offline, timeout, permission and status states;\n- onboarding, settings and consent/permission explanations;\n- AI-system disclosure, uncertainty, refusal, fallback, source and consequential-action warnings;\n- feature/interface naming and enterprise terminology consistency;\n- brevity, grammar, tone, localization readiness, text expansion and device/input wording;\n- consistent terms for the same object, action and state across the journey.\n\nPreserve facts, approved claims, legal qualifiers, exact data effects and accessibility meaning. Do not add personality that makes risk, failure or destructive consequences less clear.\n\n## Routing boundary\n\n- General prose, emails, articles, marketing copy or personal voice → `$humanize-writing`.\n- New company, brand, product, service, project or channel name creation → `$create-distinctive-names`.\n- Visual/interaction design audit → `$audit-premium-digital-experience`.\n- Accessibility behavior audit beyond wording → `$audit-accessibility-and-inclusive-design`.\n\n## Output\n\nReturn scope and terminology authority, a compact issue table with string/location/state/problem/user risk/recommended replacement/rationale, a canonical terminology list, unresolved behavior or owner decisions, localization notes and final consistency check. If rewriting is authorized, lead with implementation-ready replacement strings; otherwise keep them explicitly proposed.\n\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}