adhd

Generate layered, scannable code explanations with hooks, maps, and progress markers.

10|1|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Yuvasee/samocode --skill adhd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adhd
Source: https://github.com/Yuvasee/samocode/tree/main/skills/adhd
Command: npx skills add https://github.com/Yuvasee/samocode --skill adhd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a cognitive scaffold for developers with ADHD, helping them transition from distraction to focused comprehension of code by offering layered, scannable explanations.

Core Features & Use Cases

  • Layered Explanations: Delivers information in distinct, digestible layers (Hook, Map, Walkthrough, Gotchas, Deep Dive).
  • Scannable Format: Utilizes bolding, inline code, progress markers, and varied formatting to maintain engagement.
  • Use Case: A developer struggling to grasp a complex new feature can use this Skill to get a quick, high-impact overview, followed by a structured breakdown of components and potential pitfalls, enabling rapid understanding and hyperfocus.

Quick Start

Use the adhd skill to explain the code changes on the current branch.

Frequently Asked Questions about adhd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an ADHD-friendly explanation of a complex code diff?

To get an ADHD-friendly code explanation, process your git diffs through this skill to generate layered, scannable content with hooks, maps, and progress markers for rapid comprehension.

What is the best way to understand GitHub PRs when struggling to focus?

The best way to understand GitHub PRs with focus issues is using structured walkthroughs that break changes into immediate impacts, component maps, and critical gotchas to trigger hyperfocus.

Can I use this to explain code directly from a file path?

Yes, you can generate an optimized code explanation by providing a file path to generate a structured breakdown with bolding, inline code, and progress markers to maintain engagement.

How do scannable formats help developers comprehend code faster?

Scannable formats help developers comprehend code faster by utilizing bolding, inline code, and progress markers to deliver digestible layers like hooks, maps, and walkthroughs that facilitate hyperfocus.

Does this work for understanding feature descriptions or only existing code?

This works for understanding feature descriptions as well as existing code, adapting to various input types like git diffs, GitHub PRs, file paths, or feature descriptions to generate structured walkthroughs.

When do I need a cognitive scaffold for code comprehension?

You need a cognitive scaffold for code comprehension when transitioning from distraction to focused understanding, using layered explanations to digest complex new features and avoid potential pitfalls.