frontend▌

"Transform Figma designs into implementation-ready specifications with pixel-perfect accuracy"

Design intuitive, accessible, user-centered interfaces.

Apply these rules when writing or reviewing Next.js code.

Establish design token hierarchies, theming infrastructure, and component architecture for scalable design systems. \n \n Covers three-layer token organization: primitive tokens (raw values), semantic tokens (contextual meaning), and component tokens (specific usage) \n Includes theme switching patterns with CSS custom properties, React context providers, system preference detection, and persistent storage \n Provides component architecture patterns including compound components, polymorphic var

Establish consistency and best practices across backend microservices (blog-api, auth-service, notifications-service) using modern Node.js/Express/TypeScript patterns.

Create distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices. Expert UI/UX design skill that helps create unique, and thoughtfully designed interfaces. This skill emphasizes design decision collaboration, breaking away from generic patterns, and building interfaces that stand out.

This skill encodes design principles derived from comparing polished, production-quality SwiftUI apps against poorly-built ones. The patterns here represent what separates an app that feels "right" from one where the margins, spacing, and text sizes just look "off."

Build responsive applications using reactive streams and observables for handling asynchronous data flows.

CLI tools for Svelte 5 documentation lookup and code analysis with built-in autofixer. \n \n Three core commands: list-sections to browse available docs, get-documentation to fetch full documentation for specific topics, and svelte-autofixer to analyze code and suggest fixes \n Autofixer supports Svelte 4 and 5 targeting via --svelte-version flag and async mode via --async option \n Accepts both inline code (with escaped $ characters) and file paths for analysis \n Designed for use within the sv

You are a UI/UX architect. You do not write features or touch functionality. You make apps feel inevitable — like no other design was ever possible. If a user needs to think about how to use it, you've failed. If an element can be removed without losing meaning, it must be removed.