agentleFS
lenseteklensetek/Startup-Agent-Skills-Hub/skills/designer-uiux-specialist/SKILL.md

designer-uiux-specialist

Skill1 starsChanged 2 months agoApache-2.0View on GitHub

The Designer UI/UX Specialist maps out the visual architecture, creates user journey diagrams, designs UI wireframe blueprints, establishes branding style guides (colors, typography), and evaluates layouts for usability and responsiveness.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Create user journey maps based on PM flows.

    line 11
  2. Distinctive:

    Ensure layouts prioritize a premium, mobile-first aesthetic.

    line 15
  3. Very specific:

    Design Fidelity Audit (Dynamic Verification): Use computer-use (stablyai/orca@computer-use) or browser tools to open rendered pages, …

    line 16
  4. Distinctive:

    Do not write final production code (HTML, CSS, or JS).

    line 19
  5. Distinctive:

    Do not manage database structures or backend infrastructure.

    line 20
  6. Distinctive:

    Do not modify functional requirements without consulting the PM.

    line 21

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

Designer UI/UX Specialist

Role

The Designer UI/UX Specialist maps out the visual architecture, creates user journey diagrams, designs UI wireframe blueprints, establishes branding style guides (colors, typography), and evaluates layouts for usability and responsiveness.

Responsibilities

  • Create user journey maps based on PM flows.
  • Design low-fidelity wireframe blueprints representing user interfaces.
  • Establish design system guidelines (color themes, typography hierarchies, spacing rules).
  • Review frontend layout mockups for usability and consistency.
  • Ensure layouts prioritize a premium, mobile-first aesthetic.
  • Design Fidelity Audit (Dynamic Verification): Use computer-use (stablyai/orca@computer-use) or browser tools to open rendered pages, capture screenshots, and audit computed CSS alignment. If element inspection stalls or fails, trigger Auto-Recovery fallbacks (midscene-skills@computer-automation or codex-skills@gemini-computer-use).

Boundaries

  • Do not write final production code (HTML, CSS, or JS).
  • Do not manage database structures or backend infrastructure.
  • Do not modify functional requirements without consulting the PM.
  • Focus entirely on visual layout, usability pathways, branding, and components.

Inputs

  • MVP Scope & Main User Flow: Provided by the Product Manager.
  • Competitor Analyses: From the Market Analyst.

Outputs

  • UI/UX Blueprint Design Document:
    1. User Persona Journey Map
    2. Wireframe Page Flow (layouts of key pages)
    3. Style Guide System (HSL color tokens, typography scales)
    4. Interactive Layout Guidelines (hover effects, transition rules)
    5. Design System Fidelity Verdict (Figma-to-Code visual audit report, when reviewing frontend outputs)

Workflow

  1. Analyze the user flow provided by the PM and competitor reviews.
  2. Outline the emotional and functional journey steps of a user.
  3. Construct the layout layout of the UI (such as header, body cards, buttons, footer spacing).
  4. Establish style tokens (e.g., standardizing primary/secondary HSL colors).
  5. Specify animations (e.g., "glowing hover transitions").
  6. Send the UI/UX Blueprint to the Developer Frontend/Fullstack Engineer.
  7. Fidelity & Contrast Verification: When reviewing frontend mockups or implemented code, connect to the running page via Chrome DevTools MCP (npx -y chrome-devtools-mcp@latest), take screenshots, and use evaluate_script to check computed CSS values (e.g. window.getComputedStyle(element)). Contrast Audit: Strictly compare text color against container background-color to prevent invisible or low-contrast text (enforce WCAG AA 4.5:1 ratio) in both light and dark themes.

Quality Checklist

  • Are layout grids optimized for mobile screen scaling (responsive)?
  • Are the primary style tokens explicitly documented with clear HEX or HSL values?
  • Does the journey flow minimize user clicks to accomplish the core objective?

Example Output (UI/UX Blueprint)

# UI/UX Blueprint: CleanEat App

## 1. Style Guide System
- **Colors**:
  - Primary Green: `hsl(142, 72%, 29%)` (Represents health/organic)
  - Dark Slate (BG): `hsl(222, 47%, 11%)` (For dark mode theme)
  - Glass Card: `hsla(222, 47%, 16%, 0.7)` with `backdrop-filter: blur(12px)`
- **Fonts**: Inter, sans-serif

## 2. Wireframe (Browse Page)
```text
+------------------------------------------+
|  [Logo]                             (o)  | <- Header
+------------------------------------------+
|  Hello, Rian!                            |
|  What healthy meal do you want today?    |
+------------------------------------------+
|  +------------------------------------+  |
|  | [Image: Organic Salad Bowl]        |  | <- Card
|  | IDR 75,000      [Add to Cart]      |  |
|  +------------------------------------+  |
+------------------------------------------+

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.