[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0JC2VHSQS7QZR8PD7KQ8F":3,"skill-same:01M7F0JC2VHSQS7QZR8PD7KQ8F":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F0JC2VHSQS7QZR8PD7KQ8F","micro-copy-intelligence",null,"1000+ microcopy and UX-writing templates by component, tone and sector: button labels, every error message and failure state, empty states, tooltips, confirmations, permission requests and notifications. Use when writing any interface string — robotic copy is the loudest slop tell.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fmicro-copy-intelligence\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: micro-copy-intelligence\ndescription: \"1000+ microcopy and UX-writing templates by component, tone and sector: button labels, every error message and failure state, empty states, tooltips, confirmations, permission requests and notifications. Use when writing any interface string — robotic copy is the loudest slop tell.\"\nallowed-tools: Read, Grep, Glob\n---\n\n# Micro-Copy Intelligence\n\nCopy-paste-ready microcopy templates for every UI component and state, with tone variants, character counts, accessibility notes, and i18n notes. This skill owns all interface-string templates in design-ops.\n\n## Core Principle: Clear > Clever\n\nThe single most important rule in UX writing: **clarity beats cleverness every time**. Users are not reading your interface for entertainment. They are trying to accomplish a task. Every word should reduce cognitive load, not add to it.\n\n| Principle             | Description                                | Example                                                            |\n| --------------------- | ------------------------------------------ | ------------------------------------------------------------------ |\n| Clear > Clever        | Plain language over puns or jargon         | \"Save changes\" not \"Commit your brilliance\"                        |\n| Specific > Generic    | Tell them exactly what happens             | \"Delete 3 photos\" not \"Delete items\"                               |\n| Human > Robotic       | Write like a helpful person, not a machine | \"We couldn't find that page\" not \"Error 404: Resource not located\" |\n| Short > Long          | Every extra word is cognitive cost         | \"Saved\" not \"Your changes have been successfully saved\"            |\n| Active > Passive      | Direct the user with active voice          | \"Enter your email\" not \"Email should be entered\"                   |\n| Consistent > Creative | Same action = same word everywhere         | Always \"Remove\" or always \"Delete\", never both                     |\n| Helpful > Blaming     | Guide, don't accuse                        | \"That password is too short\" not \"You entered an invalid password\" |\n\n## Tone Adaptation by Context\n\nThe same product shifts tone based on what the user is experiencing:\n\n| Context                 | Tone Shift                 | Why                                                    |\n| ----------------------- | -------------------------- | ------------------------------------------------------ |\n| **Errors**              | Empathetic, calm, helpful  | User is frustrated — don't add to it                   |\n| **Success**             | Warm, affirming, brief     | User accomplished something — celebrate proportionally |\n| **Empty states**        | Encouraging, instructional | User sees nothing — guide them to value                |\n| **Destructive actions** | Cautious, specific, clear  | High stakes — no ambiguity allowed                     |\n| **Onboarding**          | Welcoming, motivating      | First impressions — build confidence                   |\n| **Loading\u002Fwaiting**     | Light, reassuring          | User is stuck — ease anxiety                           |\n| **Permission requests** | Transparent, benefit-led   | User must trust you — explain why                      |\n| **Pricing\u002Fpayment**     | Trustworthy, precise       | Money is involved — no vagueness                       |\n| **Legal\u002Fcompliance**    | Plain, clear, accessible   | Required info — make it readable                       |\n\n## The Microcopy Formula\n\nFor any UI element, apply this structure:\n\n```\n[Action Verb] + [Object] + [Benefit\u002FContext]\n```\n\n**Examples:**\n\n- \"Save changes\" = action + object\n- \"Upload photo to complete your profile\" = action + object + benefit\n- \"Delete this project permanently\" = action + object + context\n- \"Invite teammates to collaborate\" = action + object + benefit\n\n**When to add benefit\u002Fcontext:**\n\n- The action is unfamiliar (onboarding)\n- The action is irreversible (destructive)\n- The action requires trust (permissions, payments)\n- The action has a non-obvious outcome\n\n## Routing\n\n| Question | Read |\n| --- | --- |\n| Button, link or CTA label; choosing the verb (action verb matrix, pairing, char counts) | `references\u002Fbutton-label-templates.md` |\n| Something went wrong, or succeeded (validation, system, permission, business-logic errors; success copy; celebration proportionality) | `references\u002Ferror-success-messages.md` |\n| Nothing to show (first use, no results, cleared, error, no access) | `references\u002Fempty-state-copy.md` |\n| First launch, setup, feature tours, value proposition, permission priming and denial recovery | `references\u002Fonboarding-permission-copy.md` |\n| Push, in-app, toast, tooltip, helper text, confirmation dialogs, loading copy, changelog, placeholders, banners | `references\u002Fnotification-tooltip-copy.md` |\n| How to write a given component (structure rules for buttons, errors, empty states, confirmation severity tiers, placeholders, tooltips, onboarding, notification channel limits, success, loading by wait length) | `references\u002Fcomponent-copy-guidelines.md` |\n| Voice and tone calibration, sector tone guides, readability targets by component, inclusive language, i18n expansion, top-25 anti-patterns, step-by-step writing process | `references\u002Fvoice-tone-style.md` |\n\nFor a full screen, combine templates from several files, then filter them through the sector tone guide in `voice-tone-style.md`. For a copy audit, check against the principles below, the quality checklist, and the anti-pattern encyclopedia.\n\n## Quality Checklist for Any Microcopy\n\nBefore shipping any piece of UI text, verify:\n\n- [ ] Is it clear on first read? (No re-reading needed)\n- [ ] Is it specific? (User knows exactly what will happen)\n- [ ] Is it actionable? (User knows what to do next)\n- [ ] Is it consistent? (Same terms used across the product)\n- [ ] Is it concise? (No unnecessary words)\n- [ ] Is it inclusive? (No gendered, ableist, or culturally specific language)\n- [ ] Is it translatable? (No idioms, puns, concatenated strings)\n- [ ] Is it accessible? (Works with screen readers, announced properly)\n- [ ] Does it match the product voice? (Tone is appropriate for context)\n- [ ] Is it tested? (Real users understood it without explanation)\n\n## Accessibility Requirements for Microcopy\n\n- **ARIA live regions:** Error messages and success confirmations must be announced to screen readers via `aria-live=\"polite\"` (success) or `aria-live=\"assertive\"` (errors).\n- **Error association:** Every error message must be programmatically associated with its input via `aria-describedby`.\n- **Button labels:** If a button uses only an icon, provide `aria-label` with the full text label.\n- **Tooltip accessibility:** Tooltips must be reachable via keyboard (focus, not just hover) and announced by screen readers.\n- **Loading announcements:** Announce loading start and completion to screen readers.\n- **Confirmation dialogs:** Focus must move to the dialog when it opens and return to the trigger when it closes.\n- **Status messages:** Use `role=\"status\"` for non-critical updates and `role=\"alert\"` for urgent messages.\n- **No time pressure:** If a toast auto-dismisses, the information must be available elsewhere (notification center, status area).\n","# Micro-Copy Intelligence\n\nCopy-paste-ready microcopy templates for every UI component and state, with tone variants, character counts, accessibility notes, and i18n notes. This skill owns all interface-string templates in design-ops.\n\n## Core Principle: Clear > Clever\n\nThe single most important rule in UX writing: **clarity beats cleverness every time**. Users are not reading your interface for entertainment. They are trying to accomplish a task. Every word should reduce cognitive load, not add to it.\n\n| Principle             | Description                                | Example                                                            |\n| --------------------- | ------------------------------------------ | ------------------------------------------------------------------ |\n| Clear > Clever        | Plain language over puns or jargon         | \"Save changes\" not \"Commit your brilliance\"                        |\n| Specific > Generic    | Tell them exactly what happens             | \"Delete 3 photos\" not \"Delete items\"                               |\n| Human > Robotic       | Write like a helpful person, not a machine | \"We couldn't find that page\" not \"Error 404: Resource not located\" |\n| Short > Long          | Every extra word is cognitive cost         | \"Saved\" not \"Your changes have been successfully saved\"            |\n| Active > Passive      | Direct the user with active voice          | \"Enter your email\" not \"Email should be entered\"                   |\n| Consistent > Creative | Same action = same word everywhere         | Always \"Remove\" or always \"Delete\", never both                     |\n| Helpful > Blaming     | Guide, don't accuse                        | \"That password is too short\" not \"You entered an invalid password\" |\n\n## Tone Adaptation by Context\n\nThe same product shifts tone based on what the user is experiencing:\n\n| Context                 | Tone Shift                 | Why                                                    |\n| ----------------------- | -------------------------- | ------------------------------------------------------ |\n| **Errors**              | Empathetic, calm, helpful  | User is frustrated — don't add to it                   |\n| **Success**             | Warm, affirming, brief     | User accomplished something — celebrate proportionally |\n| **Empty states**        | Encouraging, instructional | User sees nothing — guide them to value                |\n| **Destructive actions** | Cautious, specific, clear  | High stakes — no ambiguity allowed                     |\n| **Onboarding**          | Welcoming, motivating      | First impressions — build confidence                   |\n| **Loading\u002Fwaiting**     | Light, reassuring          | User is stuck — ease anxiety                           |\n| **Permission requests** | Transparent, benefit-led   | User must trust you — explain why                      |\n| **Pricing\u002Fpayment**     | Trustworthy, precise       | Money is involved — no vagueness                       |\n| **Legal\u002Fcompliance**    | Plain, clear, accessible   | Required info — make it readable                       |\n\n## The Microcopy Formula\n\nFor any UI element, apply this structure:\n\n```\n[Action Verb] + [Object] + [Benefit\u002FContext]\n```\n\n**Examples:**\n\n- \"Save changes\" = action + object\n- \"Upload photo to complete your profile\" = action + object + benefit\n- \"Delete this project permanently\" = action + object + context\n- \"Invite teammates to collaborate\" = action + object + benefit\n\n**When to add benefit\u002Fcontext:**\n\n- The action is unfamiliar (onboarding)\n- The action is irreversible (destructive)\n- The action requires trust (permissions, payments)\n- The action has a non-obvious outcome\n\n## Routing\n\n| Question | Read |\n| --- | --- |\n| Button, link or CTA label; choosing the verb (action verb matrix, pairing, char counts) | `references\u002Fbutton-label-templates.md` |\n| Something went wrong, or succeeded (validation, system, permission, business-logic errors; success copy; celebration proportionality) | `references\u002Ferror-success-messages.md` |\n| Nothing to show (first use, no results, cleared, error, no access) | `references\u002Fempty-state-copy.md` |\n| First launch, setup, feature tours, value proposition, permission priming and denial recovery | `references\u002Fonboarding-permission-copy.md` |\n| Push, in-app, toast, tooltip, helper text, confirmation dialogs, loading copy, changelog, placeholders, banners | `references\u002Fnotification-tooltip-copy.md` |\n| How to write a given component (structure rules for buttons, errors, empty states, confirmation severity tiers, placeholders, tooltips, onboarding, notification channel limits, success, loading by wait length) | `references\u002Fcomponent-copy-guidelines.md` |\n| Voice and tone calibration, sector tone guides, readability targets by component, inclusive language, i18n expansion, top-25 anti-patterns, step-by-step writing process | `references\u002Fvoice-tone-style.md` |\n\nFor a full screen, combine templates from several files, then filter them through the sector tone guide in `voice-tone-style.md`. For a copy audit, check against the principles below, the quality checklist, and the anti-pattern encyclopedia.\n\n## Quality Checklist for Any Microcopy\n\nBefore shipping any piece of UI text, verify:\n\n- [ ] Is it clear on first read? (No re-reading needed)\n- [ ] Is it specific? (User knows exactly what will happen)\n- [ ] Is it actionable? (User knows what to do next)\n- [ ] Is it consistent? (Same terms used across the product)\n- [ ] Is it concise? (No unnecessary words)\n- [ ] Is it inclusive? (No gendered, ableist, or culturally specific language)\n- [ ] Is it translatable? (No idioms, puns, concatenated strings)\n- [ ] Is it accessible? (Works with screen readers, announced properly)\n- [ ] Does it match the product voice? (Tone is appropriate for context)\n- [ ] Is it tested? (Real users understood it without explanation)\n\n## Accessibility Requirements for Microcopy\n\n- **ARIA live regions:** Error messages and success confirmations must be announced to screen readers via `aria-live=\"polite\"` (success) or `aria-live=\"assertive\"` (errors).\n- **Error association:** Every error message must be programmatically associated with its input via `aria-describedby`.\n- **Button labels:** If a button uses only an icon, provide `aria-label` with the full text label.\n- **Tooltip accessibility:** Tooltips must be reachable via keyboard (focus, not just hover) and announced by screen readers.\n- **Loading announcements:** Announce loading start and completion to screen readers.\n- **Confirmation dialogs:** Focus must move to the dialog when it opens and return to the trigger when it closes.\n- **Status messages:** Use `role=\"status\"` for non-critical updates and `role=\"alert\"` for urgent messages.\n- **No time pressure:** If a toast auto-dismisses, the information must be available elsewhere (notification center, status area).\n",{"name":5,"description":7,"allowed-tools":24},"Read, Grep, Glob","main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fdesign-ops\u002Fskills\u002Fmicro-copy-intelligence","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill micro-copy-intelligence",{"tool":39,"command":40},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill micro-copy-intelligence",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill micro-copy-intelligence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fmicro-copy-intelligence\u002FSKILL.md",true,[47,53,57,61,65,69,73],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fbutton-label-templates.md","REFERENCE","参考文档",27027,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fmicro-copy-intelligence\u002Freferences\u002Fbutton-label-templates.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fcomponent-copy-guidelines.md",9468,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fmicro-copy-intelligence\u002Freferences\u002Fcomponent-copy-guidelines.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fempty-state-copy.md",25748,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fmicro-copy-intelligence\u002Freferences\u002Fempty-state-copy.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Ferror-success-messages.md",27929,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fmicro-copy-intelligence\u002Freferences\u002Ferror-success-messages.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fnotification-tooltip-copy.md",31824,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fmicro-copy-intelligence\u002Freferences\u002Fnotification-tooltip-copy.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fonboarding-permission-copy.md",26504,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fmicro-copy-intelligence\u002Freferences\u002Fonboarding-permission-copy.md",{"path":74,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fvoice-tone-style.md",20249,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdesign-ops\u002Fskills\u002Fmicro-copy-intelligence\u002Freferences\u002Fvoice-tone-style.md",[78,84,91,98,105,112],{"skillNo":79,"name":80,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]