How to Tune the i-have-adhd Skill by Forking and Swapping in a Custom Ruleset

You can tune the i-have-adhd skill by forking the ayghri/i-have-adhd repository, editing the skills/i-have-adhd/SKILL.md file to customize the 10 core rules, and swapping the upstream Claude plugin for your fork using the claude plugin CLI commands documented in the README.

The i-have-adhd skill controls Claude's communication style through a centralized markdown configuration rather than scattered code files. This architecture makes it possible to tune the skill by forking and swapping in a custom ruleset without modifying the assistant's core logic. All behavioral changes—from rule phrasing to metadata categorization—live in a single file that you can edit and publish as a replacement plugin.

Understanding the Ruleset Architecture Before Forking

Every response generated by the /i-have-adhd command follows the 10 core rules defined in skills/i-have-adhd/SKILL.md. According to the ayghri/i-have-adhd source code, this file contains both the skill metadata (lines 2-9) and the behavioral rules that shape output style.

The metadata block includes metadata.tags and metadata.category, which are parsed when the plugin loads. Because these properties live inside SKILL.md, any changes you make to them—such as updating categories or adding descriptive tags—automatically reflect in the plugin marketplace listing. The file AGENTS.md maps these runtime entry points, but you do not need to edit it to change the skill's behavior; SKILL.md is the only file that requires modification to alter the ruleset.

Fork and Customize Your Ruleset

Fork the Repository

Start by creating your own copy of the repository on GitHub. You can use the GitHub web interface or the CLI to fork ayghri/i-have-adhd to your personal account.

Edit the Rules in SKILL.md

Once cloned locally, open skills/i-have-adhd/SKILL.md in your preferred editor. This file contains the canonical definition of the ADHD-friendly rules. You can:

• Modify the existing 10 rules to change phrasing or constraints
• Adjust the numbering style or formatting
• Update the metadata headers (lines 2-9) to change tags or category

For example, to change how the skill structures lists or emphasizes key points, edit the relevant rule descriptions in the markdown body.

Commit and Push Changes

After editing, commit your custom ruleset and push it to your fork:

git clone https://github.com/<your-username>/i-have-adhd.git
cd i-have-adhd

# Edit the ruleset

nano skills/i-have-adhd/SKILL.md

# Commit and push your changes

git add skills/i-have-adhd/SKILL.md
git commit -m "Custom rule set for i-have-adhd"
git push origin main

Swap the Upstream Plugin for Your Forked Ruleset

With your custom ruleset published to your fork, you must replace the upstream plugin with your version. The README.md file (lines 82-92) documents the exact sequence of claude plugin CLI commands required to perform this swap.

Execute the following commands to uninstall the original and install your custom version:

# Remove the upstream copy

claude plugin uninstall i-have-adhd

# Remove the original marketplace entry

claude plugin marketplace remove i-have-adhd

# Add your fork as the new source

claude plugin marketplace add <your-username>/i-have-adhd

# Install the custom version

claude plugin install i-have-adhd@i-have-adhd

This procedure ensures that the next time you invoke the skill, Claude loads your ruleset instead of the default one.

Verify Your Custom Rules Are Active

To confirm that your forked ruleset is in effect, invoke the skill in Claude Code:

/i-have-adhd

The first response should now follow the specific rules, phrasing, and constraints you defined in your forked SKILL.md. If the output reflects your modifications—such as different bullet styles or additional formatting constraints—your custom plugin is active.

Summary

• The i-have-adhd skill behavior is controlled entirely by skills/i-have-adhd/SKILL.md, which contains the 10 core rules and metadata.
• To tune the skill, fork the ayghri/i-have-adhd repository and edit SKILL.md to customize the ruleset.
• Push your changes to GitHub, then use the claude plugin CLI (as documented in README.md lines 82-92) to uninstall the upstream version and install your fork.
• Metadata changes made in SKILL.md (lines 2-9) automatically update the plugin's categorization when loaded.
• No modifications to AGENTS.md or core assistant code are required to customize the skill's output.

Frequently Asked Questions

Do I need to modify any files other than SKILL.md?

No. According to the repository structure, skills/i-have-adhd/SKILL.md is the only file you need to edit to change the skill's behavior. While AGENTS.md defines runtime entry points and README.md provides installation instructions, all behavioral rules and metadata live inside SKILL.md.

Will changing the metadata in SKILL.md affect how the plugin is categorized?

Yes. The metadata block at lines 2-9 of SKILL.md includes metadata.tags and metadata.category. When you modify these values and reinstall the plugin from your fork, the updated metadata automatically reflects in the plugin listing and categorization.

Can I share my forked ruleset with other users?

Yes. Once you push your custom SKILL.md to a public GitHub repository, other users can add your fork to their marketplace using claude plugin marketplace add <your-username>/i-have-adhd and install it. This allows teams to distribute standardized communication styles across multiple Claude installations.

How do I revert to the original upstream skill?

To revert, uninstall your custom plugin using claude plugin uninstall i-have-adhd, remove your fork from the marketplace with claude plugin marketplace remove <your-username>/i-have-adhd, then re-add the original source (ayghri/i-have-adhd) and reinstall. The commands in README.md lines 82-92 provide the template for reversing the swap procedure.

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