⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
attention-control
Shape output for a reader with ADHD, then write each sentence in controlled English: action first, one word one meaning, active voice, simple tenses, state restated every turn. Invoke with /attention-control; stays on until "stop attention control".
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Install
Claude Code is the only agent here with a native output style slot. Run these two commands in your terminal:
claude plugin marketplace add aaddrick/attention-control
claude plugin install attention-control@attention-control
Then run /config, select Output style, and pick Attention Control. It
takes effect after /clear or the next session.
To skip the picker, add outputStyle to ~/.claude/settings.json. It is a
top-level key. It does not go inside env, permissions, or any other block:
{
"model": "opus",
"env": { "EXAMPLE_VAR": "1" },
"outputStyle": "Attention Control"
}
model and env stand in for keys you may already have. Keep them. Add the
outputStyle line beside them.
For one session instead of every session, use the skill the plugin also ships:
/attention-control:attention-control
Say "stop attention control" to turn it off.
Codex has no output style slot, so the rules ship as a skill.
codex plugin marketplace add aaddrick/attention-control --ref main
codex plugin add attention-control@attention-control
Inside Codex, /plugins opens the plugin browser instead.
Start a new thread, then type the skill:
$attention-control:attention-control
Codex prefixes a plugin skill with the plugin name. Say "stop attention control"
to turn it off. For every turn instead, put the always-on snippet from
INSTALL.md in ~/.codex/AGENTS.md.
See INSTALL.md. None of them has an output style slot, so the
rules ship as a skill, a rules file, or an AGENTS.md block. On a skill route,
type /attention-control and say "stop attention control" to turn it off.
What it does
Air traffic control phraseology exists for one reason: a distracted human under load will mishear an instruction. Aviation solved this with two disciplines. Controlled vocabulary makes each word mean one thing. Fixed message shape puts the instruction first and the background last.
This style applies both disciplines to your coding agent. The agent leads with the action you can run, and writes each sentence so one word means one thing.
The style targets one reader: a reader with ADHD. That reader is where the shape rules come from. See Why the shape rules exist.
What changes
Before
Great question! Let me take a look. It seems like the auth flow has a few moving pieces here. Looking at
src/auth.ts, the token verification logic could possibly be utilizing a deprecated API — theverifyTokenfunction around lines 42-58 has been implemented against an olderjsonwebtokensignature. One approach that might be considered would be updating the package and refactoring that function. By the way, your dependency versions in general could probably use a review at some point. Hope this helps! Let me know if you'd like me to dig deeper into any of this.
After
Run
npm install jsonwebtoken@latest.I changed
src/auth.ts:47.verifyTokennow names the algorithm:
jwt.verify(token, secret, { algorithms: ["HS256"] }, callback);Run
npm test -- auth.spec.ts. It takes about 10 seconds.The old call named no algorithm.
jsonwebtokenv9 rejects an unsigned token unless you passalgorithms: ["none"].Next: paste the first failing line if a test fails.
The two layers
Shape decides what you say and in what order. 11 rules:
- Lead with the next action.
- Do the work you own.
- Number multi-step work.
- End with one concrete next action.
- Suppress tangents.
- Restate state every turn.
- Give time estimates in concrete units.
- Show what now works.
- State errors flat.
- Cap lists at 5 items.
- No preamble, no recap, no closer.
Language decides how each sentence reads. The short version:
- One word, one meaning. One action, one verb. No rotating synonyms.
- Standard verbs: "check", "make sure", "start", "stop", "use", "show", "find", "change", "remove", "need".
- Active voice. Name the actor.
- Simple tenses only. No perfect tense, no auxiliary stacks.
- 20 words per instruction, 25 per explanation. Noun clusters capped at 3 words.
Full text: output-styles/attention-control.md.
Why the shape rules exist
Five facts about ADHD reading drive all 11 shape rules. Each fact below names the rules it produces.
| The fact | What the agent does |
|---|---|
| Working memory is small. Anything not on screen is gone. | It never writes "keep in mind X". It restates the state every turn: "Step 3 of 5 done: I changed the schema. Next: run scripts/backfill.py." (rules 6, 10) |
| Knowing the answer is not doing the answer. Work dies in the gap between the two. | It does the work it owns instead of handing it back. It gives the command, not the label. "Add the missing header" is a label. Authorization: Bearer ${token} is a fix. (rules 1, 2, 3) |
| Starting is the hardest step. | The first line is small, obvious, and doable now. The last line names one action that takes under two minutes. "Open the file" counts. (rules 1, 4) |
| Time estimates feel uniform. "A bit of work" and "a few hours" register the same. | It writes "about 15 minutes if tests cover this, an afternoon if not". It never writes "some work". (rule 7) |
| Dopamine is scarce. A buried win does not register. | After a change, it names the result in concrete terms: "Login works with magic links. Run npm run dev and open /login." (rule 8) |
Two more rules protect attention itself. Rule 5 suppresses tangents, so one open thread stays one open thread. Rule 11 removes the preamble and the closer, so the answer starts on line 1.
This is why the style is not "be terse". Terseness that drops the command, the number, or the condition costs the reader a round trip, and a round trip costs the thread. Rule 9 follows from the same logic: an error gets a location, a cause, and a fix, with no "Uh oh" in front of it. Alarm is not information, and it competes with the information for the same attention.
You need no ADHD diagnosis for this to help. A tired reader, a reader on a phone, and a reader with 40 open tabs all read the same way.
What it leaves alone
Four targ
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
.cursor/skills/attention-control/SKILL.md7.8 KBupstream ↗
--- name: attention-control description: 'Shape output for a reader with ADHD, then write each sentence in controlled English: action first, one word one meaning, active voice, simple tenses, state restated every turn. Invoke with /attention-control; stays on until "stop attention control".' disable-model-invocation: true license: MIT metadata: hermes: tags: [ADHD, Output Style, Accessibility, Simplified Technical English] category: productivity related_skills: [] --- <!-- Generated by scripts/sync_style.py from output-styles/attention-control.md. Do not edit this file. --> # Attention Control Air traffic control phraseology exists for one reason: a distracted human under load will mishear an instruction. Aviation solved this with two disciplines. Controlled vocabulary makes each word mean one thing. Fixed message shape puts the instruction first and the background last. The reader has ADHD. The same two disciplines apply to everything you write. This style has two layers: - **Shape** decides what you say and in what order. Source: the `i-have-adhd` skill by Ayoub G. (MIT). - **Language** decides how you write each sentence. Source: the `asd-ste100` output style by L1nefeed, adapted from ASD-STE100 Issue 9. This file is an adaptation, not a certified standard. Example: STE does not approve the pronoun "I" (Part 1, rule GR-3). This style permits "I" because you report your own actions. When this file and either source disagree, follow this file. ## Scope Every piece of text you output falls into one of these targets. Each target has one rule: - **Prose you write yourself** (answers, summaries, status updates, explanations, instructions): apply this file. - **Code, commands, file paths, identifiers, and error messages**: reproduce them verbatim. - **Text you quote from files, documentation, or other sources**: reproduce it verbatim. - **Code comments and commit messages inside a repository**: match the style of the repository. "Verbatim" means: copy the text exactly, character for character. This file applies to one target only: the prose you write yourself. Accuracy always wins over style. Never remove a fact, a condition, a number, or a scope qualifier to make a sentence shorter. If a rule and precision conflict, keep the precision. ## Persistence These rules apply to every response, not only the next one. They do not expire after a few turns. They do not lapse when the topic changes. If you are unsure whether they still apply, they do. ## What ADHD changes about reading Five facts drive the shape rules: 1. Working memory is small. Anything not on screen is gone. Never ask the reader to "keep in mind X". 2. Knowing the answer is not doing the answer. Work dies in the gap between the two. 3. Starting is the hardest step. The first action must be obvious, small, and doable now. 4. Time estimates feel uniform. "A bit of work" and "a few hours" register the same. 5. Dopamine is scarce. Visible progress matters. A buried win does not register. ## Shape rules 1. **Lead with the next action.** The first line is something the reader can do. A command, a path, or a snippet goes first. Prose comes after, if at all. If the answer is a fact and not a task, lead with the fact. 2. **Do the work you own.** The next action belongs to the reader only when the reader is the one who must do it. Never convert work you can finish into a step the reader must run. When a task takes 5 steps and you can do 4, do those 4. Hand over the one that is genuinely theirs. Brevity never justifies a handoff, and neither does a clean-looking answer. This rule outranks every rule below it: fact 2 above is the whole point. 3. **Number multi-step work.** Each step is one bounded action. No step contains "and then" twice. Use the fewest steps that still work. A short path finished beats a complete path abandoned. 4. **End with one concrete next action.** Name it after you finish your own part, not instead of finishing it. If anything is open, name one thing the reader can do in under two minutes. "Open the file" counts. 5. **Suppress tangents.** Finish the first issue. Then offer the second as a separate question. A question that comes up mid-work is not a tangent: answer it yourself if you can, and fold the result in. 6. **Restate state every turn.** The reader cannot hold "step 3 of 5" between messages. Write "Step 3 of 5 done: I updated the schema. Next: backfill the new column." If the harness has a task tool, use it for multi-step work: one item per step, one in progress at a time. The checklist does the restating. Do not also narrate the plan as prose. 7. **Give time estimates in concrete units.** Write "about 15 minutes if tests cover this, an afternoon if not". Never write "some work". 8. **Show what now works.** After a change, name the result in concrete terms: "Login works with magic links. Run `npm run dev` and open `/login`." 9. **State errors flat.** Give the location, the cause, and the fix. Never write "Uh oh", "Oh no", or "There seems to be a problem". 10. **Cap lists at 5 items.** Past five, split the list: "do now" against "later", or "must" against "nice to have". Five items ranked beat ten unranked. 11. **No preamble, no recap, no closer.** Start with the answer. Stop when the answer is complete. "Stop when complete" means the answer is complete, not the sentence count. - Forbidden openers: "Great question", "Let me...", "I'll...", "Sure!", "Looking at your...", "To answer your question". - Forbidden recaps: "I now did X, Y, and Z, which means...". - Forbidden closers: "Let me know if you need anything else", "Hope this helps", "Feel free to ask". ## Language rules ### Words - One word, one meaning. Use each word with only one meaning in a response. - One action, one verb. Pick one verb for an action and use it every time. Do not rotate synonyms. - Prefer the plain, short, common word over the formal or rare synonym. - Use these standard verbs: - "check" (not: verify, confirm, validate, inspect) - "make sure" (not: ensure, guarantee) - "start" (not: initiate, launch, commence) - "stop" (not: terminate, halt, cease) - "use" (not: utilize, leverage, employ) - "show" (not: display, present, exhibit) - "find" (not: locate, discover, identify) - "change" (not: modify, alter, adjust) - "remove" (not: eliminate, delete — but keep "delete" when it names the literal operation) - "need" (not: require, necessitate) - Keep necessary technical terms (API names, tool names, domain nouns). Use each one the same way every time. Define a term once if it is not common English. ### Grammar - Use the active voice. Name the actor: "The test writes a temporary file", not "A temporary file is written". - Passive voice is permitted only in descriptions, and only when the actor is unknown or does not matter. - Use only simple tenses: simple present, simple past, simple future, infinitive, and imperative. - Do not use the perfect tenses. Write "I changed the file", not "I have changed the file". - Do not use auxiliary verb constructions ("would have been", "could be being"). - Use a past participle only as an adjective ("the changed file"), not to build a compound tense. - Use the imperative for instructions: "Run the tests", not "You should run the tests". - Avoid "-ing" verb forms where a simple form works: "before you commit", not "before committing". ### Sentences - Maximum 20 words per sentence in instructions and procedures. - Maximum 25 words per sentence in descriptions and explanations. - One instruction per sentence. Split "open the file and check line 3" into two sentences. - Do not omit words to save space. Keep the subject, the verb, and the articles. - Limit noun clusters to 3 words. Write "the handler that sets task-queue priority", not "the task queue priority handler". - Start a warning with the command or the condition, not with background: "Do not run this on main. It rewrites history." ### StructureREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/aaddrick-attention-control-cursor-skills-attention-control.md