design▌

Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing.

Only code in HTML/Tailwind in a single code block. Any CSS styles should be in the style attribute. Start with a response, then code and finish with a response. Don't mention about tokens, Tailwind or HTML. Always include the html, head and body tags. Use lucide icons for javascript, 1.5 strokewidth. Unless style is specified by user, design in the style of Linear, Stripe, Vercel, Tailwind UI (IMPORTANT: don't mention names). Checkboxes, sliders, dropdowns, toggles should be custom (don't add, o

Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text / right-image), background-image freedom, varied CTAs, varied hero scales (giant / mid / mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.

Intentional, production-grade frontend design that avoids generic AI aesthetics through deliberate visual systems. \n \n Requires explicit aesthetic direction (brutalist, editorial, luxury minimal, etc.) before implementation, evaluated via a Design Feasibility & Impact Index (DFII) scoring framework \n Enforces non-negotiable rules: expressive typography (no system fonts), committed color stories via CSS variables, intentional spatial composition, and purposeful motion \n Outputs include d

Audience-centered presentation design framework covering planning, visual strategy, cognitive load, and evaluation. \n \n Provides assertion-evidence structure to replace bullet points with clear claims supported by visual evidence, reducing cognitive overload \n Includes four evaluation phases: audience and content planning, visual strategy, cognitive load management, and structure patterns with scoring rubrics \n Covers five common anti-patterns (data dumps, script reading, template traps, ani

Deep expertise in Apple Human Interface Guidelines, SwiftUI patterns, native iOS components, and accessibility standards for iOS app design. \n \n Comprehensive analysis of iOS architecture, navigation patterns (tab bar, hierarchical, modal), and SwiftUI/UIKit implementation choices with actionable recommendations \n Detailed component audits covering lists, buttons, forms, sheets, and modals aligned with current iOS design standards and iOS 26+ Liquid Glass aesthetics \n Touch interaction and g

$21

Production-grade UI design with design tokens, layout rules, motion guidance, and accessibility validation. \n \n Provides structured design token system covering colors, typography, spacing, shadows, and breakpoints for consistent scaling across projects \n Includes layout specification templates for different page types (landing, dashboard, form, blog, e-commerce) with responsive breakpoint rules \n Offers motion guidelines with easing curves, transition durations, and interaction patterns for

Professional UI/UX design creation in Penpot with MCP tools, design systems, and accessibility standards. \n \n Four MCP tools enable design creation, modification, export, and API access within Penpot's plugin context \n Includes discovery workflow to identify existing design systems, components, and tokens before building new designs \n Covers responsive layouts for mobile (375×812), desktop (1440×900), and platform-specific guidelines (iOS, Android, Material Design) \n Provides default design

A practical framework for managing the fundamental challenge of software engineering: complexity. Apply these principles when designing modules, reviewing APIs, refactoring code, or advising on architecture decisions. The central thesis is that complexity is the root cause of most software problems, and managing it requires deliberate, strategic thinking at every level of design.