This is the main entry point for the design-it skill system. Instead of falling back to generic "AI slop" aesthetics, you have access to 48 distinct, deeply opinionated design styles.
Use this skill when a user requests building any frontend interface (website, app screen, UI component) and you want to apply a specific, opinionated design aesthetic instead of generic defaults.
When a user asks you to build a frontend interface (web or app):
spatial-design, bento-ui, or glassmorphismtile-designsci-fi-interface or brutalist-typographyswiss-designcyberpunk-uiIf they don't specify a style, choose one that best fits the project context.
SKILL.md.If the user provides their own colors, use them. Otherwise, these ten illustrative palettes are optional starting points. No award provenance is claimed. Adapt their colors for the selected style, brand and measured contrast, and define reusable color tokens.
#F9F6F0#1B2A49#C85A32#E2D8C9#F4EFEA#2D2B2A#A65E44#8C8781#D1D1D1#111111#9A3B3B#757575#D9CBBF#4A362D#7A4C3A#948275#F7F5F0#3A4B3A#8A9A86#D3CEC4#F4F4F9#2B303A#5C6B73#C0C5C1#0A0A0A#F5F5F0#B59A5F#1C1C1C#E6E2DD#1F1C1B#524036#B8B0A8#EAEAEA#1C252E#C28F79#2C3E50#F9F9F9#121212#D44A3A#8F8F8FTo use a style, you MUST read its file at <style-folder>/SKILL.md relative to this file's directory.
minimalismflat-designflat-design-2material-designglassmorphismneumorphismskeuomorphismclaymorphismaurora-uibento-ui3d-uiisometric-designlayered-designfloating-uispatial-designswiss-designeditorial-designtypography-firstbrutalist-typographybrutalismneo-brutalismretro-designy2k-designcyber-y2kvaporwavesynthwavefrutiger-aeroretro-futurismdark-modemonochromatic-uigradient-designduotone-designcolor-blockingsoft-pastelhigh-contrastvibrant-maximalismmaximalismcyberpunk-uisci-fi-interfaceholographic-uiai-native-uispatial-computing-uidashboard-designcard-based-designwidget-based-designtile-designdata-dense-designcommand-center-uiUser request:
Review this interface with @design-it, identify the highest-impact design problems, and propose an implementation-ready improvement.
The style references are visual studies and partial snippets, not complete compiled applications. Imports, package versions, licensed fonts and image assets must be supplied by the project. Color(hex:) is a custom extension; use an explicitly implemented parser or RGB initializers. Framework APIs and shadow support vary by version and platform; legacy React Native shadow props do not describe all New Architecture capabilities.
Define the referenced CSS tokens in the project (for example --bg-primary, --primary-text, --text-primary, --secondary-base, --bg-surface and --cta-highlight); palette names alone do not declare these variables. A palette or native material does not establish contrast compliance.
Keep semantic buttons, labels, focus, keyboard activation and useful navigation even when the decoration looks raw or text-only. Empty callbacks, container-only buttons and gesture-only examples demonstrate appearance; connect real actions and cancellation-safe interaction state before use. Do not announce decorative duplicate text, glows, scanlines or icons as repeated content. Respect text scaling, safe areas and reduced-transparency settings. Avoid fixed layouts that clip essential content at narrow widths.
Animation is optional. Prefer stable essential text and controls, pause decorative loops when hidden, dispose controllers and stop loops on unmount, and provide a static reduced-motion version. Web animation examples should include a targeted fallback such as:
@media (prefers-reduced-motion: reduce) {
.aurora-blob, .cyber-y2k-btn, .max-sticker, .tile-live-content {
animation: none;
transition: none;
}
}
Use the corresponding native reduced-motion setting and keep a readable fallback for gradient/masked text. Styling choices do not replace accessibility testing on the target device.
Implementation references: Flutter component theme migration, Flutter child color filters, Android RenderEffect, and SwiftUI inner shadow style).