design-info
Skill3 starsChanged 49 days agoMITView on GitHub
Corporate / info site lens. Use when the site's purpose is to explain and build trust — corporate sites, documentation, content-heavy sites, informational portals, blog hubs, public-sector sites. Load after design-core has established why the site exists and confirmed the goal is trust and clarity. Does not replace design-core; adds subtype-specific priorities, typical failures, and layer-by-layer guidance.
In this repository5 other files it gives its agents.
- design-coreSkill
- design-ecommerceSkill
- design-portfolioSkill
- design-promoSkill
- design-saasSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
No hierarchy inside sections: Every paragraph has the same weight, so nothing is skimmed.
≈ “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
Design Info — Corporate & Information Sites
A subtype lens for design-core. Load this after design-core has run its three entry steps and confirmed the goal is trust and clarity.
This file does not redefine the eight elements, the four layers, the two modes, or the two phases. It only adds what is specific to info sites.
Focus
Trust and structure. A lot of content, and it must be easy to find. Navigation is deep but never scary — the visitor should always know where they are and how to go back. Readability on long text is the primary craft. Design serves clarity; it does not perform.
Marketing does not run as a filter here — but a clear path to action (contact, sign-up, download) is part of the frame, not an afterthought.
Typical failures
- Wall of text. Unbroken blocks with no hierarchy, no subheads, no air. Fix: break into sections, give every section one job, let space do the separating.
- Five-level navigation. The menu nests deeper than the visitor will follow. Fix: no more than three levels; use search for depth.
- No hierarchy inside sections. Every paragraph has the same weight, so nothing is skimmed. Fix: a real subhead system with visible hierarchy.
- Buried dates or contacts. The two facts a visitor often needs first (what's current, how to reach you) are hidden. Fix: surface them.
Layer-by-layer
Frame (composition, space). The frame is a reading grid — 65–75 characters per line. Space separates sections, and section boundaries are felt, not just seen. Navigation is persistent and honest about current location. The composition serves comprehension; it does not try to impress.
Body (form, color). Color carries trust: restrained palettes, high contrast, no accent color used for decoration. Form is minimal — cards and containers serve grouping, not styling. Radius is small or absent; large radii read as playful and undermine authority.
Surface (texture, typography). Typography is the main tool. A clear type scale, readable body size, generous line height, and a real heading system. Texture is absent or near-absent; grain, gradient, and photographic ornament distract from reading.
Accent (point, line). Minimal. Dividers may be used to separate sections, but only if they carry structural meaning. Icons support navigation, not decoration. The accent color, if present, is reserved for links and calls to action.
Reading order
Info sites have two reading modes, and both matter:
- Scan — a visitor lands, understands what the site is, and finds their entry point in under 10 seconds. Hierarchy in headings, sections, and nav makes this possible.
- Read — a visitor settles on a page and reads long content. Line length, line height, contrast, and subheads make this bearable.
A page that serves only one of these modes fails the other.
Audit specifics
Beyond the common grid, these are the info-site breakages to hunt:
- Space → Frame → navigation nests deeper than three levels → three levels max; search carries the depth.
- Typography → Surface → paragraphs carry equal weight, nothing skimmable → a real subhead system with visible hierarchy.
- Color → Body → accent used decoratively → accent is reserved for links and actions; trust reads from restraint.
- Line → Accent → dividers between every section → rules only where boundaries carry structure.
- Typography → Surface → dates and contacts buried at page end → the current/contact facts surface where visitors look first (in docs: TOC and search stay visible).
Return to core
For the method, see design-core/SKILL.md. For the words on long pages — headings, dates, links — see design-core/references/copy.md. For the layers protocol, see design-core/references/layers.md. For the audit grid — which is especially useful for large info sites — see design-core/references/audit-grid.md.
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.

