Review an existing interface component and identify three visual or interaction problems. Get concrete layout, spacing, color, and code changes that follow the project’s existing design conventions, with short before-and-after examples.
Critique and improve the visual design of an existing UI component with concrete implementation guidance. Use when the user asks to redesign, restyle, reimagine, polish, or improve a component, screen, or interface, especially in React and Tailwind codebases.
Run score Not tested
See how to installThis skill inspects an existing UI component and its surrounding layout, then identifies three specific visual or interaction issues. It considers hierarchy, spacing, contrast, alignment, and responsiveness. For each issue, it suggests layout or Tailwind changes and provides a short before-and-after excerpt showing the meaningful class or structure changes.
Use it to refine a screen that already works, or when feedback says an interface is hard to read but does not identify what to change. It is especially useful in React and Tailwind projects, where improvements should follow existing color and spacing tokens and component conventions.
The skill needs to inspect the actual component and surrounding code. If you also ask it to implement the changes, it follows the repository’s required UI verification process afterward.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 29, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Inspect the real component and its surrounding layout before proposing changes. Reuse the repository's existing design tokens, primitives, and component conventions.
Respond in this order:
Keep the critique concise and grounded in the current code. Do not invent a new visual language when the repository already provides one.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review how you use Superset and identify unused features that fit your workflow. Get a short list of suggestions, learn about each option, and set up selected features such as scheduled agents, parallel workspaces, or shared tasks.
Set up recurring tasks in Superset with an agent prompt, a schedule or event trigger, and a chosen execution workspace. After explicit confirmation, create the automation, check its saved settings, and review a real first run.
Browse pages, click controls, fill fields, and inspect screenshots or console messages through Superset's browser pane. Use it to preview a running web app, check interface behavior, and work through browser tasks in a visible session.
Build Stripe payments, subscriptions, and invoicing using verified documentation and API parameter definitions. The skill guides product selection, sandbox testing, and webhook handling, where server notifications determine payment and subscription state.
Verify a UI change or reproduce a bug in the running desktop app using the Chrome DevTools Protocol (CDP), a browser debugging interface. Follow the real user journey and compare screenshots with measurements such as route, scroll position, and persisted state.
Diagnose failed GitHub Actions runs by finding the first meaningful error, separating code problems from infrastructure issues and intermittent failures, and comparing the base branch. Get a focused report explaining the PR’s involvement and recommended next steps.