How to Report Errors with the I-Have-ADHD Skill: A Matter-of-Fact Approach

Report errors by stating what went wrong, why it happened, and how to fix it—never use emotive phrases like "Uh oh" or "There seems to be a problem."

The I-Have-ADHD skill enforces a strict, ADHD-friendly communication style that prioritizes clarity and action over emotional language. When this skill encounters errors, following its prescribed error-reporting format ensures users receive immediate, actionable guidance without cognitive overhead.

The Core Rule: Rule 8 in SKILL.md

The definitive source for error reporting lives in skills/i-have-adhd/SKILL.md. Rule 8 explicitly bans three common error openers:

• "Uh oh"
• "Oh no"
• "There seems to be a problem"

According to the skill's source code, these phrases add emotional noise that distracts from problem-solving. The rule mandates replacing them with a three-part structure: location, cause, and fix.

The Three-Part Error Report Structure

Every error report in the I-Have-ADHD skill follows this exact template:

1. Location

Pinpoint precisely where the failure occurred—file path, line number, or command name.

2. Cause

State concisely why the failure happened. No speculation, no hedging.

3. Fix

Provide the exact change or command needed to resolve the issue.

Before and After: Error Reporting Examples

Bad (violates Rule 8):

Uh oh, the test is failing. There seems to be an issue with authentication...

Good (Rule 8 compliant):

Test fails at auth.spec.ts:42: expected 200, got 401. Cause: missing auth header. Fix: add Authorization: Bearer ${token} to the request.

The compliant version delivers the same information in half the words, with zero emotional filler and immediate actionability.

Markdown Template for Error Reports

Use this reusable format in your responses:

**Error report template**

- **File/Command:** `src/auth.ts:42`
- **Cause:** Missing `Authorization` header in the request.
- **Fix:** Insert `Authorization: Bearer ${token}` before sending the request.

Sample usage in a response:

Test fails at auth.spec.ts:42: expected 200, got 401.
Cause: missing auth header.
Fix: add Authorization: Bearer ${token} to the request.

## Where the Rules Live

Two files in the `ayghri/i-have-adhd` repository define and enforce this standard:

| File | Purpose |
|------|---------|
| [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) | Canonical rule definition, including Rule 8's error-reporting mandate |
| [`.cursor/skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/.cursor/skills/i-have-adhd/SKILL.md) | Mirror location maintained in sync with the main file |

Both files implement identical constraints. When the skill loads, it references these paths to validate response tone and structure.

## Why This Approach Works for ADHD

The I-Have-ADHD skill's error reporting eliminates **decision fatigue** and **emotional processing** from debugging. By front-loading critical information (location, cause, fix) and stripping away apologetic or alarmist language, users can:

- Instantly grasp severity
- Skip to the relevant file/line
- Execute the fix without parsing subtext

This aligns with cognitive load research: direct, structured information reduces executive function demands.

## Summary

- **Never use** "Uh oh", "Oh no", or "There seems to be a problem" when reporting errors with the I-Have-ADHD skill
- **Always structure** error reports as: Location → Cause → Fix
- **Reference** [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) Rule 8 for the canonical definition
- **Maintain** identical formatting across both `skills/` and `.cursor/skills/` mirror locations

## Frequently Asked Questions

### What happens if I use emotional language in an error report?

The I-Have-ADHD skill will flag the response as non-compliant. Per [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md) Rule 8, emotive phrasing violates the established communication protocol and should be rewritten in the matter-of-fact format.

### Can I add context before stating the location?

No. Leading with location immediately orients the user. Context belongs in the **Cause** section if truly necessary, though brevity is preferred.

### Is the `.cursor/skills/` mirror required?

Yes. The repository maintains both [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) and [`.cursor/skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/.cursor/skills/i-have-adhd/SKILL.md) in sync. Tools or IDEs referencing either path receive identical rule enforcement.

### Does this apply to warnings or just errors?

Rule 8 governs all problem reporting. Whether the issue blocks execution (error) or suggests improvement (warning), the same matter-of-fact tone and three-part structure applies.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}