i-have-adhd: readable responses, adapters and evidence
Prompt, skill or always-on plugin: choose the smallest useful integration
Compare response-style delivery options by persistence, review surface and rollback rather than unmeasured product rankings.
What you will learn
- Start from the lifetime of the preference
- Compare concrete maintenance responsibilities
- Let the learning task determine the answer shape
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
- Choose persistence to match the recurring need.
- Adapters add lifecycle and compatibility maintenance.
- Different reading intentions require different answer shapes.
Start from the lifetime of the preference
If you need one answer reformatted, a clear instruction in that request can be enough. If a recurring task benefits from a reusable contract, a manually invoked skill can make that contract easier to review. Always-on integration fits a persistent preference only after checking that unrelated tasks, explanations and safety-sensitive work still receive appropriate detail.
These are integration choices, not a leaderboard of assistants. We have not benchmarked competing products or measured which host reads the rules most reliably. The selection question is whether the added persistence and configuration surface solve a recurring problem that simpler delivery has failed to solve.
Compare concrete maintenance responsibilities
An inline instruction has little installation overhead but can drift across conversations. A versioned skill centralizes wording but still needs deliberate activation and revision review. An executable adapter adds event handling and host-version compatibility to that responsibility. A team should know who approves rule changes and how a user can opt out.
The pinned source also shows that more integrations do not imply identical semantics: a startup hook, a per-turn transform and a stateful extension behave differently. Choose a route whose activation and rollback you can observe. A feature list that says a host is supported is less useful than a small, repeatable acceptance test for your actual environment.
Let the learning task determine the answer shape
For troubleshooting, prioritize evidence, one diagnostic step and a way to report the result. For a conceptual lesson, require the mechanism, a concrete example and a boundary case. For a catalogue, preserve every requested item even if you group the display. No single short-answer style should erase the defining content of these tasks.
Trial one integration with a diverse task set before making it a team default. Keep the previous style available and collect concrete complaints such as missing prerequisites or repeated state notices. A personal preference is a valid reason to choose a style, but it should not be advertised as a measured universal productivity improvement.
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
Decide whether the preference lasts one answer or many sessions.
- 2
Compare review and rollback responsibilities.
- 3
Trial troubleshooting, explanation and complete-list tasks.
- 4
Keep an explicit opt-out route.
Copy-ready example
{
"preferenceLifetime": "one-response",
"firstOption": "explicit request",
"alwaysOnRequired": false,
"comparativeBenchmarkExecuted": false
}Frequently asked questions
Is always-on automatically better?
No. It increases persistence and maintenance; a one-off instruction may solve the task with less configuration.
Which competing assistant wins?
This series does not contain a controlled cross-assistant benchmark.
Sources
- i-have-adhd / INSTALL.mdSource checked 2026-09-12
- i-have-adhd / skills/i-have-adhd/SKILL.mdSource checked 2026-09-12
- i-have-adhd / hooks/always-on.mjsSource checked 2026-09-12
- i-have-adhd / .opencode/plugins/i-have-adhd.mjsSource checked 2026-09-12
- i-have-adhd / extensions/i-have-adhd.tsSource checked 2026-09-12