saas-product-ui-system
Skill17 starsChanged 8 months agoMITView on GitHub
Canonical SaaS product UI skill for designing, reviewing, or implementing calm, premium, production-ready interfaces across dashboards, settings, admin/runtime screens, editors, builders, tables, forms, drawers, sidebars, and related public surfaces. Use when you need strong hierarchy, reusable tokens, typography, responsive layout rules, component consistency, and app-surface patterns rather than decorative one-off design.
In this repository4 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 11 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
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
- Distinctive: line 10
Use this skill as the default UI/UX and frontend-design workflow for serious SaaS product work.
- Very specific: line 83
Use assets/default-product-tokens.css when a task needs a starter token file instead of conceptual guidance alone.
- Distinctive: line 98
If the user asks for code:
- Distinctive: line 99
follow the existing stack and patterns first
- Distinctive: line 100
use semantic tokens and reusable components
- Distinctive: line 101
keep markup production-ready and workflow-oriented
- Distinctive: line 103
If the user asks for critique:
- Distinctive: line 109
Prefer existing product patterns and tokens when working inside an established app.
- Distinctive: line 110
Do not introduce decorative styles that break the system just to make one page feel unique.
- Distinctive: line 111
Keep admin and settings surfaces operational, not presentation-heavy.
- Distinctive: line 112
Keep copy short on settings and runtime pages.
- Distinctive: line 114
Avoid noisy gradients, scattered accent colors, and one-off visual treatments.
≈ “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 Product UI System
Overview
Use this skill as the default UI/UX and frontend-design workflow for serious SaaS product work. It combines the cleaner design-system language of ui-ux-design-system with the stronger workflow, typography, flexibility, and page-composition guidance from saas-ui-ux-designer-with-flex.
Use This Skill To
- design or redesign dashboards, settings pages, admin panels, runtime/provider screens, editors, builders, billing, security, and data-heavy list/detail pages
- refactor noisy UI into one coherent product system
- decide layout hierarchy before styling
- improve typography, density, spacing, and responsive behavior
- implement or review frontend code that should feel product-grade and reusable
- choose the right composition for cards, tables, filters, side panels, drawers, dialogs, and summary strips
Do Not Use This Skill For
- backend-only work with no UI or product-surface impact
- purely decorative concept art or poster-style design
- strict pixel cloning of a design system that already defines every token and component
- native mobile UI where platform conventions matter more than SaaS web patterns
Workflow
- Classify the surface:
- public marketing or trust page
- authenticated product workspace
- admin or operations page
- settings or runtime configuration
- editor, builder, or writing workspace
- Define the user goal, current state, and primary action.
- Choose density before layout:
- comfortable for onboarding, empty states, and trust-heavy surfaces
- balanced for most product pages
- compact for admin, reporting, and data-heavy operational views
- Structure the screen before styling:
- context row or page intro
- current-state summary
- main working area
- supporting panels or side rails
- secondary details
- Choose layout primitives deliberately:
- flex for aligned actions, rows, toolbars, filters, and control groups
- grid for summaries, card collections, split lanes, and multi-column forms
- Apply the design system, typography, component, and page-pattern references.
- Produce implementation or critique with real states, responsive behavior, and clear hierarchy.
Defaults
- Neutral-first surfaces
- Premium SaaS product tone
- Dark-first with light-mode parity
- One clear primary action per section
- Balanced density by default
- Typography and spacing carry hierarchy
- Semantic colors only for status, focus, and key actions
- Existing product patterns override invention when working in an established app
Reference Loading Order
Load only what the task needs. For broad page work, use this order:
- references/product-ui-principles.md Core philosophy, tokens, layout rules, AI-product patterns, state rules, responsiveness, and accessibility.
- references/app-surface-patterns.md App-oriented guidance for settings, admin, runtime, editors, tables, shell behavior, and density choices.
- references/typography-system.md Typography hierarchy, scale, weight, line-height, and readability rules.
- references/layout-flexibility.md Responsive layout, flex/grid strategy, breakpoints, overflow handling, and stress-test rules.
- references/component-spec.md Shared component behavior and expectations for buttons, inputs, navigation, overlays, tables, and feedback states.
- references/page-blueprints.md Composition patterns for public pages and internal product surfaces.
- references/design-tokens.css Concrete token values when implementation needs a ready CSS variable base.
Use assets/default-product-tokens.css when a task needs a starter token file instead of conceptual guidance alone.
Output Contract
Unless the user asks for something narrower, produce:
- Product and user assumptions
- Surface type and density mode
- Visual direction
- Layout structure
- Typography and token decisions
- Component and state decisions
- Responsive and accessibility notes
- Implementation notes or critique findings
If the user asks for code:
- follow the existing stack and patterns first
- use semantic tokens and reusable components
- keep markup production-ready and workflow-oriented
If the user asks for critique:
- identify hierarchy, density, state, and responsiveness gaps first
- recommend structural fixes before decorative changes
Constraints
- Prefer existing product patterns and tokens when working inside an established app.
- Do not introduce decorative styles that break the system just to make one page feel unique.
- Keep admin and settings surfaces operational, not presentation-heavy.
- Keep copy short on settings and runtime pages; the UI should explain itself structurally.
- Build real empty, loading, error, disabled, and selected states where relevant.
- Avoid noisy gradients, scattered accent colors, and one-off visual treatments.
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.

