✍️ Content Designer Agent¶

🎯 Purpose¶

The Content Designer Agent is a language-focused, UX-aware agent within the ConnectSoft AI Software Factory responsible for UX microcopy generation, content strategy, voice and tone guidelines, error message authoring, accessibility text alternatives, and content auditing.

It crafts every word users see — from button labels and tooltips to error messages, empty states, onboarding copy, and notification text — ensuring consistency, clarity, and empathy across all product editions and platforms.

It doesn't just write copy — it designs language as a UX element, ensuring every word reduces cognitive load, guides action, and reflects the brand voice.

🧠 Core Role in the Factory¶

The Content Designer Agent serves as the voice architect of the Research and UX/UI Design cluster. It ensures that all user-facing text is intentional, consistent, accessible, and localization-ready — turning raw UI components into human-centered experiences.

🧩 Position in the Research and UX/UI Design Cluster¶

Layer	Cluster	Description
✍️ Copy Architect	Research and UX/UI Design	Generates and maintains all user-facing microcopy across UI surfaces
🎯 Voice & Tone Guardian	Research and UX/UI Design	Defines and enforces voice/tone guidelines per context and persona
🌍 Localization Readiness	Research and UX/UI Design	Ensures copy is structured for translation and cultural adaptation

flowchart TD
    UXD[UX Designer Agent] -->|ux_design_completed| CDA[Content Designer Agent]
    UID[UI Designer Agent] -->|ui_component_created| CDA
    LOC[Localization Agent] -->|localization_requested| CDA
    CDA --> UXD
    CDA --> UID
    CDA --> LOC
    CDA --> AEA[Accessibility Engineer Agent]

Hold "Alt" / "Option" to enable pan & zoom

🔄 Triggering Events¶

Event Trigger	Description
`ux_design_completed`	New UX flow requires microcopy for all interaction points
`ui_component_created`	New component needs button labels, tooltips, placeholders, and helper text
`localization_requested`	Content needs to be prepared for translation with context annotations
`error_flow_defined`	Error handling flow requires user-friendly error messages
`onboarding_flow_designed`	Onboarding sequence needs step-by-step instructional copy
`content_audit_requested`	Manual or automated request to audit existing copy for consistency
`brand_voice_updated`	Voice and tone guidelines have changed, requiring copy revision

⏱ Trigger Frequency and Schedule¶

Mode	Description
📥 Event-driven	Primary mode — activates on UX/UI completion or component creation
🕒 Scheduled	Quarterly content audit across all product editions
🚨 Consistency-driven	Immediate activation when voice/tone drift is detected across surfaces

💡 Trigger Payload Example¶

{
  "trigger": "ui_component_created",
  "component_id": "file-upload-widget",
  "component_type": "form_element",
  "surfaces": ["button_label", "placeholder", "helper_text", "error_message", "empty_state"],
  "persona_context": "clinic_admin",
  "edition": "pro",
  "tone": "professional_supportive"
}

📦 Responsibilities and Deliverables¶

🧰 Key Responsibilities¶

Responsibility	Description
✍️ Microcopy Generation	Author button labels, tooltips, placeholders, helper text, confirmation messages, and empty states
📋 Content Strategy	Define content hierarchy, information architecture labels, and navigation copy
🎯 Voice & Tone Documentation	Create and maintain voice/tone guidelines per product edition and persona context
❌ Error Message Authoring	Write clear, actionable, non-blaming error messages with recovery guidance
♿ Accessibility Text Alternatives	Generate alt text, ARIA labels, screen reader announcements, and accessible descriptions
📊 Content Audit	Systematic review of existing copy for consistency, clarity, tone alignment, and completeness
🌍 Localization Preparation	Structure copy with translator context, character limits, plural rules, and cultural notes
🧭 Onboarding Copy	Write step-by-step instructional copy for user onboarding and feature discovery flows
💡 Notification & Alert Copy	Author push notifications, email subject lines, in-app alerts, and status messages

📤 Deliverables¶

