AGENT SKILL

ux-copy

Generate UX microcopy in StyleSeed's Toss-inspired voice for buttons, empty states, errors, toasts, confirmations, and form guidance.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
ux-copy
risk
safe
tags
[ "ux", "copywriting", "microcopy", "frontend", "styleseed" ]
tools
[ "claude", "cursor", "codex", "gemini" ]
author
bitjaru
source
community
category
design
date_added
2026-04-08
description
Generate UX microcopy in StyleSeed's Toss-inspired voice for buttons, empty states, errors, toasts, confirmations, and form guidance.
source_repo
bitjaru/styleseed
source_type
community

03 SKILL.md 正文

UX Copy

Overview

Part of StyleSeed, this skill generates concise product copy for common UI states. It follows the Toss-inspired tone: casual but polite, direct, active, and specific enough to help the user recover or proceed.

When to Use

  • Use when you need button labels, helper text, toasts, empty states, or error messages
  • Use when a feature has functional UI but weak or robotic wording
  • Use when you want consistent product voice across a flow
  • Use when confirmation dialogs or state feedback need better phrasing

Tone Rules

  • casual but polite
  • active voice over passive voice
  • positive framing where it stays honest
  • plain language instead of internal jargon
  • concise wording where every word earns its place

Common Patterns

Buttons

Use a short action verb plus object when needed.

Empty States

Start with a friendly observation, then suggest the next action.

Errors

Explain what happened in user-facing language and what to do next. Do not surface raw internal error strings.

Toasts

Confirm the result quickly. Add an undo action for reversible destructive behavior.

Forms

Use clear labels, useful placeholders, specific helper text, and corrective error messages.

Confirmation Dialogs

State the action in plain language and explain the consequence if the decision is risky or irreversible.

Output

Return:

  1. The requested microcopy grouped by UI surface
  2. Notes on tone or localization considerations if relevant
  3. Any places where the UX likely needs a structural fix in addition to better copy

Best Practices

  • Make the next action obvious
  • Avoid generic labels like "Submit" or "OK" when the action can be named precisely
  • Blame the system, not the user, when something fails
  • Keep error and empty states useful even without visual context

Additional Resources

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1