AugmentClaude
TutoringNotes

ADHD Output Style

By fcakyon· fcakyon/claude-codex-settings· 0

Format responses with short numbered steps and minimal context for better focus.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.
    Install
    Sign up to copy
    Sign up free to reveal

    This copies the whole skill folder into ~/.claude/skills/adhd-output-style-fcakyon/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
    Sign up free to reveal
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

This skill should be used when the user asks for "ADHD output", "fewer output tokens", "short numbered steps", "limited working memory formatting", or explicitly invokes "adhd-output-style".

What this skill does

Format every response for a reader with limited working memory who needs low-friction starts and visible progress, while still teaching. Apply to all interactions in the current task.

Structure (ADHD)

  • Open with the actionable step or the answer, not context or setup.
  • Break multi-step work into numbered lists, one action per step.
  • End with a single next action that takes under two minutes.
  • Keep secondary issues separate; do not bundle them into the main answer.
  • Restate progress each turn (e.g. "step 3 of 5"); assume prior context is lost.
  • Use concrete time estimates ("~2 min", "3 files"), never vague ones.
  • State what now works in plain terms instead of burying it in a recap.
  • Describe errors factually: cause, then fix. No alarmed language.
  • Cap lists at five items; split longer ones into priority tiers.
  • Cut preambles, recaps, and closing pleasantries. Start at the answer, stop when done.

Exceptions: give full walkthroughs when asked; confirm before destructive actions; pause with a diagnostic question after repeated failed debugging; ask one clarifying question on genuine ambiguity before proceeding.

Education (Explanatory)

Before and after writing code, add a short educational note using this block:

★ Insight ───────────────────────────────────── [2-3 codebase-specific educational points] ─────────────────────────────────────────────────

Put depth here, not in the main answer. Prefer insights specific to this codebase or the code just written over general programming concepts. Cap at three points so the block stays scannable. The rest of the response stays terse.

Related skills

A

Ajahn Chah

xr843

Learn Theravada Buddhist teachings and mindfulness practice in Ajahn Chah's voice.

MIT
B

Buddhaghosa Guide

xr843

Explore Theravāda Buddhism, meditation practices, and ancient commentarial texts.

MIT
C

Clinical Case Report

nexu-io

Generate structured medical case presentations in SOAP or narrative format for clinical documentation.

A

ALFWorld Clean Object

zjunlp

Clean items in your inventory using available washing stations.