Developer Tooling Error State Experience Matrix

Role: Staff Product Designer specializing in Developer Experience (DevEx) and CLI/IDE workflow usability.

Context

• Target tooling surface: {{target_tool_type}}
• Severity categories in scope: {{error_severity_levels}}
• Target user technical background: {{user_skill_profile}}
• Information density requirements: {{stack_trace_depth}}
• Actionable recovery capabilities: {{remediation_action_types}}
• Execution runtime context: {{primary_runtime_environment}}

Task

Generate a comprehensive UX matrix that maps raw engineering diagnostics and error conditions to structured interface components, progressive disclosure tiers, and direct remediation patterns across developer touchpoints.

Method

1. Break down the {{error_severity_levels}} within {{primary_runtime_environment}} into discrete visual hierarchy tiers.
2. Evaluate how {{user_skill_profile}} cognitively processes complex error outputs in {{target_tool_type}}.
3. Define progressive disclosure breakpoints for {{stack_trace_depth}} to avoid visual noise while preserving technical fidelity.
4. Correlate each error state with high-leverage {{remediation_action_types}} to minimize mean time to resolution (MTTR).
5. Map terminal ANSI color palettes, typography, and interactive web/IDE elements to each error category.
6. Identify contextual jump-links, copy-to-clipboard patterns, and telemetry logging hooks for each failure mode.
7. Synthesize findings into a comparative UI/UX matrix contrasting current developer friction with proposed design patterns.

Constraints

• MUST format the core deliverable as a Markdown comparative matrix with at least 5 structured columns.
• MUST NOT suggest abstract UI ideas that cannot be rendered in {{target_tool_type}}.
• MUST include explicit keyboard-accessible interaction pathways for every remediation pattern.
• Recommendations MUST balance deep technical accuracy with cognitive load reduction for {{user_skill_profile}}.

Output format

• Section 1: Executive Overview (100-150 words summarizing DevEx problem statement and design thesis).
• Section 2: Error Experience Matrix (Markdown table with columns: Error Severity, Visual Component, Information Architecture Tier, Remediation Trigger, Keyboard Shortcut / Interaction Model).
• Section 3: Component Specification Notes (3-5 concise bullet points covering typography, accessibility, and truncation rules).

Self-review

• Confirm all 6 variables are directly incorporated into matrix rows and columns.
• Verify that every listed remediation is technically feasible within {{primary_runtime_environment}}.
• Ensure no placeholder text or vague recommendations appear in the matrix cells.