i-have-adhd: readable responses, adapters and evidence
Install and distribute i-have-adhd without confusing host configuration
Distinguish a Markdown skill from executable adapters, pin the reviewed revision and plan a narrow rollback before global installation.
What you will learn
- Deployment means assistant integration here
- Review the files before changing a shared environment
- Acceptance includes loading, behavior and recovery
Before you start
- Basic Git and command-line knowledge
- Ability to separate observed behavior from an untested claim
Explain the inspected mechanism, plan a reversible trial and interpret evidence without treating style as correctness.
Key takeaways
- A Markdown import and an executable plugin are different deployments.
- Do not infer a public npm package from package.json.
- A rollback should target only the changes you introduced.
Deployment means assistant integration here
This project is not a web service requiring a database, container cluster or public port. Deployment means making a reviewed skill or adapter discoverable to a particular assistant. The repository contains several manifests, hooks and extension entry points; their presence does not prove that every current host version accepts the same installation command.
Use the pinned INSTALL.md section for the host you actually operate, and check its prerequisites and verification step. Some documented integrations are explicitly untested. Treat those as proposed procedures until verified locally. A manually imported Markdown file also has a different execution surface from a plugin that launches Node code at session startup.
Review the files before changing a shared environment
Record the exact Git revision before reviewing the canonical skill, plugin manifest and any executable entry point. package.json declares private and has Pi/OMP metadata; do not invent an npm install route from its name. For a managed team, distribute an approved revision through the host-supported mechanism and document which files are included.
The Node hook uses CLAUDE_CONFIG_DIR or a default Claude configuration directory for its marker. The OpenCode adapter uses XDG_CONFIG_HOME or its own default configuration directory. Copying an opt-in marker from one host to another is not a portable activation procedure. Check actual source and host documentation rather than assuming every plugin uses a shared switch.
Acceptance includes loading, behavior and recovery
Separate three checks: the host discovers the plugin, the intended rules reach a controlled conversation, and disabling or rolling back removes future activation. A plugin-list entry verifies only the first. Our fixtures execute source components directly and do not certify the host discovery step, the host API version or the model response.
Keep the previous approved revision and a record of changed configuration keys. Roll back only the specific plugin entry or opt-in setting you introduced, then begin a fresh session. Do not erase an entire assistant configuration directory. No global installation, provider request or user configuration change was performed for this series.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Select the host-specific pinned installation section.
- 2
Inspect the manifest, rules and executable entries.
- 3
Trial the integration in a disposable profile.
- 4
Record discovery, behavior and rollback checks separately.
Copy-ready example
# In a checkout you have already reviewed; read-only checks.
git rev-parse HEAD
git show 6f1f982d0a47c65899af3c5a7450b7098bc65325:package.json
git show 6f1f982d0a47c65899af3c5a7450b7098bc65325:hooks/hooks.jsonFrequently asked questions
Is Docker required?
No server deployment is established by this project structure; it integrates with assistant hosts.
Can the offline fixture certify all hosts?
No. It does not exercise host discovery or host APIs in a running assistant.
Sources
- i-have-adhd / INSTALL.mdSource checked 2026-09-12
- i-have-adhd / package.jsonSource checked 2026-09-12
- i-have-adhd / hooks/hooks.jsonSource checked 2026-09-12
- i-have-adhd / .codex-plugin/plugin.jsonSource checked 2026-09-12