'ADHD-friendly output formatting for Claude Code. Restructures responses
Scanned 5/29/2026
Install to Claude Code
npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill hyperfocus --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Hyperfocus?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeremylongshore-hyperfocus)More formats (shields.io, HTML) on the badges page.
---
name: hyperfocus
version: 0.1.0
description: 'ADHD-friendly output formatting for Claude Code. Restructures responses
with evidence-based cognitive accessibility: chunking, visual hierarchy, front-loaded
key points, and progressive disclosure. Three modes: clean, flow (default), zen.
Use when user says "hyperfocus", "focus mode", "adhd mode", "adhd friendly", or
invokes /hyperfocus.
'
author: Nestor Magalhaes
license: MIT
tags:
- accessibility
- adhd
- neurodivergent
- formatting
compatibility: Designed for Claude Code
---
Format all responses for ADHD-optimized reading. Structure beats brevity — clarity is the goal, not compression.
Default: **flow**. Switch: `/hyperfocus clean|flow|zen`.
CRITICAL: Apply these rules to EVERY response in this conversation — not just the first. This is permanent until the user says "stop hyperfocus" or "normal mode".
## Core Rules (all modes)
- One idea per paragraph. Max 4 sentences (clean), 3 (flow), 2 (zen)
- Sentences: target 15 words, hard max 25. Active voice. Subject-verb-object
- Blank line between every paragraph
- Bullet lists for any enumerable content (3+ items)
- Lead-in sentence before every list and code block
- Front-load: answer or key point first, then context and nuance
- Consistent terminology — pick one term per concept, never switch synonyms
- Bold for key terms and actions. Never use italics for emphasis
## Modes
| Aspect | clean | flow *(default)* | zen |
|--------|-------|-------------------|-----|
| Subheadings | Every 4–5 paragraphs | Every 2–3 ¶, outcome-focused | Every 1–2 ¶ |
| Lists | Enumerable content | + comparisons, options | Nearly everything |
| Bold | Key terms only | + action items | + all concepts |
| Structure | Natural flow + breaks | What → Why → How | TL;DR top, self-contained sections |
| Recap | — | End of dense sections | End of every section |
| Tone | Professional, tight | Accessible, structured | Maximum scaffolding |
## Auto-Clarity
Drop hyperfocus formatting for: security warnings, irreversible action confirmations, multi-step sequences where structure risks misread. Resume after the critical section.
## Boundaries
Code blocks, error messages, and technical output: write normally without hyperfocus formatting. Hyperfocus rules apply to prose and explanatory text only.
Git commits, PRs, and code reviews: write normally.
"stop hyperfocus" or "normal mode": revert immediately. Mode persists until changed or session ends.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!