# Rule 7 Make Wins Visible: Technical Implementation in the i-have-adhd Skill

> Learn how to make wins visible for ADHD users with Rule 7 in the i-have-adhd skill. Discover technical implementation for dopamine reinforcement and success confirmation.

- Repository: [Ayoub Ghriss/i-have-adhd](https://github.com/ayghri/i-have-adhd)
- Tags: deep-dive
- Published: 2026-08-21

---

**Rule 7 requires surfacing completed work immediately at the end of a response to provide dopamine reinforcement and clear confirmation of success for users with ADHD.**

The `ayghri/i-have-adhd` open-source repository defines a specialized Cursor skill that optimizes technical communication for neurodivergent developers. Rule 7 Make Wins Visible serves as one of ten core formatting guidelines that shape how the skill structures successful task completion. 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), this rule specifically prohibits burying successes in recaps and mandates explicit, concrete confirmation of functional outcomes.

## What is Rule 7 Make Wins Visible?

Rule 7 Make Wins Visible is a formatting constraint defined in the i-have-adhd skill that requires the AI to physically surface successful task completion at the end of every response. As implemented in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) (lines 89-95), the rule states: "Show what now works, in concrete terms. Do not bury wins in a recap."

This guideline exists to counter the default tendency toward lengthy summaries that force readers with ADHD to parse through text to find confirmation of success. Instead, Rule 7 mandates immediate visual confirmation followed by actionable verification steps.

## The Three Goals of Rule 7

The implementation of Rule 7 Make Wins Visible targets three specific cognitive accessibility requirements:

### Immediate Dopamine Reinforcement

By stating the new functional state in concrete terms—such as "Login now works with magic links"—the rule provides an immediate dopamine-boosting cue. This neurological reward signal confirms that the effort produced a tangible outcome, which is critical for maintaining motivation in ADHD users.

### Clarity of Outcome

The rule requires specific, testable phrasing that tells the user exactly what to observe next. Rather than vague confirmations, implementations must include commands like `Try: npm run dev, open /login` that eliminate ambiguity about what changed.

### Reduced Memory Burden

Since ADHD limits working memory capacity, explicitly naming the completed win prevents the need to mentally track changes during the interaction. The visible win statement acts as an external memory anchor, allowing the user to focus on the next task without retaining the previous context.

## Source Code Location

The canonical definition of Rule 7 resides in the skill's primary documentation file:

**File:** [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md)  
**Lines:** 89-95  
**Repository:** `ayghri/i-have-adhd`

A Cursor-compatible mirror exists at [`.cursor/skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/.cursor/skills/i-have-adhd/SKILL.md), which remains synchronized with the canonical definition. Both files contain the identical constraint: "Show what now works, in concrete terms. Do not bury wins in a recap."

## Implementation Pattern and Examples

When applying Rule 7 Make Wins Visible, responses must follow a strict two-part structure: a visible win statement marked with ✅ and a concrete verification command.

The pattern requires:

1. **✅ Visible win statement** – Concise, positive, present-tense confirmation in bold
2. **Verification command** – Short, runnable instruction that proves the win

### Authentication Fix Example

```markdown
<!-- After fixing authentication -->
✅ **Login now works with magic links.**  
Try it: `npm run dev` and open `http://localhost:3000/login`.

```

### Configuration Update Example

```markdown
<!-- After updating a configuration file -->
✅ **Feature flag X is enabled.**  
Check it by reloading the page and looking for the new UI element.

```

### Database Migration Example

```markdown
<!-- After a database migration -->
✅ **User table now includes the `last_login` column.**  
Run `SELECT last_login FROM users LIMIT 5;` to see recent timestamps.

```

## Summary

- **Rule 7 Make Wins Visible** is defined in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) (lines 89-95) as a core formatting requirement for the i-have-adhd skill.
- The rule mandates **immediate concrete confirmation** of successful task completion, prohibiting burial of successes within recaps.
- Implementation follows a **two-part pattern**: a ✅ marked visible win statement followed by a specific verification command.
- The goal serves **triple cognitive support**: dopamine reinforcement, outcome clarity, and reduced working memory load for ADHD users.
- All ten rules in the skill aim to reduce cognitive load, but Rule 7 specifically targets the **confirmation phase** of technical interactions.

## Frequently Asked Questions

### Where is Rule 7 Make Wins Visible defined in the repository?

Rule 7 is defined in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) at lines 89-95, with a synchronized copy maintained at [`.cursor/skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/.cursor/skills/i-have-adhd/SKILL.md) for Cursor IDE compatibility. The source text explicitly states to "Show what now works, in concrete terms" and warns against burying wins in recaps.

### Why does Rule 7 emphasize concrete terms over general success messages?

Concrete terms eliminate ambiguity that creates cognitive load for ADHD users. Specific phrases like "Login now works with magic links" provide immediate context and dopamine reinforcement, whereas vague confirmations like "The task is complete" force the reader to search for meaning, increasing working memory burden.

### What is the correct format for implementing Rule 7 in a response?

The correct format consists of two elements: first, a ✅ symbol followed by a **bold, present-tense statement** of what now functions, and second, a **runnable verification command** that proves the success. This pattern appears in the [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md) source as the standard for all task completions within the i-have-adhd skill.

### How does Rule 7 differ from other rules in the i-have-adhd skill?

While other rules in the `ayghri/i-have-adhd` repository focus on breaking down complex tasks or limiting paragraph length, Rule 7 specifically governs the **termination** of an interaction. It ensures the final moments of any exchange provide immediate positive reinforcement, whereas preceding rules typically structure the process of getting to that endpoint.