content-design

Designs interface content around user needs, information priority, and task clarity.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/rebuildup/my-web-2026 --skill content-design-rebuildup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-design
Source: https://github.com/rebuildup/my-web-2026/tree/main/skills/content-design
Command: npx skills add https://github.com/rebuildup/my-web-2026 --skill content-design-rebuildup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Interfaces often ship with copy written last, organized around internal structure rather than user needs, producing unclear headings, vague labels, and errors that block recovery. This Skill designs and revises product, service, and page content starting from what users must understand, decide, and do. ## Core Features & Use Cases - Need-first content design: Follows an Inspect → Extract → Translate → Implement → Verify workflow that identifies what information users need before writing any copy. - Observation axes: Evaluates purpose, information priority, language, scanning structure, interaction copy, and voice/tone against primary references in references/content.md. - Decision rules for UI copy: Covers leading with what matters, plain language without losing precision, predictable links and controls, recovery-oriented error messages, and status/confirmation content. - Use Case: When redesigning a checkout flow, use this Skill to rewrite headings, button labels, instructions, and error messages so users can predict outcomes and recover from mistakes. ## Quick Start Use the content-design skill to review and rewrite the headings, labels, and error messages on this settings page around user tasks.

Frequently Asked Questions about content-design

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

FAQPage Schema
How do I design interface content around user needs?

Start by identifying what users must know, decide, and do next, plus what they need to recover from mistakes. Then inspect the current artifact, extract required information, translate it into headings, labels, and messages, and verify it in the real task flow.

How to write error messages that help users recover?

Error content should answer three things: what did not complete, which input or condition caused the problem, and what the user should do next. Avoid blaming wording, bare error codes, and vague messages like "Invalid input" that give no recovery path.

What is the difference between content design and form design?

Form design owns question sequencing, single-page versus multi-step choices, validation timing, and review flows. Content design owns the wording and information clarity inside those structures, such as labels, instructions, and error text.

Should button labels say Click here or Learn more?

No. Link and button labels should let users predict the destination, action, or object without surrounding context. Use consistent vocabulary for the same action and avoid reusing the same words for different meanings.

When should plain language not replace technical terms?

When a technical, legal, or medical term is needed for accuracy or searchability, keep it. Put the familiar wording first, then include or explain the precise term, and avoid introducing multiple names for the same concept.