Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gentleman-programming/cognitive-doc-design
Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.
Passed 8 of 23 test cases with the skill, and 5 of 23 without it.
and 4 more in the full report
4 fixed4 passed either way14 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Write a decision record summary for switching our session store from PostgreSQL to Redis. The main decision is that Redis was selected to reduce query latency under 5ms, while historical background details describe the latency spikes analyzed during Q3 load testing. Draft this summary.
| Checked | Without skill | With skill |
|---|---|---|
| States the decision to adopt Redis in the first sentence. | Missed | Passed |
| Places contextual latency spike details after the primary decision statement. | Missed | Passed |
The instructions your model reads when the skill loads.
Load this skill when creating or editing documentation that people need to understand quickly, retain, or use during review.
Use it especially for:
| 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. |
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 |
test cases passed, vs 5 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.