# Forbidden Phrases in i-have-adhd: Rule 10 and the No-Fluff Policy > Discover forbidden phrases in i-have-adhd's Rule 10. Learn how to bypass preambles, recaps, and closers to deliver direct, actionable content. Maximize clarity and efficiency. - Repository: [Ayoub Ghriss/i-have-adhd](https://github.com/ayghri/i-have-adhd) - Tags: deep-dive - Published: 2026-08-08 --- **The i-have-adhd skill explicitly forbids any preamble, recap, or closing phrasing, requiring responses to jump directly into actionable content without greetings, summaries, or sign-offs.** The *i-have-adhd* repository enforces a strict **"no-fluff"** communication protocol designed to eliminate cognitive overhead for users. According to the source code, **Rule 10** in the skill definition mandates that all responses must avoid forbidden phrases that function as conversational padding. This constraint is implemented across multiple configuration files to ensure consistent, direct output. ## The Rule 10 Constraint Rule 10 is the central governing principle that defines the **forbidden phrases in i-have-adhd**. Rather than maintaining a static blacklist of words, the rule prohibits any linguistic construction that serves as a preamble, recap, or closer. The constraint is documented verbatim in three critical locations: - **[`skills/i-have-adhd/agents/gemini.toml`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/agents/gemini.toml)** (lines 5-21): The agent-specific prompt reiterates the "no preamble/recap/closer" directive. - **[`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md)** (lines 107-113): The central skill definition includes Rule 10 as a numbered item. - **[`README.md`](https://github.com/ayghri/i-have-adhd/blob/main/README.md)** (lines 70-76): The repository-level summary echoes the same constraint for contributors. Because the rule is phrased as "No preamble, no recap, no closers," the system evaluates intent rather than specific vocabulary. Any wording that functions as a greeting, thank-you, summary, or sign-off is considered forbidden. ## Categories of Forbidden Phrases The forbidden phrases in i-have-adhd fall into three distinct functional categories. The following examples illustrate typical violations, though this is not an exhaustive list. ### Preambles and Greetings Opening pleasantances or acknowledgments that delay the core content are prohibited. Common forbidden constructions include: - "Hello," or "Hi there," - "Hey," or "Good morning," - "Thanks for asking," - "I'm happy to help," ### Recaps and Summaries Transitional phrases that restate information already provided waste cognitive resources. Avoid: - "In summary," or "To recap," - "To sum up," or "Overall," - "In short," ### Closers and Sign-offs Any language that signals the end of the conversation or offers further assistance is banned. This includes: - "Thanks!" or "Thank you for your question," - "Hope this helps," - "Let me know if you need anything else," - "Best regards," "Take care," or "Have a great day," ## Implementation in Source Files The enforcement of forbidden phrases is hardcoded into the repository's configuration layer. In [`skills/i-have-adhd/agents/gemini.toml`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/agents/gemini.toml), the system prompt explicitly instructs the model to strip these elements. The [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md) file codifies this as Rule 10 within the skill's behavioral guidelines, while the root [`README.md`](https://github.com/ayghri/i-have-adhd/blob/main/README.md) ensures contributors understand the constraint during development. When any of the prohibited constructions appear in generated output, they are flagged by the skill's output processor and removed before delivery to the user. ## Allowed vs. Forbidden Response Patterns The following examples demonstrate the practical application of Rule 10. **Allowed (strict, no-fluff):** ```markdown 1. Open the Settings menu. 2. Toggle **Enable Notifications**. 3. Click **Save**. Action completed. ``` **Forbidden (contains a preamble):** ```markdown Hi! Here's how you can enable notifications: 1. Open the Settings menu... ``` **Forbidden (contains a recap):** ```markdown To recap, you need to open Settings, toggle the switch, and click Save. ``` **Forbidden (contains a closing):** ```markdown Hope that helps! Let me know if you have any other questions. ``` ## Summary - **Rule 10** in the i-have-adhd skill explicitly bans preambles, recaps, and closers. - Forbidden phrases are defined by function (greetings, summaries, sign-offs) rather than a static word list. - The constraint is documented in [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md), [`gemini.toml`](https://github.com/ayghri/i-have-adhd/blob/main/gemini.toml), and [`README.md`](https://github.com/ayghri/i-have-adhd/blob/main/README.md). - Responses must jump directly into actionable content and end immediately when the task is complete. - Violations include common phrases like "Hello," "In summary," and "Hope this helps." ## Frequently Asked Questions ### Is there a hard-coded list of forbidden words in i-have-adhd? No. 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) and related files, the repository does not maintain a hard-coded list of specific banned words. Instead, Rule 10 forbids any phrasing that functions as a preamble, recap, or closer, regardless of the specific vocabulary used. ### Why does i-have-adhd ban preambles and closers? The skill is designed to minimize cognitive overhead for users with ADHD. By eliminating greetings, summaries, and sign-offs, the responses deliver information density without the "fluff" that typical conversational AI uses, reducing the time and mental effort required to extract actionable content. ### How do I know if my phrase counts as a preamble? If the phrase serves to greet the user, acknowledge their question, or delay the actual answer, it functions as a preamble. The safest approach is to jump straight into the first actionable step or piece of information without any introductory padding. ### Where is Rule 10 documented in the repository? Rule 10 appears in three locations: lines 107-113 of [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md), lines 5-21 of [`skills/i-have-adhd/agents/gemini.toml`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/agents/gemini.toml), and lines 70-76 of the root [`README.md`](https://github.com/ayghri/i-have-adhd/blob/main/README.md). Each file reinforces the "no preamble, no recap, no closers" directive for different contexts (skill definition, agent configuration, and contributor documentation).