depression-sensitive-web-content

name	depression-sensitive-web-content
description	Audit and rewrite web content for depression-sensitive UX patterns. Removes shame/blame language, reduces cognitive load, improves error recovery. Maps to WCAG 2.2, W3C COGA, ISO 9241-110, ISO/IEC 30071-1. Non-clinical content accessibility tool.
metadata	{"version":"1.0.0","author":"OpenCode Community","standards":["WCAG 2.2","W3C COGA","ISO 9241-110","ISO/IEC 30071-1"],"domains":["accessibility","content-design","cognitive-accessibility","mental-health-ux"],"license":"MIT"}

Depression-Sensitive Web Content Support (DS-WCS)

This skill enables OpenCode agents to audit and rewrite web content for depression-sensitive patterns. The skill addresses emotional safety and cognitive accessibility through evidence-based content design principles.

Purpose and Clinical Boundaries

This skill is a UX and content accessibility tool, NOT a clinical resource. It focuses on:

• Reducing shame-inducing language in digital interfaces
• Minimizing cognitive load for users with executive function differences
• Providing clear error recovery paths
• Supporting emotional safety through calm, professional tone
• Improving task completion rates for users with cognitive impairments

This skill does NOT provide:

• Medical advice or diagnosis
• Clinical assessment of mental health conditions
• Therapeutic interventions
• Treatment recommendations

For mental health concerns, users should seek guidance from qualified healthcare professionals.

---

When to Use This Skill

Apply this skill when auditing or reviewing:

• Error messages and validation feedback - Forms, checkout flows, login/authentication
• Call-to-action buttons and labels - Signup, submit, and action buttons
• Empty states and onboarding flows - New user experiences, progressive disclosure
• Notifications and alerts - Warnings, confirmations, status updates
• Help text and tooltips - Form guidance, contextual assistance
• Content for sensitive services - Health portals, financial services, government applications, wellness platforms

Ideal for:

• Content design reviews
• UX writing audits
• Accessibility assessments (complementary to technical WCAG audits)
• User experience improvement initiatives
• Inclusive design implementation

---

When NOT to Use This Skill

Do not use this skill for:

• Medical or clinical content requests - "Assess if this patient has depression" (clinical diagnosis)
• Therapy or counseling guidance - "What should I say to someone with depression" (treatment advice)
• Non-UX content reviews - Legal documents, medical records, clinical protocols
• Simple grammar or typo corrections - Use general language tools instead
• Content already reviewed by clinical professionals - Mental health organization guidelines

---

Context for Agents

Depression affects cognitive function, including:

• Working memory: Reduced capacity to hold information across steps
• Executive function: Impaired planning, decision-making, and problem-solving
• Attention: Difficulty concentrating and maintaining focus
• Processing speed: Slower information processing and response generation

These deficits mean users may:

• Abandon tasks when faced with shame-inducing errors
• Struggle with complex, multi-step processes
• Forget information between steps
• Require clear recovery paths to maintain task completion
• Be more sensitive to tone and emotional language

This skill applies evidence-based content patterns to support these users while maintaining alignment with international accessibility standards.

---

Agent Workflow Instructions

For Audit Requests

When a user requests content auditing for depression-sensitive patterns, follow this workflow:

1. Scope Definition

   • Identify target content (files, URLs, or user-provided text)
   • Determine content types to review (errors, CTAs, forms, notifications, etc.)
   • Note any context-specific considerations (health, financial, sensitive services)

2. Content Analysis

   • Read target content files or user-provided text
   • Apply the audit checklist from resources/implementation-guide.md#audit-checklist
   • Identify patterns across these categories:
     • Error messages (shame language, missing recovery)
     • CTAs (generic labels, urgency)
     • Forms (memory reliance, required field handling)
     • Notifications (urgency markers, dismissive tone)
     • Empty states (obligation language, shame)
     • Onboarding (premature disclosure, unclear value)
     • Help text (hidden, inconsistent)

