Art & Design

Make or update a Webflow site's style guide page in the one fixed layout every site uses (a sidebar of sections, each section a list of rows with the name on the left and the live specimen on the right), first in the localhost prototype and then in Webflow at /design/style-guide. Use when starting a project's style guide, when the style guide is the first page of a prototype or of a Webflow build, when a new class or component needs its row, when checking that every class is on the page before running Webflow's "Clean up unused styles", or when adding a style guide to an existing site.

Architecture and flow visualization pattern. Generates standardized, syntactically valid Mermaid and C4 diagrams for system designs, data flows, and state machines.

Design, build, and review SaaS and internal web application UI that people use for work and agents can operate - app shells and navigation, list and detail views, data tables with sorting, filtering, bulk actions and pagination, empty states, settings, onboarding, roles and permissions, workspace or tenant switching, optimistic updates and undo, command palettes, and URL-driven view state. Use whenever building or reviewing an admin panel, CRM, back office, internal tool, project tracker, or any logged-in product ("build me an admin for orders", "our app feels clunky", "add bulk delete", "make the table filterable", "add an org switcher"), even when the request names only one screen. Not for KPI and monitoring pages (dashboard-design), forms and wizards in depth (form-design), marketing pages (landing-page-design), native desktop shells (desktop-app-design), or AI chat surfaces (ai-chat-design).

UX design guidance and strict UI reviews based on the 30 Laws of UX (lawsofux.com). Advises on a product or design direction, guides UI design and front-end implementation, and reviews a design, prototype, screenshot or UI diff before commit. Use whenever UX or usability input is wanted, or when a specific law is named — Fitts, Hick, Jakob, Miller, Tesler, Postel, Parkinson, Pareto, Occam, Doherty, Zeigarnik, Von Restorff, peak-end, serial position, goal-gradient, aesthetic-usability, choice overload, chunking, cognitive load or bias, working memory, mental models, flow, selective attention, paradox of the active user, or the Gestalt laws of proximity, similarity, common region, uniform connectedness and Prägnanz.

Restyle a chosen portion of an existing UI as a High Renaissance scientific manuscript, after Leonardo da Vinci's working notebooks (the Windsor sheets, Codex Leicester, the Vitruvian Man, Codex Arundel, Codex Forster) with four paper presets (iron gall ink faded to browns on laid rag paper, freehand rules, hatched shading, margin notes, decorative mirror script, pen sketches, an asymmetric working-page layout). Use when the user asks to turn a component, section, page or screen into a "manuscript", "Leonardo", "da Vinci", "Renaissance notebook", "codex", "old paper sketchbook", "sepia ink" or "parchment sketch" style, or runs /verso or /manuscript-ui with a target. Converts only the portion named, keeps the content, semantics and behaviour, and keeps every piece of real text readable.

Curated, up-to-date knowledge of UI component libraries, animation libraries and building blocks (icons, charts, tables, forms, toasts, drag-and-drop, virtualization, rich text) for web (React, Next.js, Vue, Svelte, Solid, Angular) and mobile (React Native/Expo, Flutter, SwiftUI, Jetpack Compose), with a decision process for picking one. Use this whenever a project is being started or scaffolded, when the user asks "which UI library / component library / design kit should I use", compares libraries (shadcn vs MUI vs Mantine, Tamagui vs NativeWind, etc.), needs a specific widget (date picker, data table, command palette, carousel, bottom sheet, chart), wants "cool animated components", or when you are about to hand-roll a component that a mature library already solves well.

Improve or review visual and interaction details in an existing interface. Use for UI polish involving typography, component surfaces, icons, states, motion, and responsive behavior; do not use for a full visual redesign.

Reverse-engineers a software repository into an accurate, interactive UML class diagram (one self-contained HTML file) - classes, interfaces, enums, attributes, methods, visibility, inheritance, associations, aggregation, composition, dependencies, multiplicities and database/ORM relationships, every element traced to its source file and line - with search, filters, a magnifying lens, in-diagram editing, change detection and SVG/PNG/JSON/HTML exports. Use when the user wants to visualize, document, understand or review a codebase's architecture, class model, domain or entity model (ERD), dependencies or dependency cycles, or asks for a UML class diagram of a project. Supports Java/Spring/JPA, Kotlin, TypeScript/JavaScript (Angular, NestJS, TypeORM), Python (Django, SQLAlchemy, dataclasses), C# (EF Core), Go (GORM), PHP (Doctrine, Laravel), SQL DDL and Prisma.

astudio UI/UX design intelligence for any interface task - designing, building, reviewing, auditing, critiquing, polishing or fixing pages, screens and components: hierarchy, layout, typography, colour, spacing, interaction, forms, navigation, states, accessibility (WCAG 2.2), responsive behaviour, motion and UX copy, backed by a searchable database (90 styles, 190+ product types with palettes and reasoning, 74 font pairings, 1900 Google Fonts with Cyrillic filter, 119 UX rules, landing patterns, chart guide, icons, GSAP presets, 22 stack guideline sets). Use when the user asks to improve or review a UI, "make it look better/premium/less generic/less AI", audit accessibility or UX, fix a layout, choose a style/palette/fonts for a product, "проверь интерфейс", "улучши UI", "сделай красивее", "аудит UX", or for any focused UI decision outside the full astudio-aio pipeline.

