Art & Design

Expert UX design thinking, user psychology, and experience strategy. Activates when building, reviewing, or discussing any user-facing interface -- websites, apps, dashboards, forms, onboarding, checkout, sign-up, settings, landing pages, modals, navigation. Triggers on: user flows, wireframes, prototypes, usability, information architecture, content strategy, error handling, accessibility, interaction design, user testing, conversion. Also activates on: 'how should this flow', 'user experience', 'make it easier', 'onboarding', 'conversion', 'drop-off', 'friction', 'confusing', 'intuitive', 'usability', 'user journey', 'review screen', 'review interface', 'UX audit'. Applies whenever a human uses an interface, even without saying 'UX'. Hands off to ui-designer for visual styling and craft. Hands off to ux-research for evidence gathering and discovery. Hands off to design-system for component infrastructure. Do NOT activate for: purely visual styling, backend logic

Audit and improve an existing web app's UI and UX while preserving its design language. Use for polish passes, inconsistent typography or icons, cramped panes, weak contrast, awkward controls, snapping menus, and requests to make a shipped interface feel more considered. Covers visual hierarchy, control geometry, pane-aware layout, interaction states, and motion. Prefer a design-direction skill for a new visual identity and a performance skill for load-speed work.

Single entry point for every glass GLSL shader, from words or an image. Picks the shape (animated liquid glass background via glsl-liquid-glass; 3D glass letters in any font or vibe via glsl-sdf-typography, with dots and accents replaced by shapes via glsl-sdf-shapes; a glass card, button or panel via glsl-glassmorphism) and the kind of glass (plain liquid, shard / broken glass, prism, crystal / gem), recognized automatically from the words or a reference image. Always delivers GLSL code. Understands the short syntax /liquid-glass-skill 'happy birthday' letter i in birthday shape heart background purple glass crystal, as well as plain sentences. Use when the user runs /liquid-glass-skill, or asks for any glass, liquid glass, glassmorphism, crystal, prism, gem, shard or broken glass shader, background, card, button, word, name, title or sentence, or shares an image of glass.

Audit, document, or extend a design system's tokens, components and patterns. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, props and accessibility, or designing a new component or pattern that fits the existing system instead of duplicating one.

Deciding how a screen looks and behaves, triggered by the moments that hand the decision to the user unworked: about to ask which layout, which colour, which placement, how to draw a diagram, how wide a pane, how to split a view; about to call a visual choice a matter of taste; about to treat "it looks fine" as having checked it; about to ship a control sized by eye; about to read an automated accessibility pass, or a Lighthouse score of 100, as a clean bill of health. Most of these have an answer in a published standard, a measurable threshold, or one screenshot — WCAG 2.2 fixes contrast, target size, reflow and focus; a design system fixes spacing and components; axe-core finds about 57% of WCAG issues, and Lighthouse's accessibility score is that same engine weighted, so both leave the rest to a person. What survives is a genuine question, asked with the evidence attached. Use before asking any question about appearance, layout or interaction, and before calling

Audits and fixes the "AI look" in mobile apps built with Expo/React Native, Flutter, SwiftUI or Jetpack Compose, using sourced Apple, Android and framework rules. Use when the user asks to unslop, polish, de-AI, audit, review or score a mobile app, to "make it feel native", or says a generated app looks like a website in a phone frame. Typical tells it fixes: purple gradients, glass cards, emoji icons, tiny touch targets, taps with no feedback, no haptics, no dark mode, centered popups instead of sheets, hamburger menus, ignored safe areas, keyboards covering fields, broken back navigation, text that cannot scale. Not for web apps, desktop apps or backend code.

Writes any word, name or sentence as 3D liquid glass lettering in GLSL, in any real font (Google Fonts by name, a font file, or a vibe such as romantic, cloud, medieval, cartoon) or in hand-built neon tubes, filled with the moving liquid glass surface, on a solid background color (black by default) or on the user's own image, with a ready-to-open HTML preview. Reads plain-language requests or the /liquid-glass-skill short syntax to find the text, the background color and which letter marks (i/j dots, punctuation dots, accents) to replace with shapes from glsl-sdf-shapes. Use when the user asks to write, spell or render a word, name, title, phrase or sentence in glass, GLSL or SDF, or to replace the dot or accent of a letter with a heart, star or other shape.

