mcpbeat Sign in

Cognitive Doc Design Agent Skill

Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.

594 tokens
context cost
SKILL.md, read when the skill is used
1
files
plus fonts, images or templates
0
copies elsewhere
how many repositories repackaged it
6 287
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Gentleman-Programming/gentle-ai --skill cognitive-doc-design

The instruction itself

5 sections, as written by the author

When to Use

Load this skill when creating or editing documentation that people need to understand quickly, retain, or use during review.

Use it especially for:

  • PR descriptions and review notes.
  • Contributor or maintainer guides.
  • Architecture, workflow, or onboarding docs.
  • Any doc that currently feels long, dense, or hard to scan.

Critical Patterns

| Pattern | Rule |

|---------|------|

| Lead with the answer | Put the decision, action, or outcome first. Context comes after. |

| Progressive disclosure | Start with the happy path, then add details, edge cases, and references. |

| Chunking | Group related information into small sections. Keep flat lists short. |

| Signposting | Use headings, labels, callouts, and summaries so readers know where they are. |

| Recognition over recall | Prefer tables, checklists, examples, and templates over prose that must be remembered. |

| Review empathy | Design docs so reviewers can verify intent without reconstructing the whole story. |

Documentation Shape

Use this default structure unless the repo already provides a stronger template:

# <Outcome-oriented title>

<One paragraph: what changed, who it helps, and why it matters.>

## Quick path

1. <First action>
2. <Second action>
3. <Verification or expected result>

## Details

| Topic | Decision |
|-------|----------|
| <area> | <concise explanation> |

## Checklist

- [ ] <Reader can confirm this>
- [ ] <Reader can confirm that>

## Next step

<Link or action that continues the workflow.>

PR and Review Docs

When documenting a PR, reduce reviewer burnout by making the review path explicit:

  • State what to review first.
  • State what is intentionally out of scope.
  • Link the previous and next PR when work is chained.
  • Keep each section focused on one decision or unit of work.
  • Use checklists for acceptance criteria and verification.

Commands

# Check markdown files changed in the current branch
git diff --name-only -- '*.md'

# Inspect PR changed-line count for cognitive load
gh pr view <PR_NUMBER> --json additions,deletions,changedFiles

How to use it

Copy the folder

Take gentleman-programming/cognitive-doc-design from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.