|
| 1 | +--- |
| 2 | +name: depression-sensitive-web-content |
| 3 | +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." |
| 4 | +metadata: |
| 5 | + version: "1.0.0" |
| 6 | + author: "OpenCode Community" |
| 7 | + standards: |
| 8 | + - "WCAG 2.2" |
| 9 | + - "W3C COGA" |
| 10 | + - "ISO 9241-110" |
| 11 | + - "ISO/IEC 30071-1" |
| 12 | + domains: |
| 13 | + - accessibility |
| 14 | + - content-design |
| 15 | + - cognitive-accessibility |
| 16 | + - mental-health-ux |
| 17 | + license: MIT |
| 18 | +--- |
| 19 | + |
| 20 | +# Depression-Sensitive Web Content Support (DS-WCS) |
| 21 | + |
| 22 | +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. |
| 23 | + |
| 24 | +## Purpose and Clinical Boundaries |
| 25 | + |
| 26 | +This skill is a **UX and content accessibility tool**, NOT a clinical resource. It focuses on: |
| 27 | + |
| 28 | +- Reducing shame-inducing language in digital interfaces |
| 29 | +- Minimizing cognitive load for users with executive function differences |
| 30 | +- Providing clear error recovery paths |
| 31 | +- Supporting emotional safety through calm, professional tone |
| 32 | +- Improving task completion rates for users with cognitive impairments |
| 33 | + |
| 34 | +**This skill does NOT provide:** |
| 35 | +- Medical advice or diagnosis |
| 36 | +- Clinical assessment of mental health conditions |
| 37 | +- Therapeutic interventions |
| 38 | +- Treatment recommendations |
| 39 | + |
| 40 | +For mental health concerns, users should seek guidance from qualified healthcare professionals. |
| 41 | + |
| 42 | +--- |
| 43 | + |
| 44 | +## When to Use This Skill |
| 45 | + |
| 46 | +Apply this skill when auditing or reviewing: |
| 47 | + |
| 48 | +- **Error messages and validation feedback** - Forms, checkout flows, login/authentication |
| 49 | +- **Call-to-action buttons and labels** - Signup, submit, and action buttons |
| 50 | +- **Empty states and onboarding flows** - New user experiences, progressive disclosure |
| 51 | +- **Notifications and alerts** - Warnings, confirmations, status updates |
| 52 | +- **Help text and tooltips** - Form guidance, contextual assistance |
| 53 | +- **Content for sensitive services** - Health portals, financial services, government applications, wellness platforms |
| 54 | + |
| 55 | +**Ideal for:** |
| 56 | +- Content design reviews |
| 57 | +- UX writing audits |
| 58 | +- Accessibility assessments (complementary to technical WCAG audits) |
| 59 | +- User experience improvement initiatives |
| 60 | +- Inclusive design implementation |
| 61 | + |
| 62 | +--- |
| 63 | + |
| 64 | +## When NOT to Use This Skill |
| 65 | + |
| 66 | +Do not use this skill for: |
| 67 | + |
| 68 | +- **Medical or clinical content requests** - "Assess if this patient has depression" (clinical diagnosis) |
| 69 | +- **Therapy or counseling guidance** - "What should I say to someone with depression" (treatment advice) |
| 70 | +- **Non-UX content reviews** - Legal documents, medical records, clinical protocols |
| 71 | +- **Simple grammar or typo corrections** - Use general language tools instead |
| 72 | +- **Content already reviewed by clinical professionals** - Mental health organization guidelines |
| 73 | + |
| 74 | +--- |
| 75 | + |
| 76 | +## Context for Agents |
| 77 | + |
| 78 | +Depression affects cognitive function, including: |
| 79 | + |
| 80 | +- **Working memory**: Reduced capacity to hold information across steps |
| 81 | +- **Executive function**: Impaired planning, decision-making, and problem-solving |
| 82 | +- **Attention**: Difficulty concentrating,容易被分散 |
| 83 | +- **Processing speed**: Slower information processing and response generation |
| 84 | + |
| 85 | +These deficits mean users may: |
| 86 | +- Abandon tasks when faced with shame-inducing errors |
| 87 | +- Struggle with complex, multi-step processes |
| 88 | +- Forget information between steps |
| 89 | +- Require clear recovery paths to maintain task completion |
| 90 | +- Be more sensitive to tone and emotional language |
| 91 | + |
| 92 | +This skill applies evidence-based content patterns to support these users while maintaining alignment with international accessibility standards. |
| 93 | + |
| 94 | +--- |
| 95 | + |
| 96 | +## Agent Workflow Instructions |
| 97 | + |
| 98 | +### For Audit Requests |
| 99 | + |
| 100 | +When a user requests content auditing for depression-sensitive patterns, follow this workflow: |
| 101 | + |
| 102 | +1. **Scope Definition** |
| 103 | + - Identify target content (files, URLs, or user-provided text) |
| 104 | + - Determine content types to review (errors, CTAs, forms, notifications, etc.) |
| 105 | + - Note any context-specific considerations (health, financial, sensitive services) |
| 106 | + |
| 107 | +2. **Content Analysis** |
| 108 | + - Read target content files or user-provided text |
| 109 | + - Apply the audit checklist from `resources/implementation-guide.md#audit-checklist` |
| 110 | + - Identify patterns across these categories: |
| 111 | + - Error messages (shame language, missing recovery) |
| 112 | + - CTAs (generic labels, urgency) |
| 113 | + - Forms (memory reliance, required field handling) |
| 114 | + - Notifications (urgency markers, dismissive tone) |
| 115 | + - Empty states (obligation language, shame) |
| 116 | + - Onboarding (premature disclosure, unclear value) |
| 117 | + - Help text (hidden, inconsistent) |
| 118 | + |
| 119 | +3. **Severity Assessment** |
| 120 | + - Rate each finding: HIGH, MEDIUM, or LOW |
| 121 | + - HIGH: Causes task abandonment or emotional distress |
| 122 | + - MEDIUM: Increases cognitive load or friction |
| 123 | + - LOW: Missed opportunity, comfort improvement |
| 124 | + |
| 125 | +4. **Findings Report Generation** |
| 126 | + - Organize by severity (HIGH first) |
| 127 | + - Include file path and line number references |
| 128 | + - Provide specific text excerpts (before) |
| 129 | + - Reference standards for each finding |
| 130 | + |
| 131 | +5. **Standards Traceability** |
| 132 | + - Map each finding to relevant WCAG 2.2 success criteria |
| 133 | + - Map to W3C COGA objectives |
| 134 | + - Map to ISO 9241-110 principles |
| 135 | + - Map to ISO/IEC 30071-1 clauses where applicable |
| 136 | + |
| 137 | +### For Rewrite Requests |
| 138 | + |
| 139 | +When a user requests content rewriting for depression-sensitive patterns: |
| 140 | + |
| 141 | +1. **Pattern Identification** |
| 142 | + - Identify problematic patterns using the rewrite library |
| 143 | + - Consult `resources/implementation-guide.md#rewrite-library` |
| 144 | + - Determine which principles apply |
| 145 | + |
| 146 | +2. **Rewrite Application** |
| 147 | + - Apply appropriate rewrite rules |
| 148 | + - Reference the 12+ before/after examples for guidance |
| 149 | + - Maintain original intent while improving accessibility |
| 150 | + |
| 151 | +3. **Output Generation** |
| 152 | + - Present before/after comparison |
| 153 | + - Include rationale for each change |
| 154 | + - Map changes to specific standards |
| 155 | + - Note any context-specific considerations |
| 156 | + |
| 157 | +### Output Format Template |
| 158 | + |
| 159 | +All DS-WCS skill outputs shall follow this structure: |
| 160 | + |
| 161 | +```markdown |
| 162 | +## Findings |
| 163 | + |
| 164 | +### HIGH Severity |
| 165 | +[Findings that cause task abandonment or emotional distress] |
| 166 | +- **File:line**: Description of issue |
| 167 | + - Original: "problematic text" |
| 168 | + - Standards: WCAG X.X.X, COGA Objective Y, ISO 9241-110 Clause Z |
| 169 | + |
| 170 | +### MEDIUM Severity |
| 171 | +[Findings that increase cognitive load or friction] |
| 172 | +- Same format |
| 173 | + |
| 174 | +### LOW Severity |
| 175 | +[Missed opportunities for improvement] |
| 176 | +- Same format |
| 177 | + |
| 178 | +## Recommended Rewrites |
| 179 | + |
| 180 | +### Example 1: [Category] |
| 181 | +**Before:** |
| 182 | +``` |
| 183 | +original text |
| 184 | +``` |
| 185 | +
|
| 186 | +**After:** |
| 187 | +``` |
| 188 | +rewritten text |
| 189 | +``` |
| 190 | +
|
| 191 | +**Rationale:** |
| 192 | +- Why this change improves accessibility |
| 193 | +- How it addresses the identified issue |
| 194 | +
|
| 195 | +**Standards:** |
| 196 | +- WCAG 2.2: X.X.X (Error Identification) |
| 197 | +- W3C COGA: Objective N |
| 198 | +- ISO 9241-110: Clause M |
| 199 | +
|
| 200 | +## Structure Analysis |
| 201 | +
|
| 202 | +[Optional: Observations about content organization, scanability, memory load] |
| 203 | +
|
| 204 | +## Standards Traceability Summary |
| 205 | +
|
| 206 | +| Finding Type | WCAG 2.2 | COGA | ISO 9241-110 | ISO/IEC 30071-1 | |
| 207 | +|-------------|----------|------|--------------|-----------------| |
| 208 | +| [Category] | X.X.X | Obj N| Clause M | Clause P | |
| 209 | +
|
| 210 | +--- |
| 211 | +
|
| 212 | +## Resources |
| 213 | +
|
| 214 | +The following resources provide detailed guidance: |
| 215 | +
|
| 216 | +- **`resources/implementation-guide.md`**: Comprehensive guide containing: |
| 217 | + - **Section A: Rewrite Library** - Seven core principles with 12+ before/after examples |
| 218 | + - **Section B: Standards Traceability Matrix** - Complete mapping to all four standards |
| 219 | + - **Section C: Audit Checklist** - 40+ check items organized by content type |
| 220 | +
|
| 221 | +--- |
| 222 | +
|
| 223 | +## Quality Assurance |
| 224 | +
|
| 225 | +When applying this skill: |
| 226 | +
|
| 227 | +1. **Preserve original intent** - Rewrites must maintain the original purpose and meaning |
| 228 | +2. **Maintain brand voice** - Adapt tone to match organizational style while improving accessibility |
| 229 | +3. **Consider context** - Sensitive contexts (health, finance) may require additional consideration |
| 230 | +4. **Test with users** - Where possible, validate changes with users who have cognitive differences |
| 231 | +5. **Document decisions** - Note any context-specific rationale for audit findings |
| 232 | +
|
| 233 | +--- |
| 234 | +
|
| 235 | +## Integration with Other Skills |
| 236 | +
|
| 237 | +This skill complements: |
| 238 | +
|
| 239 | +- **`accessibility-compliance-accessibility-audit`**: WCAG technical compliance (focused on perceivable, operable, understandable, robust) |
| 240 | +- **`web-design-guidelines`**: Structural and interaction design best practices |
| 241 | +- **`ui-ux-pro-max`**: Comprehensive UI/UX design patterns |
| 242 | +
|
| 243 | +DS-WCS addresses the **emotional and cognitive** dimensions of accessibility that complement the technical dimensions covered by other skills. |
| 244 | +
|
| 245 | +--- |
| 246 | +
|
| 247 | +## Non-Clinical Disclaimer |
| 248 | +
|
| 249 | +This tool addresses content and UX design for emotional safety and cognitive accessibility. It is NOT: |
| 250 | +
|
| 251 | +- A clinical assessment tool |
| 252 | +- A diagnostic instrument |
| 253 | +- A treatment recommendation resource |
| 254 | +- A substitute for mental health professional guidance |
| 255 | +
|
| 256 | +For mental health concerns, consult qualified healthcare providers. |
0 commit comments