Run a recursive, evidence-driven visual polish loop on a web UI. Audit every page, theme and state against a quality bar (palette, contrast, surfaces, typography, spacing, component states, focus), prototype genuinely different directions on the real pages, implement the winner through design tokens, then capture, have independent reviewers scrutinize, fix and repeat until a round comes back clean, and deliver a PR with before/after evidence and metrics. Use this whenever someone asks to polish, refine, clean up, unify, uplift or "make seamless" a UI, theme, palette or colour system, close a quality gap between two themes or screens, do a design or finish pass with high scrutiny, or says "visual clean loop" / "visual polish loop", even if they only mention colours or say it "doesn't feel as polished as" something. Not for building new features or single-bug visual fixes.

Create a modern design system for any product or company, or audit an existing codebase or live URL and recommend better design choices, tokens and components.

Art direction and a checked build process for web pages that look designed for their subject instead of generated: landing pages, marketing and product sites, portfolios, multi-page sites, single sections, brand kits (elements, palette, type, a placeholder wordmark on a board), and improving, restyling, redesigning or reviewing an existing web UI or app screen. Use it whenever the user asks to design, build, redesign, restyle, polish, review or audit a web page, site, hero, section or dashboard, or says a page looks generic, templated or AI-made. Every run researches the business, competitors and customers, builds a storyline that serves both the business and the customer, roasts its own plan, applies the team's taste and the client's brand, asks the designer at short gates, checks the result in a real browser, and returns the research with the work. Not for backend work, data pipelines, slides or documents.

Full security audit (34 checks) for web apps built with AI tools (Lovable, Bolt, Base44, Cursor, Replit, Claude Code). Really checks each hole in the code and live site — exposed keys and files, Supabase/Firebase RLS and storage, reading other users' records, unprotected APIs and admin pages, login decided in the browser, forgeable payments and prices, signup/AI abuse, XSS, SQL injection, SSRF, uploads, vulnerable or AI-hallucinated packages, prompt injection and over-powered AI agents, poisoned AI rules files, risky MCP servers, security disabled by AI, HTTPS, WAF, backups. Ends with a red/orange/green summary in the chat. Use whenever the user asks to check, audit, scan or secure an app or website, asks "is my app safe / can someone hack it", mentions RLS, API keys, Stripe webhooks, admin pages, fake signups or vibe-coding security, or says בדיקת אבטחה / תבדוק לי את האבטחה / לאבטח את האפליקציה / האם האתר שלי מאובטח — even without the word "audit". Also use before a launch and after AI changed the code.

使用 QBoson Kaiwu SDK（Enterprise/Community）将组合优化问题建模为 QUBO/Ising，处理约束、精度、版本兼容与求解结果。适用于选址、调度、路径、覆盖、布尔规则、Max-Cut、混合离散连续优化，或修复 kaiwu 建模/求解 API。PyTorch 能量模型与 RBM/BM/DBN、QVAE、QDiffusion 使用独立的 kpp-coding-skill。

Lay out web UI with a spacing scale, clear grouping, alignment, grids, containers, tables and responsive structure that holds from 320px phones to wide desktops. Use when creating a page, section, form or dashboard layout, or when changing spacing, alignment, grids, containers or responsive behavior in React, Next.js, Tailwind CSS or CSS: spacing feels random, cramped or too loose, things do not line up, a layout breaks on mobile, or the user mentions padding, margins, gaps, grid, whitespace, density or responsive design. Skip it for edits that leave layout untouched.

Set up and fix typography in web UI: choose and load fonts, build a type scale of named roles, set line height, letter spacing, measure and line breaks, and style numbers, links and code. Use when creating a page, section or component, or when changing fonts, text sizes, hierarchy, line height, tracking, text wrapping or font loading in React, Next.js, Tailwind CSS or CSS, or when headings or body text look off, cramped, generic or hard to read. Skip it for edits that leave text styling untouched.

Turn a Figma website design (landing page, marketing site, company profile, portfolio) into a running, responsive website prototype on localhost or as a Claude artifact. Use when the user shares a figma.com link and wants it built as a website, coded, prototyped, or "made real". Desktop-first with human checkpoints (plan, layout, desktop), placeholder-first layout before asset import, semantic renaming of messy Figma layers, a Figma-vs-normalized typescale switch (Cmd+\), and token-budget rules.