3. Severity Assessment

   • Rate each finding: HIGH, MEDIUM, or LOW
   • HIGH: Causes task abandonment or emotional distress
   • MEDIUM: Increases cognitive load or friction
   • LOW: Missed opportunity, comfort improvement

4. Findings Report Generation

   • Organize by severity (HIGH first)
   • Include file path and line number references
   • Provide specific text excerpts (before)
   • Reference standards for each finding

5. Standards Traceability

   • Map each finding to relevant WCAG 2.2 success criteria
   • Map to W3C COGA objectives
   • Map to ISO 9241-110 principles
   • Map to ISO/IEC 30071-1 clauses where applicable

For Rewrite Requests

When a user requests content rewriting for depression-sensitive patterns:

1. Pattern Identification

   • Identify problematic patterns using the rewrite library
   • Consult resources/implementation-guide.md#rewrite-library
   • Determine which principles apply

2. Rewrite Application

   • Apply appropriate rewrite rules
   • Reference the 12+ before/after examples for guidance
   • Maintain original intent while improving accessibility

3. Output Generation

   • Present before/after comparison
   • Include rationale for each change
   • Map changes to specific standards
   • Note any context-specific considerations

Output Format Template

All DS-WCS skill outputs shall follow this structure:

## Findings

### HIGH Severity
[Findings that cause task abandonment or emotional distress]
- **File:line**: Description of issue
  - Original: "problematic text"
  - Standards: WCAG X.X.X, COGA Objective Y, ISO 9241-110 Clause Z

### MEDIUM Severity
[Findings that increase cognitive load or friction]
- Same format

### LOW Severity
[Missed opportunities for improvement]
- Same format

## Recommended Rewrites

### Example 1: [Category]
**Before:**

original text

**After:**

rewritten text

**Rationale:**
- Why this change improves accessibility
- How it addresses the identified issue

**Standards:**
- WCAG 2.2: X.X.X (Error Identification)
- W3C COGA: Objective N
- ISO 9241-110: Clause M

## Structure Analysis

[Optional: Observations about content organization, scanability, memory load]

## Standards Traceability Summary

| Finding Type | WCAG 2.2 | COGA | ISO 9241-110 | ISO/IEC 30071-1 |
|-------------|----------|------|--------------|-----------------|
| [Category]  | X.X.X    | Obj N| Clause M     | Clause P        |

---

## Resources

The following resources provide detailed guidance:

- **`resources/implementation-guide.md`**: Comprehensive guide containing:
  - **Section A: Rewrite Library** - Seven core principles with 12+ before/after examples
  - **Section B: Standards Traceability Matrix** - Complete mapping to all four standards
  - **Section C: Audit Checklist** - 40+ check items organized by content type

---

## Quality Assurance

When applying this skill:

1. **Preserve original intent** - Rewrites must maintain the original purpose and meaning
2. **Maintain brand voice** - Adapt tone to match organizational style while improving accessibility
3. **Consider context** - Sensitive contexts (health, finance) may require additional consideration
4. **Test with users** - Where possible, validate changes with users who have cognitive differences
5. **Document decisions** - Note any context-specific rationale for audit findings

---

## Integration with Other Skills

This skill complements:

- **`accessibility-compliance-accessibility-audit`**: WCAG technical compliance (focused on perceivable, operable, understandable, robust)
- **`web-design-guidelines`**: Structural and interaction design best practices
- **`ui-ux-pro-max`**: Comprehensive UI/UX design patterns

DS-WCS addresses the **emotional and cognitive** dimensions of accessibility that complement the technical dimensions covered by other skills.

---

## Non-Clinical Disclaimer

This tool addresses content and UX design for emotional safety and cognitive accessibility. It is NOT:

- A clinical assessment tool
- A diagnostic instrument
- A treatment recommendation resource
- A substitute for mental health professional guidance

For mental health concerns, consult qualified healthcare providers.