pixel-brain-page
Skill0 starsChanged 24 days agoMITView on GitHub
The reading-page look for long documents people read, such as a brain or wiki page, an approach page, a plan, a report or a status page. Use when making or restyling one. One sans family, light paper, the contents on the left, the depth one click away.
In this repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- agent-runtimeSkill
- frontend-designSkill
- architectSkill
- deep-thinkSkill
- design-systemsSkill
- ecosystem-referenceSkill
- fractal-delegationSkill
- harness-reviewSkill
- heartbeatSkill
- integrate-resourcesSkill
- llm-council-critiqueSkill
- loop-createSkill
- mcp-setupSkill
- memory-compressionSkill
- memorySkill
- model-routingSkill
- oss-project-scaffoldSkill
- playwright-cliSkill
- repo-scoutSkill
- self-improveSkill
- skill-creatorSkill
- skill-routingSkill
- sprintSkill
- test-visualSkill
- troubleshootSkill
- ux-auditSkill
- Accessibility AuditorSkill
- artifacts-builderSkill
- brand-guidelinesSkill
- canvas-designSkill
- frontend-patternsSkill
- design-mirrorSkill
- design-system-starterSkill
- design-to-codeSkill
- feature-design-assistantSkill
- figma-implement-designSkill
- frontend-designSkill
- frontend-dev-guidelinesSkill
- mobile-designSkill
- motion-canvasSkill
- pixel-agent-uiSkill
- pixel-animateSkill
- pixel-anti-slopSkill
- pixel-migrate-next16Skill
- pixel-rsc-boundarySkill
- pixel-ship-gateSkill
- premium-web-designSkill
- senior-frontendSkill
- shadcnSkill
- tailwind-design-systemSkill
- tailwind-patternsSkill
- theme-factorySkill
- ui-design-systemSkill
- ui-ux-pro-maxSkill
- ux-researcher-designerSkill
- web-design-guidelinesSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 46
Put the answer in each section's lead and first paragraph.
- Distinctive: line 49
Check before you share it: search for "Serif" (none), no dark palette, screenshots at 1280 and 390 read, no sideways scroll on the page …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
pixel-brain-page: the reading-page look
Long pages that people read need a calmer look than a product interface. This skill is that look: one sans family, light paper, the contents on the left, the answer on the page and the depth one click away. It overrides the house style (O-HS1 warm black, O-HS2 a serif display with a sans body) for reading pages only. Product interfaces keep the house style.
Why: a stretched display face and a dark page tire a reader on a long document. A contents rail and sections that open on a click let the reader find the answer first and the evidence second. Readers asked for this look in October 2026, after calling a serif title "elongated".
trigger
- any HTML page meant for reading: a brain or wiki page, an approach page, a plan, a report, a status page
- restyling a page a reader called stretched, elongated, dark or orphaned
The look
- One family: Instrument Sans for titles, headings, body and figures. No serif display face, no condensed or stretched face (Instrument Serif reads as elongated at title sizes), no monospace in prose.
- Title: weight 400,
clamp(2.5rem, 5vw, 3.5rem), line height 1.02, letter spacing -0.03em. - Scale: 56, 42, 27, 19, 16, 14 and 11 px; section headings at weight 600; labels 11px in capitals with 0.14em tracking; body 16px on 1.62.
- Paper, light only:
--bg #fbfaf7,--panel #f3f0e8,--ink #1c1b18,--mute #6b675e,--line #e4e0d6. - Colour on data only:
--acc #2f5d8a(--acc-soft #e4ecf4,--acc-ink #1e3f60),--agent #2f6b4f(--agent-soft #e3efe8) for agent employees,--you #8a4b2ffor the person,--warn-soft #f6eedbfor a note. - Layout: crumbs, kicker, title, sub and a stamp read from the clock; a 210px sticky contents rail on the left, grouped under small capital labels; a 760px reading column; figures up to 1060px; under 820px the rail becomes one row that scrolls sideways.
- Progressive disclosure: the answer on the page, the depth in
details.deeper(a + that turns to a minus) and an "Open all" button. - Figures: inline SVG drawn to scale, in the page's tokens and font, each with a title, a description and a caption; a wide figure scrolls in its own box.
- Connected: crumbs back to the brain's home and folder; the brain's build lists the page; no orphan.
steps
- Copy
template.htmlbeside the page's Markdown source and fill it in. Keep the CSS block as it is. - Put the answer in each section's lead and first paragraph; move the depth into
details.deeper. - Draw each figure with the
d-classes in the template, to scale. - Link the page from its brain (its folder's README or index) and keep the crumbs pointing home.
- Check before you share it: search for "Serif" (none), no dark palette, screenshots at 1280 and 390 read, no sideways scroll on the page itself.
Where it came from
Distilled from a long strategy document read on screen: a contents rail, about 150 sections that open on a click and
about 50 inline figures. template.html beside this file is the distilled version. First used on an approach page in
October 2026.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

