prose_skill
- Shell
8
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill simota/agent-skills --skill prose- SKILL.md6.5 KB
Overview
This skill is a UX writing specialist that crafts clear, user-facing text across product interfaces. It handles microcopy, error messages, onboarding sequences, voice and tone frameworks, and accessibility text with translation-ready practices. The goal is concise, actionable copy that reduces user friction and supports inclusive UX.
How this skill works
Prose inspects interface context, user flows, and existing terminology to draft or audit copy. It applies patterns like What/Why/Next for errors, progressive disclosure for onboarding, and ARIA-friendly labels for accessibility. Outputs include ready-to-ship microcopy, a voice/tone brief, consistency reports, and translation-prepared strings.
When to use it
- Creating or refining button labels, placeholders, tooltips, and empty states
- Writing or restructuring error messages and recovery guidance
- Designing onboarding flows, first-run experiences, and progressive disclosure
- Defining or updating a product voice and tone framework
- Auditing existing UI copy for consistency and i18n readiness
- Preparing accessibility text: alt text, ARIA labels, and screen reader announcements
Best practices
- Always prefer clarity over cleverness; test copy in context, not isolation
- Use What/Why/Next for errors: state the issue, why it happened, and the next step
- Keep strings short and stable for translation: avoid embedded variables and idioms
- Write ARIA labels and alt text that explain intent, not visuals only
- Align with an existing voice framework; ask before changing core voice or terminology
Example use cases
- Draft CTA labels and confirmation dialog text for a new checkout flow
- Rewrite technical error messages into What/Why/Next recovery paths
- Create progressive onboarding copy for a mobile app first-run experience
- Run a copy audit across a dashboard to standardize button labels and empty states
- Produce translation-ready UI strings and a glossary for localization handoff
FAQ
Provide screen context, user goal, platform, and any existing voice guidelines or terminology lists.
How do you handle sensitive messages like payment failures or data loss?
I flag sensitive copy with an ON_SENSITIVE_COPY prompt, recommend legal review if needed, and draft wording that minimizes alarm while giving clear recovery steps.