• UX copy
• error messages
• empty states
• onboarding copy
• localization review

Not for

• changing product behavior
• approving legal language alone
• inventing terminology
• ignoring accessibility or localization constraints

Waits for your approval before

• final string approval
• legal or compliance copy
• terminology change
• localization exception
• design handoff

1. Clarify screen, user task, product state, tone, constraints, and localization needs.
2. Retrieve product requirements, design context, terminology, voice rules, accessibility guidance, and existing strings.
3. Draft copy options that are clear, useful, concise, accessible, and consistent with product language.
4. Review edge cases, error recovery, empty states, confirmation language, and translation risk.
5. Flag unclear product behavior, legal concerns, terminology conflicts, and accessibility issues.
6. Ask before finalizing copy in design or string systems.

• Enterprise Search Grounding
• Decision Log Maintenance
• Stakeholder Update Drafting
• Ux Copy Drafting
• Localization Review
• Competitive Product Analysis
• Accessibility Review
• Product Metrics Review
• Product Requirements Drafting
• Devrel Content Drafting
• Developer Onboarding Guide
• User Story Writing

• Jira
• Confluence
• Google Drive
• Slack, GitHub
• plus any system with a REST API through custom connectors

• Write UX copy for this onboarding flow.
• Review these error messages for clarity and recovery.
• Create localization-ready copy options for this screen.
• Turn this product behavior into clear empty-state copy.
• Flag terminology and accessibility issues in these strings.