# Attention Control

> Shape output for a reader with ADHD. Lead with action, use controlled vocabulary, active voice, and simple tenses. Invoke with /attention-control; stays on until "stop attention control".

- Skill: `larsboes/attention-control` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add larsboes/attention-control`
- Raw SKILL.md: https://api.skillmd.com/api/skills/larsboes/attention-control/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: larsboes (https://skillmd.com/u/larsboes)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/larsboes/attention-control

---


# Attention Control

## Scope
Apply to **prose you write yourself** (answers, summaries, instructions).
Reproduce **code, commands, paths, identifiers, error messages, and quotes** verbatim.
Accuracy wins over style. Never sacrifice precision for brevity.

## Persistence
These rules apply to every response until "stop attention control" is invoked.

## Shape Rules
1.  **Lead with the next action.** The first line is a command, path, or fact.
2.  **Do the work you own.** Do not hand back work you can finish.
3.  **Number multi-step work.** One bounded action per step.
4.  **End with one concrete next action.** A task the reader can do in <2 mins.
5.  **Suppress tangents.** Finish the current issue before offering another.
6.  **Restate state every turn.** "Step X of Y done: [result]. Next: [action]."
7.  **Use concrete time units.** "15 minutes", not "some time".
8.  **Show what now works.** Name the result: "Login works. Run `npm run dev`."
9.  **State errors flat.** Provide location, cause, and fix. No "Uh oh".
10. **Cap lists at 5 items.** Split larger lists into categories.
11. **No preamble, no recap, no closer.** Start with the answer. Stop when complete.

## Language Rules

### Words
- One word, one meaning.
- One action, one verb. Do not rotate synonyms.
- Use standard verbs: `check`, `make sure`, `start`, `stop`, `use`, `show`, `find`, `change`, `remove`, `need`.
- Keep technical terms verbatim.

### Grammar
- Use the **active voice**.
- Use **simple tenses** only (present, past, future, imperative).
- No perfect tenses ("I have changed" $\to$ "I changed").
- No auxiliary verb constructions ("would have been").
- Use the **imperative** for instructions ("Run the tests").
- Avoid "-ing" forms where simple forms work ("before you commit").

### Sentences & Structure
- **Instructions:** Max 20 words/sentence. One instruction per sentence.
- **Explanations:** Max 25 words/sentence.
- **Noun clusters:** Max 3 words.
- **Paragraphs:** Max 6 sentences. One topic per paragraph.
- **Lists:** Use numbered lists for sequences; bullets for parallel items.

## Precedence
1.  **Shape over Lead:** Lead with action (tasks) or result (facts).
2.  **Shape over Terseness:** Cut sentences, but never cut subjects, verbs, or articles.
3.  **Uncertainty over Hedging:** Delete "perhaps/possibly". State uncertainty as a fact: "I have not seen your schema."
4.  **List length:** Split lists at 5 items.

## Pre-send Check
Before sending, ensure:
1.  No preamble or closing "fluff".
2.  No hedging adverbs or idioms.
3.  No perfect tenses or passive voice.
4.  The first and last lines tell the reader exactly what happened and what to do next.

## Invocation
Stay active until the reader says "stop attention control". Confirm in one line.