The entry point for any UI/UX work on web or mobile — the end-to-end workflow (brief → direction → system → stack → build → motion → verify), industry standards and best practices (WCAG 2.2, Apple HIG, Material 3, Nielsen heuristics, Laws of UX, Core Web Vitals, forms, navigation, states, i18n), a pre-ship UI checklist, and a routing map telling you which specialized design/animation/color/library skill to load for each sub-task. Use this whenever you start or plan a frontend or mobile app, build or redesign screens, review UI/UX quality, answer "what's the best practice for X" in interface design, or when several design skills could apply and you need to decide which.

Use the smallest visual when prose must carry structure—control flow, call depth, module ownership, or change shape: pseudocode, call tree, component/file tree, Mermaid diagram, or diff. Skip it when prose already answers the question.

Design, build, and review forms and multi-step flows that people finish without errors and agents can fill without guessing - sign-up and sign-in, checkout and payment details, address and contact forms, applications, onboarding questionnaires, wizards, settings forms, validation and error messages, passwords and passkeys. Use whenever someone builds or fixes a form ("add a sign-up form", "our checkout converts badly", "make these errors better", "why won't autofill work", "turn this into a wizard"), even if they only mention one field. Includes a rendered-page checker for labels, autocomplete, input types, paste, and error wiring. Not for the surrounding app shell, tables, or settings navigation (web-app-design), store layout and product pages (ecommerce-design), or native desktop dialogs (desktop-app-design).

Product designer (usability, accessibility, design patterns, design systems, component design, Figma). Builds the design system, components, micro-animations, responsive screens and full flows directly in Figma from the requirements, with implementation metadata for a frontend skill. Use 'designer system', 'designer design [feature]' or 'designer review <target>'.

Create, extend, or audit a design system for any project and platform — design tokens (color, typography, spacing, radius, elevation, motion, breakpoints), token architecture (primitive → semantic → component), the W3C DTCG token format, theming (light/dark, brands, density), multi-platform output (CSS variables, Tailwind v4 @theme, React Native, Flutter, SwiftUI, Compose), component API conventions, documentation (DESIGN.md, Storybook) and governance. Use this whenever the user starts a new app and needs a visual foundation, says "design system", "design tokens", "theme", "style guide", "UI kit", "make it consistent", "set up Tailwind theme", wants to unify inconsistent UI, extract tokens from existing code or Figma, support dark mode or multiple brands, or share styles between web and mobile.

Check a design artifact in a real browser before handing it over — console errors, broken assets, overflow, then a visual review of the screenshot. Read before delivering anything.

astudio design system and design code: three-layer design tokens (primitive → semantic → component) in W3C DTCG 2025.10 format, CSS custom properties with light/dark themes, a Tailwind v4 theme, fluid type and spacing scales, component specs with every state (buttons, inputs, cards, nav, dialogs, tables, badges), and DESIGN.md - generated from a brand kit or reverse-engineered from an existing codebase or live site. Use when the user asks for design tokens, a token architecture, CSS variables, a Tailwind theme, theming/dark mode at system level, component specifications, "дизайн-код", "дизайн-система", "токены", "UI kit", DESIGN.md, or wants hard-coded values replaced with tokens. Part of the astudio-aio pipeline (after brand, before the site build).

Build a slide presentation as one self-contained HTML file at 1920x1080, with keyboard navigation and one-page-per-slide printing. Read before making any deck or presentation.

Choose and commit to a visual direction when there is no brand or design system to follow. Read for any open-ended design ask.

Build a design system as two CSS files other apps can copy — tokens.css (custom properties) and components.css (classes built on them) — documented by a specimen page. Read before designing anything that will have more than one screen, and whenever the project has no existing system.

Build a printable document — report, memo, proposal, letter, one-pager — as one self-contained HTML file that prints cleanly to A4 or Letter. Read before making any document deliverable.

Builds client-facing PowerPoint decks (.pptx) from data or notes: the answer up front, one idea per slide, sentence headlines, a source on every number, and speaker notes. Use when asked for slides, a deck, a presentation, a QBR or a client readout.

Use when the user wants a prototype, mockup, clickable demo or "something to show" for an item with approved behaviour trees. Step 4 of the one-shot pipeline - builds a self-contained clickable HTML prototype where every tree branch can be demonstrated, and proves that coverage with the checker.

Color theory and palette engineering for UI on any platform (web, iOS, Android, Flutter, React Native). Choose and derive brand palettes, build tonal ramps, tinted neutrals and status colors, map them to light/dark semantic tokens, and verify contrast (WCAG 2.2 + APCA) and color-blind safety with a bundled zero-dependency OKLCH tool. Use this whenever the user picks, generates, critiques or fixes colors — "what colors should I use", brand color, palette, color scheme, theme, dark mode colors, accent, gradient, "this looks dull/garish", contrast problems, color-blind friendliness, or turning one hex into a full system — even if they don't say "color theory".

Create a complete brand identity as real, usable files - strategy and vibe, a verified color system (OKLCH ramps, light and dark themes, WCAG-checked roles), typography, a professional logo in SVG (from a clean wordmark or geometric mark to a complex, meaningful symbol), favicons, app and social assets, design tokens, and a brand guidelines page. Use whenever someone asks for a logo, brand, brand kit, identity, color palette, theme, font pairing, visual direction, "vibe", rebrand, favicon or app icon, or says things like "make it look like a real company", "I need branding for my bakery/app/startup", or "what colors should we use", even if they only ask for one piece. Not for laying out pages or screens; those skills (landing-page-design, web-app-design and siblings) consume the tokens this one produces.