# How the i-have-adhd Skill's Error Handling Rule 8 Differs from Standard Response Formatting > Discover how i have adhd skill's error handling rule 8 provides concise actionable messages unlike standard response formatting. Learn the cause and fix directly. - Repository: [Ayoub Ghriss/i-have-adhd](https://github.com/ayghri/i-have-adhd) - Tags: deep-dive - Published: 2026-07-22 --- **Rule 8 mandates a matter-of-fact tone that strips away apologetic filler and emotional cues, delivering concise, actionable error messages that state the cause and fix directly.** The **i-have-adhd** skill, hosted in the `ayghri/i-have-adhd` repository, defines a strict communication framework designed to reduce cognitive overhead for users with ADHD. While conventional AI assistants rely on empathetic padding to soften bad news, the **skill's error handling rule 8** requires a clinical, structured approach that prioritizes clarity over comfort. This distinction fundamentally changes how runtime failures are communicated to the end user. ## What Standard Response Formatting Looks Like Traditional conversational agents follow a social-emotional protocol when reporting failures. This approach treats errors as interpersonal moments requiring apology and reassurance. Standard formatting typically includes: - **Apologetic preambles** such as "Sorry," "Oops," or "My apologies" - **Vague descriptions** like "There seems to be an issue" or "Something went wrong" - **Emotional interjections** including "Uh-oh," "Oh no," or "Yikes" These elements increase cognitive load by forcing the reader to parse social niceties before extracting technical substance. ## Rule 8's Matter-of-Fact Protocol 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) at line 98, **Rule 8** explicitly forbids expressive interjections. Instead, the rule enforces a three-part factual structure: 1. **Identify the exact failure point** (file path, line number, or error code) 2. **Explain the root cause** in plain, unembellished terms 3. **Provide the corrective action** the user can immediately execute This method aligns with the skill's overarching goal of reducing distraction by eliminating unnecessary filler. ## Practical Comparison: Code Examples The difference becomes clear when comparing responses to identical failure scenarios. ### Test Failure Scenario **Standard (Empathetic) Response:** ```text Uh oh, the test is failing. There seems to be an issue with the authentication. ``` **Rule 8-Compliant Response:** ```text Test fails at `auth.spec.ts:42`: expected 200, got 401. Cause: missing auth header. Fix: add `Authorization: Bearer ${token}` to the request. ``` The Rule 8 version, as documented at line 100 of [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md), delivers the exact file location (`auth.spec.ts:42`), the specific mismatch (expected 200, got 401), and the precise header syntax required for resolution. ### Missing Environment Variable **Standard Response:** ```text Sorry, I can't find the API key. There might be a problem with your setup. ``` **Rule 8 Response:** ```text `API_KEY` is undefined in the environment. Fix: set `API_KEY` in `.env` or export it before running the program. ``` ### Database Connection Error **Standard Response:** ```text Oh no, we can't connect to the database right now. Please try again later. ``` **Rule 8 Response:** ```text Connection to PostgreSQL on `localhost:5432` failed: timeout after 10s. Fix: ensure the database server is running and reachable, or increase the timeout setting. ``` ## Implementation Architecture The rule set is registered through [`plugin.json`](https://github.com/ayghri/i-have-adhd/blob/main/plugin.json), which enables the Instagit platform to apply these formatting constraints to runtime responses. The full specification resides in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md), while [`README.md`](https://github.com/ayghri/i-have-adhd/blob/main/README.md) provides the high-level repository overview and entry point for developers integrating the skill. ## Summary - **Rule 8** requires **matter-of-fact error handling** that eliminates apologetic or emotional language. - Standard formatting uses **empathetic padding** ("Sorry," "Oops") that increases cognitive load. - Rule 8 messages follow a **three-part structure**: failure point identification, root cause explanation, and corrective action. - This approach is defined in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) and registered via [`plugin.json`](https://github.com/ayghri/i-have-adhd/blob/main/plugin.json) in the `ayghri/i-have-adhd` repository. ## Frequently Asked Questions ### Why does Rule 8 prohibit apologetic language in error messages? Apologetic phrases and emotional cues force users to process social context before extracting technical information. For individuals with ADHD, this additional parsing step creates unnecessary cognitive friction. Rule 8 eliminates this overhead by delivering raw, actionable data immediately. ### Where is Rule 8 defined in the i-have-adhd repository? Rule 8 is formally defined in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) at line 98, with concrete examples provided at line 100. The skill itself is registered in the Instagit platform through the [`plugin.json`](https://github.com/ayghri/i-have-adhd/blob/main/plugin.json) file at the repository root. ### How does matter-of-fact error handling improve debugging speed? By stating the exact failure location (file and line number), the specific cause (e.g., "missing auth header"), and the precise fix (e.g., exact syntax for headers), Rule 8 removes ambiguity. Users spend zero seconds interpreting tone and can immediately execute the corrective action. ### Can Rule 8 be applied to other conversational AI systems? Yes. While the `ayghri/i-have-adhd` repository implements this via the Instagit skill framework, the formatting principle—replacing vague empathy with structured, factual reporting—is system-agnostic and can be enforced in any prompt engineering or response templating layer.