Loading...
Loading...
Found 552 Skills
Evaluates interfaces, components, screens, and flows against universal UX/UI principles (heuristics, UX laws, Gestalt, cognitive psychology, accessibility) and delivers concrete, prioritized improvements. Use whenever the user shares UI code, screenshots, components, or mockups and wants feedback — even if they don't use the words "critique" or "review". Also trigger when the user asks "what's wrong with this UI", "how can I improve this", "review my component", "does this look right", "give me feedback on this design", or shares any interface and asks for thoughts. Trigger for partial slices too (a single button, form, or card) — not only full screens.
Deep UI walkthrough with screenshot-based analysis across all pages and viewports (desktop + tablet + mobile). Delivers per-page improvement pitches grounded in what you actually see. Use when user says 'review the UI', 'pitch UI improvements', 'how does this look', 'UX audit', 'walk through the app'.
Build web interfaces with genuine design quality, not AI slop. Use for any frontend work - landing pages, web apps, dashboards, admin panels, components, interactive experiences. Activates for both greenfield builds and modifications to existing applications. Detects existing design systems and respects them. Covers composition, typography, color, motion, and copy. Verifies results via screenshots before declaring done.
Self-healing browser automation framework that connects LLM agents directly to Chrome via CDP. Use when the user needs autonomous browser tasks, clean browser verification, Codex or Antigravity browser control, Claude-safe screenshots, adaptive helper code in `agent_helpers.py`, domain skills, or Browser Use Cloud escalation. Triggers on: browser-harness, self-healing browser, llm browser automation, cdp agent, chrome devtools agent, codex browser automation, antigravity browser automation, claude screenshot error, claude image error, agent browser task, browser-use harness, domain skills browser.
Implements visual regression testing with screenshot comparison, diff detection, and CI integration using Playwright or Chromatic. Use when users request "visual testing", "screenshot testing", "UI regression", "visual diff", or "Chromatic setup".
Metadata and localization sync (including Fastlane format) for Google Play Store listings. Use when updating app descriptions, screenshots, or managing multi-locale metadata.
Use when "improving image quality", "enhancing screenshots", "upscaling images", "sharpening photos", or asking about "image optimization", "screenshot quality", "resolution improvement"
ブラウザを手足のように操る。ページ遷移、フォーム入力、スクショ、なんでもこい。Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include 'go to [url]', 'click on', 'fill out the form', 'take a screenshot', 'scrape', 'automate', 'test the website', 'log into', or any browser interaction request. Do NOT load for: sharing URLs, embedding links, screenshot image files.
Creates and authors slide deck presentations using the PromptSlide framework (Vite + React 19 + Tailwind v4 + Framer Motion). Use when the user wants to create a new slide deck, add or edit slides, customize themes or branding, work with slide animations and transitions, capture slides as images, or visually verify slide appearance. Triggers on mentions of slides, decks, presentations, PromptSlide, slide screenshots, or slide-related tasks.
Audit and fix responsive/mobile issues across every page of a project, using Chrome MCP screenshots at two breakpoints (375px mobile, 1440px desktop). Design-aware: reads existing design docs to preserve aesthetic intent, not just "make it fit." Use when asked to "make it responsive", "fix mobile", "responsive audit", or after building a desktop-first UI that needs mobile adaptation.
Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead.
Load this skill whenever the user wants to control, automate, or interact with a phone or mobile device. This includes: tapping, swiping, typing, taking screenshots, reading the screen, managing apps, running AI agent tasks on a phone, or any form of phone/mobile automation. Also load when the user mentions Mobilerun, Droidrun, or phone control. Requires a Mobilerun API key (prefixed dr_sk_) and a connected device.