saas-ui-ux-designer-skill-typography-flex
Skill17 starsChanged 8 months agoMITView on GitHub
Typography-first SaaS UI/UX workflow for internal product screens and components. Use when designing or refactoring dashboards, settings pages, editors, builders, tables, or modals where typography hierarchy, flex/grid layout, spacing rhythm, and premium neutral surfaces need to be the main organizing system. Also use when a UI feels cramped, visually noisy, misaligned, or inconsistent.
In this repository4 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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 10
Use this skill to design calm, premium SaaS UI where typography and flex/grid layout carry the hierarchy.
- Distinctive: line 15
Start with layout first:
- Distinctive: line 22
Check states, spacing, and responsiveness.
- Distinctive: line 23
Read references/typography-flex.md for the detailed rules when needed.
- Distinctive: line 44
Read references/typography-flex.md for:
- Distinctive: line 54
Prefer existing product tokens and components when present.
- Distinctive: line 55
Keep output responsive and production-ready.
- Distinctive: line 56
Avoid decorative clutter, loud color, and concept-art styling.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
SaaS UI UX Designer Skill Typography Flex
Overview
Use this skill to design calm, premium SaaS UI where typography and flex/grid layout carry the hierarchy. Favor readable product structure over decorative styling.
Workflow
- Define the screen purpose, main action, and primary vs secondary zones.
- Start with layout first:
- flex vs grid
- sticky vs flowing regions
- main vs supporting panels
- desktop vs mobile stacking
- Establish typography hierarchy before decoration.
- Apply neutral surfaces, restrained accent use, and consistent card rhythm.
- Check states, spacing, and responsiveness.
- Read references/typography-flex.md for the detailed rules when needed.
Defaults
- Typography drives hierarchy
- Flex/grid drives structure
- Neutral surfaces with restrained accent
- One clear primary action per zone
- Reusable patterns over one-off layouts
- Settings and builder pages should feel product-grade, not admin-raw
Use This Skill To
- redesign SaaS settings pages
- improve dashboard or editor layout rhythm
- fix misalignment, cramped cards, or noisy spacing
- choose between stacked, split, and sticky panel layouts
- make internal product UI feel premium and production-ready
References
Read references/typography-flex.md for:
- typography hierarchy rules
- flex and grid layout recipes
- section and card composition
- settings page structure
- common UI anti-patterns
Constraints
- Prefer existing product tokens and components when present.
- Keep output responsive and production-ready.
- Avoid decorative clutter, loud color, and concept-art styling.
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.