Deliverable Type	Description
✍️ UX Copy Package	Complete microcopy set for a component or flow (labels, errors, helpers, empties)
📋 Content Guidelines	Documentation of content patterns, word lists, and forbidden terms
🎯 Voice & Tone Guide	Structured guide defining voice attributes, tone spectrum, and contextual examples
❌ Error Message Library	Categorized library of error messages with codes, copy, and recovery actions
♿ Accessibility Copy Set	Alt texts, ARIA labels, and screen reader text for all UI components
📊 Content Audit Report	Analysis of existing copy with inconsistency findings and recommendations
📚 Content Memory Index	Historical store of all copy decisions for consistency and recall

🧩 Example Output (YAML)¶

content_package_id: cp-file-upload-202606
component_id: file-upload-widget
edition: pro
persona: clinic_admin
voice_tone: professional_supportive

microcopy:
  button_label: "Upload file"
  button_label_uploading: "Uploading..."
  button_label_success: "File uploaded"
  placeholder: "Drag and drop your file here, or click to browse"
  helper_text: "Accepted formats: PDF, DOCX, JPG, PNG. Maximum size: 25 MB."
  empty_state:
    heading: "No files uploaded yet"
    body: "Upload your first file to get started. You can drag and drop or use the upload button."
    cta: "Upload a file"

error_messages:
  file_too_large:
    title: "File too large"
    body: "The file you selected exceeds the 25 MB limit. Try compressing the file or choosing a smaller one."
    recovery: "Choose a different file"
  unsupported_format:
    title: "Unsupported file type"
    body: "We accept PDF, DOCX, JPG, and PNG files. The file you selected is a different format."
    recovery: "Choose a supported file"
  upload_failed:
    title: "Upload didn't complete"
    body: "Something went wrong during the upload. Check your connection and try again."
    recovery: "Retry upload"

accessibility:
  aria_label: "File upload area. Drag and drop files or press Enter to browse."
  upload_complete_announcement: "File successfully uploaded."
  error_announcement: "Error: {{error_title}}. {{error_body}}"

localization_notes:
  - key: button_label
    max_characters: 20
    context: "Primary action button on file upload component"
    plural_rules: none
  - key: helper_text
    max_characters: 100
    context: "Appears below the upload area to guide users"

🤝 Collaboration Interfaces¶

The Content Designer Agent operates as a language layer that enriches design and development outputs with human-centered copy.

🔄 Inbound Interfaces (Receives Data From)¶

Source Agent / System	Interface Type	Purpose
🎨 UX Designer Agent	Event: `ux_design_completed`	Provides interaction flow context requiring microcopy
🖼️ UI Designer Agent	Event: `ui_component_created`	Provides component surface inventory for copy generation
🌍 Localization Agent	Event: `localization_requested`	Requests localization-ready copy with context annotations
♿ Accessibility Engineer Agent	Event: `a11y_text_needed`	Requests accessible text alternatives for UI elements

📤 Outbound Interfaces (Sends Data To)¶

Target Agent / System	Interface Type	Purpose
🎨 UX Designer Agent	Event: `ux_copy_ready`	Returns microcopy for integration into design prototypes
🖼️ UI Designer Agent	Event: `component_copy_ready`	Provides copy for component implementation
🌍 Localization Agent	Event: `content_localization_ready`	Delivers structured copy with translator context
♿ Accessibility Engineer Agent	Event: `a11y_text_generated`	Provides alt text, ARIA labels, and screen reader copy
📥 Memory Indexing System	Internal Save Event	Stores copy decisions for consistency and audit

🕸️ Agent Interaction Graph¶

flowchart LR
    UXD[UX Designer] --> CDA[Content Designer Agent]
    UID[UI Designer] --> CDA
    CDA --> UXD
    CDA --> UID
    CDA --> LOC[Localization Agent]
    CDA --> AEA[Accessibility Engineer]

Hold "Alt" / "Option" to enable pan & zoom

🧠 Memory and Knowledge¶

📚 Preloaded Knowledge¶

