agentleFS
dhananjaym182dhananjaym182/ai-ui-design-skills/skills/saas-ui-ux-designer-with-flex/SKILL.md

saas-ui-ux-designer-with-flex

Skill17 starsChanged 8 months agoMITView on GitHub

Full-system SaaS UI/UX design workflow for product interfaces that should feel premium, calm, structured, responsive, and production-ready. Use when designing or refactoring dashboards, settings pages, editors, builders, forms, tables, modals, drawers, sidebars, and runtime configuration screens. Also use when deciding layout hierarchy, typography, spacing, neutral surface treatment, card composition, flex/grid structure, dark/light parity, and reusable system patterns across a SaaS app.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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
  1. Distinctive:

    Use this skill to design real SaaS product UI with a system-first approach.

    line 10
  2. Distinctive:

    Keep typography, spacing, surfaces, and states consistent across the full page.

    line 25
  3. Distinctive:

    Read these references as needed, in this order for broad UI work:

    line 54
  4. Very specific:

    Use assets/default-saas-tokens.css when the task needs a ready token starter file rather than only conceptual guidance.

    line 71
  5. Distinctive:

    Prefer existing product patterns and tokens when working inside an established app.

    line 75
  6. Distinctive:

    Do not invent decorative styles that break the system just to make one screen feel different.

    line 76
  7. Distinctive:

    Avoid loud color, visual noise, and concept-art styling unless explicitly requested.

    line 77
  8. Distinctive:

    Keep output production-ready and workflow-oriented.

    line 78

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SaaS UI UX Designer With Flex

Overview

Use this skill to design real SaaS product UI with a system-first approach. It is for application surfaces and workflow-heavy pages, not decorative concept work.

Workflow

  1. Define the user goal, the current state the page must show, and the single primary action.
  2. Choose the structure before styling:
    • page intro
    • current-state summary
    • main configuration or working area
    • supporting panels
    • secondary details
  3. Build the layout with flex or grid based on content behavior:
    • flex for aligned controls, toolbars, settings rows, action groups
    • grid for repeated cards, summary tiles, split lanes, and multi-column forms
  4. Apply the full design system from references/saas-ux-design-system-skills.md.
  5. Keep typography, spacing, surfaces, and states consistent across the full page.
  6. Final-check:
    • hierarchy is obvious at a glance
    • accents are restrained
    • cards feel like one family
    • empty/loading/error states exist where needed
    • mobile layout stacks cleanly

Defaults

  • Neutral-first surfaces
  • Premium SaaS product tone
  • Dark-first with light-mode parity
  • One clear primary action per section
  • Reusable components over one-off markup
  • Typography and spacing carry hierarchy
  • Flex/grid structure chosen deliberately, not by habit
  • Semantic colors only for status

Use This Skill To

  • design internal product pages, dashboards, settings screens, editors, and builders
  • review or refactor noisy UI into one coherent product system
  • decide page hierarchy, card composition, panel structure, and control density
  • improve typography rhythm, layout alignment, and visual consistency
  • choose when to use cards, tabs, chips, forms, tables, drawers, and sidebars

References

Read these references as needed, in this order for broad UI work:

  1. references/saas-ux-design-system-skills.md Full product UI system, philosophy, tokens, component rules, responsiveness, and defaults.
  2. references/typography-system.md Typography hierarchy, scale, weight, spacing, and SaaS readability rules.
  3. references/flexibility-system.md Flexibility and responsive-layout rules for resilient SaaS UI.
  4. references/design-tokens.css Concrete token defaults for color, type, spacing, radius, and depth.
  5. references/component-spec.md Shared component rules and expectations for buttons, inputs, navigation, tables, and more.
  6. references/page-blueprints.md Page-level composition patterns for landing pages, pricing, features, docs, dashboards, builders, settings, and data views.
  7. references/video-alignment.md Notes showing how the bundle aligns with the original typography/flexibility direction.

Use assets/default-saas-tokens.css when the task needs a ready token starter file rather than only conceptual guidance.

Constraints

  • Prefer existing product patterns and tokens when working inside an established app.
  • Do not invent decorative styles that break the system just to make one screen feel different.
  • Avoid loud color, visual noise, and concept-art styling unless explicitly requested.
  • Keep output production-ready and workflow-oriented.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.