agentsclimarketplace

Ux writing

Skill nevitonsantana/adaptive-skills/skills/ux-writing

38 portable Agent Skills for disciplined, reviewable AI-assisted work across Codex, Claude Code, GitHub Copilot, and compatible agents.

Install
npx -y skills add nevitonsantana/adaptive-skills --skill ux-writing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Improve product language, terminology, and explanatory text so interface and documentation are semantically safe and easy to act on.

SKILL.md

2.1 KB, as published. Nobody here has run it

Overview

Use this skill when the main problem is language: wording, structure, terminology, explanation, or semantic safety.

When to Use

  • microcopy review
  • labels and messages
  • product documentation language
  • glossary and terminology clean-up

When NOT to Use

  • pure visual polish
  • brand campaign writing
  • cases where the concept itself is still undefined

Core Moves

  1. Classify the content and the reader decision.
  2. Diagnose whether the issue is wording, structure, terminology, explanation, or concept.
  3. Rewrite for precision before elegance.
  4. Preserve semantic safety and actionability.

Optional Modules

  • Terminology alignment — Create or tighten a canonical term when multiple names exist.
  • Explanation layer — Add short explanatory support for thresholds, states, or system behavior.
  • Public-facing tone — Adjust for institutional or sensitive contexts without pretending certainty.

Activation Triggers

  • Use terminology alignment when the same concept has multiple names.
  • Use explanation layer when users may misread the consequence of a state or action.
  • Use public-facing tone when the text will travel beyond the product team.

Expected Output

  • clearer copy
  • explicit terminology decisions
  • safer explanatory text

Verification

  • The rewrite improves precision, not just style.
  • System state, interpretation, and action are not blurred together.
  • A reader can act correctly after a quick scan.

Handoff Signals

  • The root problem is conceptual rather than textual.
  • The next move belongs to design or product strategy rather than writing.

Pairs Well With

  • heuristic-audit
  • communication
  • triad-check

Anti-patterns

  • Using elegant language to hide conceptual confusion.
  • Removing technical precision when it is operationally necessary.
  • Treating documentation and interface language as separate universes.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.