Ux Writing

Community

cgallic

ux-writing

Create user-centered, accessible interface copy (microcopy) for digital products including buttons, labels, error messages, notifications, forms, onboarding, empty states, success messages, and help text. Use when writing or editing any text that appears in apps, websites, or software interfaces, designing conversational flows, establishing voice and tone guidelines, auditing product content for consistency and usability, reviewing UI strings, or improving existing interface copy. Applies UX writing best practices based on four quality standards — purposeful, concise, conversational, and clear. Includes accessibility guidelines, research-backed benchmarks (sentence length, comprehension rates, reading levels), expanded error patterns, tone adaptation frameworks, and comprehensive reference materials.

Overview

Publisher	cgallic
Repository	`kai-cmo-harness`
Skill name	`ux-writing`
Stars	61
Forks	8
Bundled files	11
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
11 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by cgallic on GitHub. Read the source before you install it.

Installation

Install the Ux Writing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/cgallic/kai-cmo-harness/tree/main/harness/skills-v2/ux-writing
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/cgallic/kai-cmo-harness.git /tmp/kai-cmo-harness
mkdir -p .claude/skills
cp -r /tmp/kai-cmo-harness/harness/skills-v2/ux-writing .claude/skills/ux-writing

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ux Writing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ux Writing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ux Writing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

ux-writing (v2, goal-oriented)

Third-party skill (content-designer/ux-writing-skill, MIT; see UPSTREAM.md and LICENSE). The complete, unmodified rule set is references/ux-writing-rules.md in this folder. This file states the goal and the binding constraints; every rule in the reference still applies. Paths that the rules mention (references/, templates/, examples/, docs/) are relative to this skill folder.

Objective

Ship interface copy (buttons, labels, errors, notifications, forms, onboarding, empty states, success messages, help text) that is purposeful, concise, conversational and clear, matches the product's voice, and works for every user, including screen-reader users.

Done when

The context is written down before drafting: the user goal, the business goal, technical constraints (character limits, components) and the user's likely emotional state and stakes.
Every string follows its pattern from the rules: buttons as [Verb] [object], errors as [What failed]. [Why]. [What to do]., success as [Action] [result], empty states as explanation plus a CTA.
Each string has gone through the four editing phases (purposeful, concise, conversational, clear) and meets the length benchmarks: buttons 2-4 words (6 max), titles 40 characters max, errors 12-18 words including the fix, instructions 20 words max.
For an audit or edit, each change is shown before and after, with the rule it applies. references/content-usability-checklist.md is run on the final set.

Constraints

Sentence case. Second person. Active voice by default. Consistent terminology across the whole flow.
No generic labels ("OK", "Submit", "Click here"), no blame words ("invalid", "illegal"), no bare error codes, and no dead ends: every error names a recovery step.
Plain language at a 7th-8th grade reading level for a general audience (9th-10th for professional tools). Define a technical term the first time it appears.
Accessible by default: descriptive link and button text, visible labels (never placeholder-only), and meaning never carried by colour alone. See references/accessibility-guidelines.md.
Tone shifts with context and stakes; voice does not. High-stakes confirmations state the consequence plainly and make backing out easy.
Keep existing brand voice rules when the product has them. Use references/voice-chart-template.md only when none exist.

Context

Full patterns, tone tables, benchmarks and editing process: references/ux-writing-rules.md.
Extended patterns: references/patterns-detailed.md. Before/after examples: examples/real-world-improvements.md. Fillable templates: templates/. Figma MCP workflow: docs/figma-integration.md.
Out of scope: long-form marketing content (blog posts, ads, emails). Route those to /kai-write and the content frameworks.

Escalate when

The product has no voice guidance and the tone choice would change meaning (for example, playful versus formal for a financial product). Ask once.
A string cannot meet its length limit without dropping required legal or safety information. Keep the information and flag the limit.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ux Writing AI skill do?

Why use Ux Writing on TypingMind?

Because you install it once and use it with any model. Ux Writing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ux Writing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cgallic/kai-cmo-harness/tree/main/harness/skills-v2/ux-writing. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ux Writing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ux Writing?

As many as you like. As long as a model supports skills, you can use Ux Writing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ux Writing AI skill free?

It is published on GitHub by cgallic. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Gh Stack

vercel

OrganizationPopular

Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or…

Agent Transcript

Requested GitHub PR/issue agent transcripts: redact, trim, preview, and insert safely.

Openclaw Refactor Docs

openclaw

OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

Gemini

Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

ux-writing (v2, goal-oriented)

Objective

Done when

Constraints

Context

Escalate when

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now