microcopy-tone

Name: microcopy-tone
Availability: InStock
Author: concept2cure

Rewrite UI copy in a calm, factual regulatory tone.

1|Updated Nov 13, 2025

Search Tags:#audit #compliance #microcopy #copywriting #regulatory #tone-of-voice #ui-copy

Ready to run

npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill microcopy-tone

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: microcopy-tone
Source: https://github.com/concept2cure/ClinicalSageAI-2-replit/tree/main/.claude/skills/microcopy-tone
Command: npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill microcopy-tone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI copy often drifts into hedging, emotion, or informal language that can undermine regulatory credibility. This skill enforces a reviewer-grade tone that is calm, factual, and restrained across all user-facing text.

Core Features & Use Cases

Tone enforcement: Applies a strict calm, factual voice to all buttons, errors, toasts, empty states, confirmations, and help text.
Quality assurance & auditability: Provides guidelines and checklists to ensure no exclamations, hedging, emoji, or hedged phrases, and promotes active voice.
Use Case: Deliver regulator-ready copy for dashboards, forms, alerts, and tooltips, ensuring consistency across product surfaces.

Quick Start

Provide a UI string example and ask the AI to rewrite it in a calm, factual, restrained regulatory tone.

Frequently Asked Questions about microcopy-tone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write regulatory UI copy that passes compliance audits?▼

Regulatory UI copy requires a calm, factual tone that forbids exclamations, hedging, and emoji while using active present tense. This approach ensures buttons, errors, and help text meet strict compliance auditability standards.

What is the best way to rewrite error messages for compliance dashboards?▼

Rewriting error messages for compliance dashboards involves applying reviewer-grade guidelines that eliminate hedging and informal language. Use active present tense and explicit rationale to maintain regulatory clarity across all user interface text.

Can I use exclamations or emoji in user-facing text for regulated interfaces?▼

Exclamations, emoji, and hedging phrases are forbidden in regulated user-facing text. Enforcing a restrained, factual tone across UI strings ensures your copy remains regulator-ready and avoids undermining compliance credibility.

How do I ensure consistent tone of voice across web and mobile compliance alerts?▼

Consistent tone of voice across web and mobile compliance alerts is achieved by applying strict guidelines to all surfaces, including toasts and empty states. This enforces a factual, active voice without emotional or informal drift.

Why does my UI copy fail regulatory review for hedging language?▼

UI copy fails regulatory review when hedging language and informal phrasing undermine factual clarity. Reviewer-grade copy requires explicit rationale and active present tense to meet strict regulatory language guidelines without ambiguity.

Does this approach work for both mobile and web interface copywriting?▼

This copywriting approach applies to all user-facing text across both web and mobile interfaces. It enforces a calm, factual tone for buttons, confirmations, and tooltips to ensure consistent regulatory compliance.