How Should Errors Be Handled According to Rule 8: Matter‑of‑Fact Error Reporting

Rule 8 requires eliminating apologetic or emotive language and instead delivering a direct statement of the failure cause paired with the exact fix required.

The ayghri/i-have-adhd skill enforces a strict protocol for how errors be handled according to Rule 8, ensuring that failure messages serve as compact, actionable instructions. This guideline appears in the skill definition file and mandates a matter‑of‑fact tone that minimizes cognitive overhead. By stripping away ambiguity and emotional padding, the rule allows developers—particularly those with ADHD—to diagnose and resolve issues without unnecessary mental load.

The Philosophy Behind Rule 8’s Matter‑of‑Fact Tone

Source Definition in SKILL.md

According to the source code in [skills/i-have-adhd/SKILL.md](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md#L98) at line 98, the section titled "### 8. Matter‑of‑fact tone for errors" establishes the requirement that error responses must directly state the cause of the failure and the exact fix rather than using informal or apologetic language.

The Three Pillars of Rule 8 Error Handling

1. Eliminate Soft Language

The rule strictly forbids emotive interjections such as "Uh oh," "Oh no," or "There seems to be a problem." These phrases introduce ambiguity and force the reader to parse emotional content before reaching technical substance.

2. State the Precise Cause

Error messages must identify the specific file, line number, or condition that triggered the failure. This precision removes guesswork and allows immediate localization of the issue.

3. Present the Concrete Fix

Every error report must conclude with the exact code change, configuration tweak, or terminal command required to resolve the issue, enabling single-step remediation.

Practical Examples: Correct vs. Incorrect Error Handling

Here are three scenarios demonstrating how to apply Rule 8 when handling errors in the i‑have‑adhd workflow.

Test Failure Scenario

Incorrect (violates Rule 8):

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

Correct (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.

Missing Environment Variable

Incorrect:

Oh no, we can't find the API key.

Correct:

Missing environment variable API_KEY in .env. Fix: add API_KEY=your_key_here to the .env file and reload the process.

Database Migration Error

Incorrect:

There seems to be a problem applying the migration.

Correct:

Migration error: column `user_id` already exists in table `orders`. Cause: duplicate migration run. Fix: rollback the last migration (`npm run migrate:down`) and remove the duplicated file.

Implementation Across the Repository

The matter‑of‑fact error handling defined in Rule 8 is enforced through several key files in the ayghri/i-have-adhd repository:

• skills/i-have-adhd/SKILL.md – Contains the complete rule set, including the specific line 98 reference to Rule 8’s error‑handling guidelines.
• evals/rubric.md – Defines evaluation criteria that enforce the matter‑of‑fact error style during skill assessment.
• extensions/i-have-adhd.ts – Implements the skill’s runtime behavior, where error messages are generated according to these strict guidelines.
• README.md – Provides the high‑level overview of the skill and references the complete rule list.

Summary

• Errors be handled according to Rule 8 by removing all apologetic or emotional language from failure messages.
• The rule requires stating the precise technical cause, including file paths and line numbers when applicable.
• Every error must provide an immediate, actionable fix that the user can execute in a single step.
• This approach reduces working‑memory demands and supports neurodivergent developers by eliminating cognitive friction.

Frequently Asked Questions

What exactly is Rule 8 in the i‑have‑adhd skill?

Rule 8 is a guideline defined in skills/i-have-adhd/SKILL.md that mandates a matter‑of‑fact tone for all error reporting. It requires that failure messages state the exact cause and the specific fix without using soft language or emotional padding.

Why does Rule 8 prohibit phrases like "Uh oh" or "Oh no"?

These phrases increase cognitive load by forcing the reader to process emotional content before accessing technical information. For developers with ADHD, this extra parsing step creates unnecessary friction and delays action.

Where is Rule 8 defined in the repository?

Rule 8 is explicitly defined at line 98 in [skills/i-have-adhd/SKILL.md](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md#L98) under the section "### 8. Matter‑of‑fact tone for errors". The rule is also enforced in evals/rubric.md and implemented in extensions/i-have-adhd.ts.

How does Rule 8 reduce cognitive load for developers with ADHD?

By presenting errors as compact, factual statements with immediate solutions, Rule 8 minimizes working‑memory demands. Readers do not need to interpret tone or search for remediation steps; they can act instantly on the provided fix.

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