Knowledge Domain	Description
✍️ UX Writing Best Practices	Microcopy patterns, conciseness rules, action-oriented language, cognitive load reduction
🎯 Voice & Tone Frameworks	Voice attribute models, tone spectrums (formal↔casual, serious↔playful), contextual tone mapping
❌ Error Message Patterns	Non-blaming language, recovery-focused messaging, error categorization by severity
♿ Accessible Content Guidelines	WCAG text alternative requirements, screen reader announcement patterns, plain language principles
🌍 Localization Best Practices	String externalization, ICU message format, plural rules, cultural sensitivity guidelines
📋 Content Strategy Frameworks	Content modeling, structured content, content-first design methodology

🧩 Dynamic Knowledge (Updated During Execution)¶

Source	Type of Knowledge
UX Designer Agent	Interaction flow context and user journey stage
UI Designer Agent	Component surface inventory and visual hierarchy
Localization Agent	Language-specific constraints and cultural feedback
Accessibility Engineer Agent	Screen reader behavior patterns and a11y requirements
Memory Store	Historical copy decisions, approved terminology, and content patterns

🧬 Semantic Memory Embeddings¶

The agent stores and retrieves:

Past microcopy decisions by component type and context
Error message patterns that tested well with users
Voice and tone examples for recall when authoring in similar contexts
Content audit findings for tracking improvement over time

🔁 Knowledge Update Policies¶

Type	Update Frequency	Notes
Writing Best Practices	Manual or infrequent	Core UX writing principles are version-controlled
Voice & Tone Guidelines	On brand update	Refreshed when brand identity or product positioning changes
Copy Decisions	Continuous	Updated on every microcopy generation or audit
Memory Embeddings	Continuous	Updated after every content package or audit output

✅ Validation¶

🔍 Validation Objectives¶

Confirm that all component surfaces have complete microcopy coverage
Ensure copy follows voice and tone guidelines for the target persona and edition
Verify error messages are actionable, non-blaming, and include recovery guidance
Validate accessibility text meets WCAG requirements for text alternatives
Ensure copy is localization-ready with character limits and context annotations

🧪 Types of Validation Checks¶

Layer	Validation Logic
✍️ Surface Coverage	Every component surface (label, helper, error, empty) has defined copy
🎯 Tone Consistency	Copy tone matches the defined spectrum for persona and context
❌ Error Quality	Error messages follow the pattern: title + explanation + recovery action
♿ Accessibility Compliance	All interactive elements have ARIA labels; images have alt text
🌍 Localization Readiness	Copy has character limits, context notes, and plural rule annotations
📏 Length Constraints	Copy respects UI layout constraints (button width, tooltip max chars)
🧾 Terminology Consistency	Uses approved terminology from the content glossary

⚠️ Flagging Risky Outputs¶

Scenario	Action Taken
Component surface missing copy	Flag as `incomplete_coverage: true`
Error message without recovery action	Flag as `non_actionable_error: true`
Copy exceeds UI character limits	Flag as `overflow_risk: true` and suggest alternatives
Tone inconsistent with guidelines	Flag as `tone_drift: true` and suggest revision
Missing localization context	Flag as `localization_incomplete: true`

🧪 Validation Result Tags¶

validation:
  status: passed
  surface_coverage: 100%
  tone_consistency: 0.94
  error_quality: valid
  accessibility_compliance: true
  localization_readiness: true
  trace_id: "evt-component-file-upload"

✅ Summary¶

The Content Designer Agent is the voice of the product in the ConnectSoft AI Software Factory — ensuring that every word users encounter is intentional, accessible, and brand-aligned.

It answers:

"What should this button say?"
"How do we tell users something went wrong without blaming them?"
"Is our copy consistent across all product surfaces?"
"Is every UI element accessible to screen reader users?"
"Is our copy ready for translation into 12 languages?"

Without this agent, copy is an afterthought — inconsistent, inaccessible, and tone-deaf. With it, language becomes a designed experience element, as intentional as color and layout.