Entry Points for the i-Have-ADHD Skill Across Claude Code, Codex, and Gemini CLI

The i-have-adhd repository defines platform-specific entry points through JSON manifests—.claude-plugin/plugin.json, .codex-plugin/plugin.json, and gemini-extension.json—that bootstrap the skill across Claude Code, Codex, and Gemini CLI runtimes.

The ayghri/i-have-adhd open-source repository implements a single skill that adapts to multiple AI platform runtimes. Understanding these i-have-adhd skill entry points is essential for developers who want to extend or debug the behavior across Claude Code, Codex, and Gemini CLI environments.

Claude Code Entry Point

Claude Code loads the skill via .claude-plugin/plugin.json, which serves as the primary manifest. This JSON file declares the skill metadata including name, version, and description.

When Claude Code initializes the plugin, it reads the manifest and executes the always-on hook defined in hooks/always-on.mjs. The hook registration is managed through the shared configuration in hooks/hooks.json.

// Illustrative loading pattern used by Claude Code runtime
import { loadPlugin } from 'claude-runtime';
await loadPlugin('.claude-plugin/plugin.json');

Codex Entry Point

Codex uses .codex-plugin/plugin.json as its plugin descriptor. According to the repository source code, this manifest is generated from the same data as the Claude manifest, ensuring consistency across platforms.

Codex additionally consults .agents/plugins/marketplace.json to make the skill discoverable in the marketplace, while applying the generic hook configuration from hooks/hooks.json.

// Codex runtime automatically registers the skill from marketplace.json
import { getSkill } from 'codex-runtime';
const adhdSkill = await getSkill('i-have-adhd');
adhdSkill.run({ input: 'Explain the next steps.' });

Gemini CLI Entry Point

The Gemini CLI identifies the skill through gemini-extension.json, which functions as the platform's extension descriptor. This file instructs the Gemini runtime how to load and execute the skill.

Platform-specific behavior and command-line flags are documented in GEMINI.md, which accompanies the extension manifest.

gemini run i-have-adhd --prompt "Summarize the last meeting."

Shared Core Skill Definition

All three runtimes reference the same canonical behavior defined in skills/i-have-adhd/SKILL.md. The platform-specific manifest files merely point to this source file and register the plugin with their respective runtimes. This architecture ensures that updates to the core skill logic propagate consistently across Claude Code, Codex, and Gemini CLI without requiring individual platform modifications.

Summary

• Claude Code uses .claude-plugin/plugin.json with hooks/always-on.mjs for runtime registration.
• Codex relies on .codex-plugin/plugin.json plus .agents/plugins/marketplace.json for marketplace discovery.
• Gemini CLI consumes gemini-extension.json and GEMINI.md for extension loading and documentation.
• All platforms share the core logic defined in skills/i-have-adhd/SKILL.md.

Frequently Asked Questions

What is the main source file for the i-have-adhd skill logic?

The canonical skill behavior resides in skills/i-have-adhd/SKILL.md. All platform manifests—including those for Claude Code, Codex, and Gemini CLI—point to this single source of truth, ensuring consistent functionality across different AI runtimes.

How does Claude Code bootstrap the skill differently from Codex?

While both platforms use JSON manifests and share hooks/hooks.json, Claude Code specifically executes hooks/always-on.mjs to register the skill at runtime. Codex alternatively relies on .agents/plugins/marketplace.json for skill discovery and marketplace registration, making the entry point workflow distinct between the two platforms.

Where is Gemini-specific configuration documented?

Gemini CLI-specific behavior, command-line flags, and usage instructions are documented in GEMINI.md. This file accompanies the gemini-extension.json manifest and provides platform-specific guidance that supplements the core skill definition.

Can the same hooks be used for both Claude Code and Codex?

Yes, both Claude Code and Codex reference hooks/hooks.json for shared hook configuration. However, Claude Code additionally requires hooks/always-on.mjs for always-on initialization, whereas Codex integrates with .agents/plugins/marketplace.json for marketplace visibility, meaning the complete hook setup is platform-specific despite shared components.

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