freemcplab / Directory / Playground / OilOil UI/UX Guide

● Community oil-oil ⚡ Instant

OilOil UI/UX Guide

Name: OilOil UI/UX Guide (Claude Skill)
Author: oil-oil

Modern UI/UX guidance covering CRAP, HCI laws, and design system thinking.

A skill that teaches Claude design fundamentals — CRAP principle, Hick's law, Fitts's law, Gestalt — and how to apply them to wireframes and component design. Catches the 'AI design slop' that makes everything look like the same dashboard.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

CRAP principle checklist (Contrast, Repetition, Alignment, Proximity)
Common HCI laws with concrete examples
Design system thinking (tokens, components, patterns)
Critique mode: 'review this UI against these principles'
Pairs well with frontend code-gen skills

Live Demo

What it looks like in practice

oiloil-ui-ux-guide-skill.replay ▶ ready

0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use OilOil UI/UX Guide

Have Claude critique a UI screenshot against design principles

👤 Solo devs without a designer ⏱ ~15 min intermediate

When to use: You built a screen and want a structured critique before shipping.

Prerequisites

Server/skill installed and authenticated — See repo README

Flow

Submit

Using the UI/UX skill, review attached screenshot of the settings page.✓ Copied

→ Critique grouped by CRAP + HCI laws
Prioritize

Rank the issues by impact and tell me the top 3 to fix.✓ Copied

→ Top-3 list with reasoning

Outcome: A short, ranked action list rather than 30 vibes.

Pitfalls

Visual critique from a screenshot misses interaction issues. Pair with a real Playwright walkthrough for flows. — Visual critique from a screenshot misses interaction issues. Pair with a real Playwright walkthrough for flows.

Cost & Limits

What this costs to run

API quota: See provider docs for rate limits
Tokens per call: Varies by tool
Monetary: See repo README for pricing details
Tip: Cache tool results and avoid repeated identical calls.

Security

Permissions, secrets, blast radius

Credential storage: Use environment variables; never commit secrets

Data egress: Tool calls go to the provider's API as documented

Troubleshooting

Common errors and fixes

critique is too generic

Provide the screen's purpose and audience. The skill's quality improves with context.

Verify: Re-run with context

skill doesn't see images

Ensure your Claude client supports image input; otherwise paste a Figma/HTML render.

Verify: Test with a plain image first

Alternatives