Oil UI guides an agent through designing, refining and reviewing websites, apps, dashboards and components. It sets a one-sentence visual north star first, then shapes layout, type, color, media and interaction around it, and judges the result from real browser screenshots.
It also builds a side-by-side comparison page of three distinct directions when you ask, flags conflicts between design documents such as DESIGN.md, and runs a read-only review mode that gives evidence and advice without touching files. The skill text is written in Chinese and replies in the language you use.
What You Get
- A single visual direction stated up front, or three clearly different directions on one comparison page when you ask
- Desktop and mobile screenshots of the built page, inspected before the result is handed over
- A read-only review with evidence and ranked advice when you only want critique
- A delivery note listing what was built, what was not done and up to three suggested next steps
Common Use Cases
- Design a new landing page or product screen from a blank start
- Compare three styles for the same page and pick one
- Polish an existing dashboard or component without changing its logic
- Recreate a page from a screenshot with a mobile layout
- Review a homepage and get written changes without edits
What Makes It Unique
The skill separates how an interface looks from whether its tasks work, and gives each its own acceptance step. Page type decides what the first screen must contain: persuasion pages follow a chosen opening layout, while tool and browse pages put the first row of content on screen one. Explicit comparisons require the three directions to share at most one trait between any two, and a separate reviewer without build history scores the result.
Under The Hood
SKILL.md is a router that reads a short light-path file for common tasks and loads other references only when a situation calls for them. Its frontmatter allows shell calls to a version-check script, which reads a public version list on the Oil UI site, caches the result under a state folder in your home directory and only notifies you; it updates nothing unless you ask. Optional helper scripts in the folder take screenshots with a local Chrome, curate and prepare media, build the comparison page, and call an image-generation service that spends credits when you have authorized it. The agent writes comparison pages, screenshots and intermediate files to a working folder named .oil-ui in your project, and final code to your project files.