How to Install i-have-adhd on Other AI Coding Assistants: A Complete Guide

Install the i-have-adhd skill by adding the repository to your assistant's marketplace or skills directory, then activate it via slash command or enable it permanently with an always-on flag.

The i-have-adhd repository by ayghri provides a portable Agent Skill that restructures LLM output for readers with ADHD, prioritizing action items and reducing cognitive load. Unlike traditional libraries that require imports, this skill integrates directly into the assistant's prompting layer through declarative configuration files. Understanding how to install i-have-adhd on different AI coding assistants requires knowing each platform's specific skill-loading mechanism.

What is the i-have-adhd Agent Skill?

The skill functions as a behavioral modifier that the assistant loads at runtime. Its core definition lives in skills/i-have-adhd/SKILL.md, a YAML front-matter file containing the skill name, description, licensing, and complete output-style rules.

When activated, the skill prepends specific formatting instructions to the system prompt, ensuring responses follow ADHD-friendly patterns: bullet points over paragraphs, clear action items first, and chunked information delivery. All supported assistants ultimately reference this single source of truth in SKILL.md, guaranteeing consistent behavior across environments.

Installation Methods for Each AI Assistant

Each assistant uses a distinct plugin/skill-loader to discover and activate the skill. Below are the exact commands and workflows for every supported platform.

Claude Code

Claude Code uses a plugin marketplace system. The plugin.json file in the repository root registers the skill with Claude's plugin manager.

claude plugin marketplace add ayghri/i-have-adhd
claude plugin install i-have-adhd@i-have-adhd

After installation, invoke the skill on-demand:

/i-have-adhd

To enable permanently, create the always-on flag file:

touch ~/.claude/.i-have-adhd-always

Codex

Codex follows a similar marketplace pattern but uses different CLI commands. The same plugin.json file serves as the entry point, alongside SKILL.md.

codex plugin marketplace add ayghri/i-have-adhd --ref main
codex plugin add i-have-adhd@i-have-adhd

Activate with the dollar-sign prefix command:

$i-have-adhd

Zed

Zed consumes skills directly through its Skills manager, reading the SKILL.md file without requiring marketplace intermediaries.

GUI Method:

1. Open Skills → Create skill from URL
2. Paste https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md
3. Save to User or Project scope
4. Invoke /i-have-adhd in the Agent Panel

Manual Method: Copy the skills/i-have-adhd folder into ~/.config/zed/skills/.

Hermes

Hermes provides a dedicated skills CLI that pulls and stores the repository under ~/.hermes/skills/.

hermes skills install ayghri/i-have-adhd/skills/i-have-adhd

Once installed, trigger with:

/i-have-adhd

Gemini CLI

Gemini CLI offers two integration routes: a command file for on-demand usage or an extension for permanent installation.

Command Route (On-Demand): Uses the agents/gemini.toml configuration file:

mkdir -p ~/.gemini/commands
curl -fsSL https://raw.githubusercontent.com/ayghri/i-have-adhd/main/skills/i-have-adhd/agents/gemini.toml \
  -o ~/.gemini/commands/i-have-adhd.toml

Then invoke with /i-have-adhd.

Extension Route (Always-On):

gemini extensions install https://github.com/ayghri/i-have-adhd

Antigravity (agy)

Antigravity installs the entire repository as a plugin, using a manifest in the repo root to locate the skill folder.

agy plugin install https://github.com/ayghri/i-have-adhd
agy plugin list

Cursor, OpenCode, and Other Harnesses

For assistants supporting the generic npx skills CLI, use the universal installer. The skill copies to the agent's scan directory (e.g., ~/.cursor/skills/ or ~/.opencode/skills/).

For Cursor:

npx skills add ayghri/i-have-adhd -a cursor -y

For OpenCode:

npx skills add ayghri/i-have-adhd -a opencode -y

Verify installation:

npx skills list

Invoke with:

/i-have-adhd

Key Files and Architecture

Understanding these source files helps troubleshoot installation issues across different assistants.

File	Purpose
skills/i-have-adhd/SKILL.md	Primary skill definition containing YAML front-matter with output rules and metadata
INSTALL.md	Centralized documentation with human-readable instructions for all platforms
plugin.json	Claude Code marketplace manifest that registers the skill
skills/i-have-adhd/agents/gemini.toml	Gemini CLI command configuration for the on-demand installation route
skills/i-have-adhd/agents/openai.yaml	OpenAI-based agent entry point for assistants like OpenCode

All paths are relative to the repository root at ayghri/i-have-adhd.

Summary

• The i-have-adhd skill modifies LLM output style through skills/i-have-adhd/SKILL.md, not traditional code imports
• Claude Code and Codex use marketplace plugins with plugin.json as the entry point
• Zed consumes the raw SKILL.md URL or local folder directly
• Hermes provides a dedicated CLI (hermes skills install) for skill management
• Gemini CLI supports both command files (gemini.toml) and permanent extensions
• Generic assistants (Cursor, OpenCode) use the npx skills add CLI with the -a flag to specify the target agent
• Always-on mode varies by platform: flag files (Claude), extensions (Gemini), or persistent rule sets

Frequently Asked Questions

What makes i-have-adhd different from a regular VS Code extension?

The i-have-adhd skill operates at the prompt level, not the IDE level. According to the repository source code, it works by prepending formatting rules to the system prompt sent to the LLM, whereas VS Code extensions typically modify the editor UI or provide code snippets. This ensures the ADHD-friendly formatting applies to the AI's actual responses regardless of which IDE you use.

Can I use the skill on multiple assistants simultaneously?

Yes. Since the canonical rules live in skills/i-have-adhd/SKILL.md, you can install the skill on Claude Code, Cursor, and Zed simultaneously without version conflicts. Each assistant reads the same rule definitions, ensuring consistent output formatting across your entire development workflow.

How do I uninstall the skill if I no longer need it?

Reverse the installation command for your specific assistant. For Claude Code, use claude plugin uninstall i-have-adhd@i-have-adhd and remove ~/.claude/.i-have-adhd-always if present. For Hermes, use hermes skills uninstall i-have-adhd. For npx-based installs, run npx skills remove i-have-adhd -a <agent>. Zed users simply delete the skill from the Skills manager or remove the folder from ~/.config/zed/skills/.

Does the skill work with self-hosted or local LLMs?

The skill works with any assistant that supports the Agent Skill protocol or plugin system described in INSTALL.md. If your local LLM setup uses Claude Code, Ollama with OpenCode, or another supported harness, the skill will function normally because it modifies the system prompt rather than requiring specific model capabilities.

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