agentleFS
Sign inStart free
YangsonHungYangsonHung/awesome-agent-skills/skills/en/ui-layout-analyzer/SKILL.md

ui-layout-analyzer

Skill18 starsChanged 6 days agoMITView on GitHub

Use when analyzing a UI screenshot to describe layout structure and interface functionality.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user provides a UI image and requests analysis.

    line 14
  2. Distinctive:

    Do not use this skill for:

    line 18
  3. Distinctive:

    Follow this format exactly:

    line 25
  4. Distinctive:

    Use Arabic numerals for section numbers (1, 2, 3...)

    line 80
  5. Distinctive:

    Keep descriptions concise but complete

    line 81

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

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

UI Layout Analyzer

Overview

Analyze a provided UI screenshot and output a structured layout description plus functional analysis. The skill focuses on interface screenshots, describing page structure, visual sections, hierarchy, controls, and likely user workflows without designing new UI or reviewing implementation code.

When to Use

Use this skill when the user provides a UI image and requests analysis.

Do not use

Do not use this skill for:

  • Non-UI images (photos, diagrams, charts that are not interface screenshots)
  • Requests to design or create UI (use ui-ux-pro-max instead)
  • Code review of UI implementation (use code-reviewer instead)

Instructions

Follow this format exactly:

## UI Layout Description

### Overall Structure
Describe the overall structure type (modal dialog/full page/sidebar/drawer), background color, rounded corners, shadows, etc. End with "---".

---

### Section N: Section Name
- Specific description items
- Use bullet points for key elements

[Continue describing each section...]

---

## Function Description

| Function Module | Description |
|---|---|
| **Module Name** | Function description |

Analysis Steps

1. Identify Overall Structure

  • Page type: Modal dialog / Full page / Sidebar / Bottom drawer
  • Background: White/gray/gradient/image background
  • Special elements: Rounded corners, shadows, borders, dividers

2. Divide into Sections

Identify sections top to bottom, each containing:

  • Section type: Header / Tab bar / Content area / List / Table / Input area / Action bar
  • Key elements: Icons, text, buttons, input fields
  • Layout: Left-aligned/centered/right-aligned, horizontal/vertical

3. Identify Interactive Elements

  • Buttons: Primary (filled) / Secondary (text) / Icon buttons
  • Inputs: Single-line/multiline text/dropdown/date picker
  • Selectors: Radio/checkbox/switch/tab switch
  • Lists: List items, grid layout, card layout

4. Describe Functions

Infer functions from visual elements:

  • Form: Input, validation, submit
  • Navigation: Jump, tab switch, back
  • Display: List, detail, carousel
  • Feedback: Toast, modal, loading state

Notes

  • Recognize and include all text visible in the image
  • Mark states (disabled/selected/expanded) when visible
  • Use Arabic numerals for section numbers (1, 2, 3...)
  • Keep descriptions concise but complete

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.

Check your setup, free