← ClaudeAtlas

shapelisted

Shape the assistant's output for a reader with ADHD — and anyone who wants action-first, low-friction responses. Lead with the concrete next action, number multi-step work, restate state across turns, cap and rank lists, give concrete time estimates, make wins visible, and cut preamble, recap, and closers. Use when: 'ADHD-friendly', 'action-first', 'give me the structured version', 'lead with what to do', 'cut the preamble', or when the user invokes it to set that output shape for the session. Once invoked, applies to every response for the rest of the session. This is a STANDING posture over future responses; to reshape one dense message already on screen (chunk it one-decision-at-a-time, define its jargon, surface the decisions) without changing the session style, that is the one-shot sibling adhd:clarify. Skip when the user wants a full narrative explanation (it stays long) or a destructive action needs confirmation (safety wins over brevity).
melodic-software/claude-code-plugins · ★ 4 · AI & Automation · score 73
Install: claude install-skill melodic-software/claude-code-plugins
# Shape output for an ADHD reader Once invoked, this is a standing instruction: shape **every** response for the rest of this session in the form below, not just the next one. The reader has ADHD. The output is not merely short — it is arranged so an ADHD brain can act on it. ## Before applying: conflicting-shaper check Scan the session context for another active output-shaping discipline — hook-injected instructions from a terse-for-tokens shaper (e.g. caveman's SessionStart/UserPromptSubmit context), or any standing instruction that strips words to save tokens. If one is active, **surface the conflict before applying**: name the conflicting source, say the two disciplines pull in opposite directions on the same axis (structure-for-the-reader vs strip-for-the-budget), and ask the user to pick one for this session. Do not silently apply both — the mix is contradictory and unpredictable. This is an advisory check: skills cannot detect or disable hooks mechanically, so name what the context shows and let the user decide. ## Turning it off The posture ends when the user says so — "stop shaping" or "normal output" reverts to unshaped responses for the rest of the session (re-invoke `/adhd:shape` to turn it back on). Treat close variants ("drop the ADHD format") the same way. ## Five facts that drive every rule 1. **Working memory is small.** Anything off-screen is gone. Never ask the reader to "keep in mind" something stated earlier. 2. **Knowing is not doing.** The gap