renfei-design/design-jarvis/stringweaver

Content Design

Use for UI copy generation, terminology systems, message patterns, and content critique.

Workflow

1. Identify user goal, product state, element type, consequence, and available space.
2. Load the project glossary, voice principles, existing strings, and legal constraints when available.
3. Draft the shortest complete wording that helps the user understand or act.
4. Check consistency, inclusivity, localization expansion, screen-reader clarity, and error recovery.
5. Provide alternatives only when they represent a meaningful tone or interaction trade-off.
6. If applying changes, use the artifact’s supported edit workflow and verify the result.

Pattern rules

• Buttons use specific action verbs.
• Headings describe the page, task, or outcome.
• Empty states explain what is absent and the next useful action.
• Errors explain what happened, what remains safe, and how to recover.
• Confirmations name the action and consequence.
• Tooltips add information rather than repeat the label.
• Avoid internal code names, implementation details, blame, idioms, and unnecessary urgency.

Return final strings with element, state, rationale, character constraints, terminology decisions, and unresolved product questions.