designing

Designs and builds distinctive visual surfaces through a five-phase loop with rendered critique and QA.

1|Updated Sep 10, 2026
One-click install
npx skills add https://github.com/blauwtje/exo --skill designing-blauwtje
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: designing
Source: https://github.com/blauwtje/exo/tree/main/skills/designing
Command: npx skills add https://github.com/blauwtje/exo --skill designing-blauwtje

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, playwright-core, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Web pages and components often end up looking like interchangeable templates: default palettes, generic card layouts, and visual choices with no connection to the subject. This Skill replaces that with a disciplined visual design workflow where every choice traces back to the brief, the audience, or the page's job, and the result is verified against rendered screenshots rather than assumed. ## Core Features & Use Cases - Five-phase design loop: context inventory, direction decision, build, rendered critique, and QA, with each phase loading only the reference material it needs. - Request sizing and routing: distinguishes tweaks, new pieces, sketches, and full or bounded redesigns, and routes tool surfaces versus expression surfaces to different direction strategies. - Deterministic verification scripts: capture screenshots at multiple viewports, run static and rendered UI checks (contrast, clipping, overlap, template tells), and assemble checkpoint evidence for a design critic. - Use Case: A landing page is reported as generic. The Skill inventories the baseline, decides a direction backed by evidence, builds it, captures before/after renders at mobile and desktop widths, and runs accessibility and anti-template checks before shipping. ## Quick Start Ask the AI to redesign the pricing page so it no longer looks like a generic template, and let it run the design loop with rendered checkpoints.

Frequently Asked Questions about designing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I redesign a web page that looks generic or template-like?▼

Run a bounded redesign: capture baseline renders, inventory the existing direction as evidence, decide a new direction traceable to the subject and audience, then build and critique the rendered result. The workflow verifies the outcome is not materially interchangeable with the baseline.

How to check a web page for accessibility issues beyond automated scans?▼

Open every reachable state such as dialogs and menus before scanning, since scanners skip hidden regions. Then verify keyboard contracts for composite widgets, 320x256 reflow, text-spacing overrides, and status messages reaching the accessibility tree without moving focus.

What tools capture deterministic screenshots of web pages for design review?▼

The capture script drives a browser through a capability ladder: an obscura CDP server, project-installed Playwright, playwright-core with a system Chrome binary, or a screenshot-only Chrome CLI fallback. It records viewport geometry, hashes, and which rung actually ran.

Does the screenshot capture work without Playwright installed?▼

Yes, it falls back to a Chrome, Chromium, or Edge binary found at platform-known paths or named by CHROME_PATH, running screenshot-only headless captures. Full-page captures and dark color scheme emulation require a driven rung such as Playwright.

When should a visual change not become a full redesign?▼

When only one element or named visual property changes and no region is added, it is a tweak: change it, audit the touched surface, and stop. Expanding a tweak into a redesign is explicitly prohibited by the workflow.