把一只股票、一份财报、一条并购/重大新闻，或任何学习资料（文章、论文、技术文档、研报、课程笔记），做成一遍就能看懂的卡通手绘图解 HTML 页面（单文件、深浅两套主题、可发布为 Artifact）。股票类默认产出完整图解报告：体检单、核心竞争力、技术规划路线、远期规划、隐藏危机、关键时间节点、股价推演、估值尺子。当用户说\"图解一下\"\"做成图解页面\"\"帮我一遍看懂\"\"ELI5 这份资料\"\"零基础讲讲这个\"\"分析一下这只股票 / 这份财报 / 这条新闻\"\"基本面变了吗\"\"这家公司的护城河、风险、催化剂是什么\"，或要求把文章、论文、财报、技术文档做成可视化学习页时使用。Also use for English requests like \"explain this stock / earnings report / merger visually\", \"make an illustrated explainer page\", \"ELI5 this filing\".

Builds Apple-style Liquid Glass UI (iOS 26 / macOS 26 look) on any platform. Web, Android WebView, Electron, Capacitor and Cordova get a ready, tested engine with real refraction, specular rims, merging drops and iOS-like stretchy buttons, toggles, sliders and tab bars. Jetpack Compose uses Kyant's Backdrop library; SwiftUI, UIKit and AppKit use the system glassEffect. Use whenever the user asks for liquid glass, Apple or iOS 26 glass, glassmorphism, frosted glass, a glass tab bar, glass buttons, toggles or sliders, or "make it look like Apple", even if the words Liquid Glass are not used.

Fast path for preparing a website's media and getting it live - compressing images and video for the web, writing matching image and video prompts for a generator such as Google Flow, the phone, polish, speed and security passes, search and sharing metadata, and deploying to Vercel. Use when the user asks to optimise or generate images or video, audit or polish an existing site, check for leaked keys, set up SEO or link previews, or launch. For a whole new site use futuristic-web-design instead.

Use when the user wants a clickable product prototype or design mock-up (web app, phone app, tablet app, or several at once) and wants it organised by user story. Builds one self-contained HTML file with a device switcher (website / Android / iPhone / iPad) and a story switcher, so reviewers can pick a story and walk through exactly the screens and data that story needs on every device, alongside its acceptance criteria, priority, status and notes. Also use when adding, changing or splitting stories in such a prototype.

Fast path for adding, restyling or rebuilding one section of an existing website (navigation, hero, trust strip, products, story, testimonials, FAQ, contact, footer) or for comparing layout options side by side. Use when the site and its design rules already exist and the user wants a single section built, changed or shown in a few variants, including a contact form that saves to a database. For a whole new site, a redesign, or a site that looks generic, use futuristic-web-design instead.

Fast path for adding one cinematic technique to an existing website - a slow background video hero, scroll-tied motion, a pinned scroll story with GSAP ScrollTrigger, parallax depth, a procedural 3D accent with Three.js or React Three Fiber, or a video scrubbed by scroll. Use when the user asks for scroll animation, a pinned or sticky section, parallax, a 3D object, or a video that plays as they scroll, on a site that already exists. For a whole new site use futuristic-web-design instead.

Build cinematic, futuristic-feeling marketing websites and landing pages end to end without the generic AI look - brief, design system, section-by-section build, AI image and video prompts for the site's visuals, scroll storytelling, a 3D accent or scroll-driven video, mobile polish, a contact form wired to a real database, deploy, domain and launch checks. Use this whenever the user wants a website, landing page, homepage, portfolio or business site built or redesigned, asks for a hero section or any page section, says cinematic, premium, futuristic, 3D, scroll animation, parallax, pinned section or Awwwards-style, wants prompts for hero images or hero video, or complains that a site looks generic or AI-made - even if all they say is "make a website for my cafe".

Recreates or builds UI designs in Sketch from a reference URL, screenshot, or source code with side-by-side screenshot fidelity validation using Sketch MCP (`get_document_info`, `get_layer_tree_summary`, `get_screenshot`, `get_design_assets`, `get_symbol_overrides`, targeted `run_code`). Use when the user wants to design, mock up, or reproduce a page or screen in Sketch from the web, an image, or code.

Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established visual direction. Skip when they have a design mockup, need a dashboard or app UI, are working at component level, building a multi-page app, or restyling with known design tokens — use frontend-design instead.