Art & Design

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.

Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Como escrever, rodar e depurar testes deste projeto — unitários (Vitest + Testing Library), E2E (Playwright, desktop e mobile) e verificação visual por screenshots. Use ao adicionar/alterar funcionalidades, ao corrigir bugs, antes de commits e sempre que precisar provar que uma mudança de UI funciona.

Como criar e manter a documentação deste projeto — README, guias em docs/, registros de decisão (ADRs), CHANGELOG e comentários no código. Use ao adicionar funcionalidades, tomar decisões de arquitetura/design, mudar comandos ou estrutura, preparar uma versão, ou quando o usuário pedir documentação.

Universal UI/UX design principles covering visual hierarchy, interaction laws, typography foundations, and WCAG accessibility requirements. Use when making design decisions not covered by a specific design system, validating principle compliance, or resolving conflicts between aesthetics and accessibility. Design-system-agnostic and applies to every surface.

Run a pre launch check on a website for security, search, accessibility, speed and after launch basics, and report what passes and what to fix. Use before launching or relaunching a site, after a big change, or when someone asks "is my site ready", "check my site" or "audit my portfolio".

Agency-grade web design for websites, landing pages, marketing sites, product launches, portfolios, e-commerce, and redesigns. Built from measured teardowns of 99 live sites shipped by top studios (basement.studio, Bakken & Bæck, Work & Co, AREA 17, Instrument, Exo Ape, Locomotive, Lusion, Immersive Garden, Unseen, Malvah, The First The Last, and others) plus in-house teams like Linear, Stripe, Vercel, and Apple. Use it whenever a frontend's visual quality matters, or when the user asks for something premium, agency-level, award-worthy, or "not AI-looking". It covers picking a direction, type, color, layout, imagery without photos, motion, copy, and a scripted self-audit.

Bauhaus style in motion - primary colours and black on off-white, circle/square/triangle geometry (Kandinsky's yellow triangle, red square, blue circle), asymmetric diagonal compositions, bars and rules, lowercase geometric sans (Bayer's Universal, Futura), red-and-black typography, photomontage, Albers colour squares, Schlemmer's geometric figures and modern Bauhaus tile patterns - with motion rules (shapes as actors, compass-and-ruler construction, 90-degree rotations, tile cascades, mechanical rhythm, colour interaction shifts, visual music). Includes After Effects, CSS/GSAP and Higgsfield recipes. Use when the user asks for Bauhaus, Bauhaus style, geometric primary-colour design, Kandinsky shapes, Triadic Ballet, Bayer/Universal type, modernist geometric animation, or Bauhaus tile patterns.

Use when the user asks for landing page, homepage CTA, inquiry form, popup, page audit, form redesign, 着陆页, 落地页, 询盘表单, 弹窗, 页面审计, or 表单改版. Audit live homepage, product, and inquiry pages against competitor CTAs, forms, and trust signals; write a sourced page audit, form redesign, popup plan, and experiment queue under deliverables/marketing/05-cro/. Read the ledger product_context first; invent no conversion rates, field counts, or competitor URLs. Never paste skill examples into the output. Not for post-submit reply scripts, launch/referral/retention playbooks, paid-media plans, technical site rebuilds, or phase navigation.

Implement modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first breakpoint strategies. Use when building adaptive interfaces, implementing fluid layouts, or creating component-level responsive behavior.

Rebuild existing web pages as working local code, matching their real content, assets, responsive layout, and interactions. Use for website cloning, replication, or reverse engineering, including Framer sites and animated pages.

Сборка и аудит лендингов, которые не выглядят собранными по шаблону. Используй, когда пользователь просит сделать лендинг, посадочную страницу, промо-сайт или одностраничник, а также когда просит проверить или доработать существующий лендинг ("выглядит как вайб-код", "слишком по-ИИшному", "как у всех").

>- Generate five distinct landing page versions for an app, each a complete deployable single-file HTML. Use when creating or refreshing an app's landing page. Each version follows a different design philosophy rather than five drafts of the same page.

>- Apple Human Interface Guidelines design foundations. Use this skill when the user asks about "HIG color", "Apple typography", "SF Symbols", "dark mode guidelines", "accessible design", "Apple design foundations", "app icon", "layout guidelines", "materials", "motion", "privacy", "right to left", "RTL", "inclusive design", branding, images, spatial layout, or writing style. Also use when the user says "my colors look wrong in dark mode", "what font should I use", "is my app accessible enough", "how do I support Dynamic Type", "what contrast ratio do I need", "how do I pick system colors", or "my icons don't match the system style". Cross-references: hig-platforms for platform-specific guidance, hig-patterns for interaction patterns, hig-components-layout for structural components, hig-components-content for display.

Explains how a website, a visual effect or an animation was built, from a live URL or a screenshot.

Builds UI from a Figma file or a design image so it matches the design, using your project's existing tokens and components.

Builds multiple variants of a component you're working on and helps you iterate and pick one.

Reviews a branch, pull request or uncommitted change for the interface problems it introduced or regressed, across accessibility, layout, writing, typography, color and UI.

Renders every state of a component you choose on a throwaway page, with mock data and a switcher, so you can work on each state.

>- Apple Human Interface Guidelines for layout and navigation components. Use this skill when the user asks about "sidebar", "split view", "tab bar", "tab view", "scroll view", "window design", "panel", "list view", "table view", "column view", "outline view", "navigation structure", "app layout", "boxes", "ornaments", or organizing content hierarchically in Apple apps. Also use when the user says "how should I organize my app", "what navigation pattern should I use", "my layout breaks on iPad", "how do I build a sidebar", "should I use tabs or a sidebar", or "my app doesn't adapt to different screen sizes". Cross-references: hig-foundations for layout/spacing principles, hig-platforms for platform-specific navigation, hig-patterns for multitasking and full-screen, hig-components-content for content display.