How to Add the i-have-adhd Plugin to AI Assistant Marketplaces: Complete Guide for Claude, Codex, OpenCode, and More

Publish the i-have-adhd plugin to any supported AI assistant marketplace by submitting the corresponding runtime-specific manifest file that points to the canonical skill definition at skills/i-have-adhd/SKILL.md.

The ayghri/i-have-adhd repository provides ADHD-friendly response formatting for AI assistants through a single source-of-truth skill definition. Adding this plugin to different marketplaces requires understanding which manifest file each runtime expects. This guide walks through the exact steps, file paths, and validation commands for every supported platform.

How the i-have-adhd Plugin Architecture Works

All marketplaces ultimately load the same core skill. The repository structure separates the canonical rules from runtime-specific adapters:

• skills/i-have-adhd/SKILL.md — The single source of truth containing the ADHD-friendly response guidelines
• Marketplace manifests — JSON files that describe the plugin to each platform's registry
• Runtime scripts — Optional JavaScript modules for advanced integrations (e.g., OpenCode's always-on mode)

This architecture means you maintain one skill definition while distributing through multiple channels.

Adding the Plugin to Claude Code

The Claude Code integration uses .claude-plugin/marketplace.json to define the plugin metadata.

File Structure

// .claude-plugin/marketplace.json
{
  "$schema": "https://claude.ai/schemas/plugin-manifest.json",
  "name": "i-have-adhd",
  "description": "ADHD-friendly response formatting for Claude Code",
  "source": "../skills/i-have-adhd",
  "category": "accessibility"
}

Installation Steps

1. Validate the manifest locally:

claude plugin validate .

2. Add to the Claude Code marketplace:

claude plugin marketplace add ./ .claude-plugin/marketplace.json

3. Users install with:

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

Optional Always-On Mode

Create a flag file to enable system-wide:

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

Adding the Plugin to Codex

The Codex implementation uses .codex-plugin/plugin.json with extended UI metadata.

Key Configuration

// .codex-plugin/plugin.json
{
  "name": "i-have-adhd",
  "skills": "../skills/i-have-adhd",
  "interface": {
    "description": "ADHD-friendly formatting for Codex responses"
  }
}

Publication Steps

# Validate before publishing

codex plugin validate .

# Publish to marketplace

codex plugin publish ./.codex-plugin/plugin.json

Users install with codex plugin install i-have-adhd.

Adding the Plugin to OpenCode

OpenCode requires two files: opencode.json for registration and .opencode/plugins/i-have-adhd.mjs for runtime behavior.

Registration File

// opencode.json
{
  "plugins": [
    "./.opencode/plugins/i-have-adhd.mjs"
  ]
}

Runtime Script

The .opencode/plugins/i-have-adhd.mjs file (lines 15-78) handles:

• Skill directory registration
• Always-on system prompt injection (lines 55-78)

Installation Commands

# Install the plugin

opencode plugin install .

# Enable always-on mode permanently

touch ~/.config/opencode/.i-have-adhd-always

Users can also trigger manually with the /i-have-adhd command.

Adding the Plugin to Kimi

Kimi uses a minimal manifest at kimi.plugin.json.

Publication Steps

# Validate

kimi plugin validate .

# Submit to marketplace

kimi plugin publish ./kimi.plugin.json

Installation: kimi plugin add i-have-adhd.

Adding the Plugin to Gemini

Gemini's extension points to a supplemental markdown description.

Key Files

• gemini-extension.json — Marketplace descriptor
• GEMINI.md — Runtime behavior documentation

Commands

gemini extension validate .
gemini extension add ./gemini-extension.json

Users enable with gemini extension install i-have-adhd.

Adding the Plugin to Qwen

Qwen references the skills folder directly through qwen-extension.json.

qwen extension validate .
qwen extension add ./qwen-extension.json

Cross-Platform Feature: Always-On Mode

Two implementations support persistent activation without explicit commands:

Platform	Activation Method	File/Path
Claude Code	Flag file	~/.claude/.i-have-adhd-always
OpenCode	Flag file + JS implementation	~/.config/opencode/.i-have-adhd-always + lines 55-78 of .opencode/plugins/i-have-adhd.mjs

The OpenCode implementation is more sophisticated—its JavaScript runtime actively injects the ADHD-friendly prompt into every interaction when the flag file exists.

Quick Reference: All Validation Commands

# Claude Code

claude plugin validate .

# Codex

codex plugin validate .

# OpenCode

opencode plugin install .

# Kimi

kimi plugin validate .

# Gemini

gemini extension validate .

# Qwen

qwen extension validate .

Summary

• One skill, many markets: All platforms read from skills/i-have-adhd/SKILL.md through their respective manifests
• Claude Code: Use .claude-plugin/marketplace.json with optional flag-file always-on mode
• Codex: Publish via .codex-plugin/plugin.json with rich UI metadata
• OpenCode: Most complex integration requiring opencode.json + .mjs runtime script with always-on hook
• Kimi, Gemini, Qwen: Single JSON manifests with platform-specific schemas

Frequently Asked Questions

What file do I edit to change the plugin's behavior across all marketplaces?

Edit skills/i-have-adhd/SKILL.md. This is the single source of truth. All marketplace manifests point to this file, so changes propagate automatically to every runtime.

Why does OpenCode require a JavaScript file while other platforms use only JSON?

OpenCode's .opencode/plugins/i-have-adhd.mjs implements the always-on system prompt injection (lines 55-78). This runtime code actively modifies prompts on every interaction when enabled. Other platforms either lack this feature or implement it through flag files interpreted by their core runtime.

Can I use the i-have-adhd plugin without publishing to a marketplace?

Yes. For local development or private use, point your AI assistant's configuration directly to the skills/i-have-adhd directory. Each platform supports local plugin loading—consult the specific CLI documentation for install commands that accept local paths rather than registry names.

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