Art & Design

Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.

Read-only technical and conversion audit of a live website, made as the before-rebuild snapshot of a B2B site. Crawls up to N same-origin pages (default 10) in headless Chrome and checks mobile layout at 360/390/768 px, bugs (console errors, failed requests, broken links and images, forms without submitting them), accessibility (axe-core, WCAG 2.1 A/AA), performance (Lighthouse or browser timing), the lead path (CTA in the first screen on desktop and phone, contact within 2 clicks, contact info, trust markers) and SEO basics. Writes one markdown report with scores per area, findings P0-P3 (what, where, why it costs leads, fix) and a snapshot to compare after the rebuild, plus raw JSON. Use when the user says "audit this site", "what's wrong with this website", "website audit", "check this URL", "аудит сайту", "технічний аудит сайту", "перевір сайт", "що не так із сайтом". NOT a copywriting audit (use website-copy-reframe), NOT a design system (use design-system-generator).

Expert integration of Supabase Auth with Next.js App Router Use when: supabase auth next, authentication next.js, login supabase, auth middleware, protected route.

Next.js App Router principles. Server Components, data fetching, routing patterns.

Comprehensive frontend development skill for building modern, performant web applications using ReactJS, NextJS, TypeScript, Tailwind CSS. Includes component scaffolding, performance optimization, bundle analysis, and UI best practices. Use when developing frontend features, optimizing performance, implementing UI/UX designs, managing state, or reviewing frontend code.

Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features, fetching data, styling, routing, or working with frontend code.

Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.

Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.

Design and build a marketing site, landing page, product homepage, or an app's UI and login/signup pages end to end — reference screenshots and image-gen drafts the user approves first, then a unified page system, an art direction and motion plan derived from the brief, component and animation libraries chosen to fit the project, i18n, and accessibility/e2e verification. Use when the user asks to design, redesign, restyle or polish an official website, landing page, homepage or its subpages, an app's screens (workbench, chat/agent UI, dashboards) or its auth pages, asks for UI reference sites, or says the current design looks bad, fragmented or lacks motion.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

Design or fix client, URL, and server state ownership, including request races, optimistic updates, and session changes.

Build modern web applications with React, Vue, Angular, or Svelte, focusing on performance and accessibility. Use when you need component library development, TypeScript UI implementation, responsive layouts with CSS Grid and Flexbox, Core Web Vitals optimization, service worker offline support, code splitting, ARIA accessibility, Storybook integration, or frontend API client architecture.

Generate a premium mockup website for a prospect using the buildinamsterdam.com template style. Use when user asks to design a website, create a mockup, or build a prospect website.

Expert guidance for integrating and building applications with shadcn/ui components, including component discovery, installation, customization, and best practices.

仅当用户明确要求在已有前端项目中生成、制作、构建或完善“原型”（例如高保真原型、可点击演示或评审 Demo）时使用此 Skill。默认基于现有源码复用组件、设计变量和技术栈，创建与正式业务入口隔离的原型页面或路由，并使用页面级模拟数据完成可点击演示；除非用户明确要求，否则不直接改动正在使用的业务页面、不接入后端或生产数据链路。

Apply whenever UI is built or changed — components, pages, forms, dialogs, menus, tabs, tables, icons, images, animations, toasts, route changes — and for accessibility audits ("a11y", "Barrierefreiheit", "WCAG", "Screenreader", "Tastatur-Navigation", "accessibility review"). Accessibility is developed together with the UI, never added later. Target WCAG 2.2 AA (also the bar for BFSG / EN 301 549). Covers semantics and ARIA, keyboard and focus, accessible names, forms and errors, live regions, contrast and color, target sizes, motion, zoom/reflow, and testing with Testing Library, Storybook addon-a11y, Playwright + axe and manual keyboard/screen-reader checks. Framework-agnostic rules with React examples.

Apply for any work on a React/TypeScript frontend — components, hooks, state, routing, data fetching, forms, styling, accessibility, i18n, tests, stories, performance and frontend security; also when setting up a new React project, containerizing a frontend or reviewing React code. Covers Vite SPAs and React Router framework mode (loaders, actions, SSR/hydration), TanStack Query for server state, TanStack Router or React Router, Zustand for client state, React Hook Form or TanStack Form with Zod, Feature-Sliced Design structure, Biome and strict TypeScript, Vitest + Testing Library, Playwright, Storybook. Holds the rules that always apply — derived state instead of effects, server data only in TanStack Query, accessibility built in, tests and stories with every feature, no tokens in browser storage — and points to references per topic.

Use when calculating or interpreting birth charts and full-spectrum astrological profiles — Western tropical natal charts, Vedic/sidereal (Lahiri) charts, Chinese BaZi / Four Pillars, and Human Design (gates, lines, type, authority, incarnation cross). Triggers on "natal chart", "birth chart", "horoscope", "โหราศาสตร์", "ดวง", "ปาจื่อ", "โป๊ยหยี่", "สี่เสา", "BaZi", "Four Pillars", "Human Design", "Vedic", "Jyotish", "sidereal", "nakshatra", or requests for planetary positions, houses, or gate activations from a birth date/time/location.

Playbook for building a new multi-language marketing website from scratch to the standard of a real production site - folder layout and build pipeline, design tokens and typography, real-screen phone mockups, i18n, SEO, GEO (AI-search visibility), performance, consent/analytics, legal pages, QA across devices/widths/modes/in-app browsers, backups, and a reviewed deploy (Vercel or similar). Use when building a new site or landing page, or when auditing one against this standard.

The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.

Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke to configure route handlers, implement middleware, set up API routes, add streaming SSR, write generateMetadata for SEO, scaffold loading.tsx/error.tsx boundaries, or deploy to Vercel. Triggers on: Next.js, Next.js 14, App Router, RSC, use server, Server Components, Server Actions, React Server Components, generateMetadata, loading.tsx, Next.js deployment, Vercel, Next.js performance.

Build immersive 3D websites and landing pages where users scroll to walk or fly through a WebGL-rendered 3D scene. Use this skill whenever the user asks for a 3D website, 3D landing page, 3D frontend, scroll-driven 3D experience, room walkthrough, fly-through, parallax 3D scene, immersive web experience, 3D portfolio, 3D storytelling page, or any web page where scrolling controls movement through a three-dimensional space. Also trigger when the user mentions 'Three.js website', 'WebGL scroll', '3D scroll animation', 'camera path on scroll', '3D frontend', 'scroll to explore 3D', 'walk through 3D', or wants to present content within a 3D world navigated by scrolling. Even if the user just says 'make it 3D' or 'make an immersive page' or '3D landing page', use this skill.

The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.

Use when adding, editing, reordering, or reviewing JavaScript modules or HTML structure in one of Pryne's vanilla-JS demo builds (files like design-demos/*.html and js/roll-*.js, or any window.<Namespace> IIFE-module site), when deciding where new interactive code should live, or when a change might touch script order, reduced-motion gating, progressive enhancement, or CSS design tokens.