pm-uxwriting
v1.0.0UX writing & content design skills: Microcopy Writer, Error Message Writer, Empty State Writer, Product Naming, Content Style Guide, and Onboarding Copy. The small words that make a product clear, usable, and on-voice.
By Mohit AggarwalLicense: MIT1.4k GitHub starsUpdated 2 days ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 6 skill or MCP entries
- Source updated
- Oct 4, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install pm-uxwriting for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install pm-uxwriting@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/mohitagw15856/pm-claude-skillsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/pm-uxwriting/.
Plugin files
├── .claude-plugin/plugin.json├── skills/content-style-guide/SKILL.md├── skills/empty-state-writer/SKILL.md├── skills/error-message-writer/SKILL.md├── skills/microcopy-writer/SKILL.md├── skills/onboarding-copy/SKILL.md└── skills/product-naming/SKILL.md
Included Skills6
Create a content style guide / voice & tone guide so everyone writes consistently. Use when asked to write a content style guide, a voice and tone guide, editorial guidelines, or UX-writing standards. Produces a usable guide — voice principles with do/don't examples, tone-by-context, mechanics (grammar, capitalisation, formatting), terminology/word list, and accessibility/inclusivity rules — that a team can actually apply.
Write empty-state content that turns a blank screen into a next step. Use when asked to write an empty state, a zero-data / first-run state, a no-results state, or onboarding placeholder content. Produces empty-state copy — a clear headline, a helpful line, and a primary action — for each type (first-use, user-cleared, no-results, error/permission), so a blank screen guides instead of confuses.
Write clear, helpful error messages that tell users what happened and how to fix it. Use when asked to write an error message, validation text, a failure/empty-error state, or to rewrite a cryptic system error. Produces human, blame-free error copy — what went wrong, why (if useful), and the next step — with options per surface (inline, toast, full page) and the related success/empty states.
Write the small UI text that guides users — buttons, labels, tooltips, CTAs, confirmations. Use when asked to write microcopy, button/CTA text, form labels, tooltips, helper text, or to make UI wording clearer. Produces specific, action-oriented microcopy with options and rationale, matched to the moment and the product's voice — concise, scannable, and free of jargon.
Write in-product onboarding copy that gets users to value fast. Use when asked to write onboarding copy, a welcome flow, product tour/tooltips, setup steps, or activation messaging. Produces the copy for an onboarding flow — welcome, the guided steps/tooltips toward the first win, progress and empty-to-active nudges, and a success moment — focused on the activation outcome, not a feature tour.
Generate and evaluate names for a product, feature, or release. Use when asked to name a product/feature/company, brainstorm naming options, or choose between name candidates. Produces a shortlist of names across naming strategies, each with rationale, plus an evaluation against clear criteria (clarity, fit, memorability, availability checks to run) and a recommendation — not just a random list.
Plugin manifests1
{
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
"name": "pm-uxwriting",
"version": "1.0.0",
"description": "UX writing & content design skills: Microcopy Writer, Error Message Writer, Empty State Writer, Product Naming, Content Style Guide, and Onboarding Copy. The small words that make a product clear, usable, and on-voice.",
"author": {
"name": "Mohit Aggarwal",
"email": "[email protected]"
},
"homepage": "https://github.com/mohitagw15856/pm-claude-skills",
"license": "MIT",
"keywords": [
"ux-writing",
"content-design",
"microcopy",
"error-messages",
"empty-states",
"naming",
"style-guide",
"onboarding"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[pm-uxwriting on Agent Plugins Marketplace](https://pluginsmp.com/plugins/pm-uxwriting)