ss-copy
Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone
npx skills add bitjaru/styleseed --skill ss-copy --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# UX Microcopy Generator ## When NOT to use - For long-form content (blog posts, docs, marketing pages) — out of scope - For full feedback state design (not just text) → use `/ss-feedback` - For brand voice/tone definition itself — this skill consumes a voice spec, doesn't create it - For translations to non-English languages — single-language only Context: **$0** Description: $ARGUMENTS > **Read `engine/UX-WRITING.md` first** — it's the rule set this skill applies: buttons > name the action (not "Submit"), errors help instead of blame, empty states invite, > money copy stays calm, one term per concept. Korean/CJK projects: see §W8 for the > clear-calm-human "Toss feel" (존댓말 일관성, 사용자 관점 "내 계좌", 군더더기 빼기). ## Instructions 1. Read the design language reference: - `DESIGN-LANGUAGE.md` sections on Microcopy Tone Guide and UX Writing 2. Apply the voice principles: ### Tone Rules - **Casual but polite**: Friendly, not robotic. Like talking to a helpful friend. - **Active voice**: "We saved your changes" not "Your changes have been saved" - **Positive framing**: "Free shipping on orders over $30" not "Orders under $30 have shipping fees" - **Plain language**: "Send money" not "Initiate tra
- When NOT to use
- Instructions
- Tone Rules
- Copy Patterns by Context
What does the ss-copy skill do?
Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone
How do I install it?
Run `npx skills add bitjaru/styleseed --skill ss-copy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From bitjaru/styleseed, a repository with 867 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.