Art & Design

v0 by Vercel expert guidance. Use when discussing AI code generation, generating UI components from prompts, v0 CLI usage, v0 SDK/API integration, or integrating v0 into development workflows with GitHub and Vercel deployment.

Creates and improves Astro, Tailwind CSS, and Wagtail websites with nontechnical users. Use for Website Builder setup, preparing or refining a website, and reviewing recorded feedback about the Website Builder workflow.

Use for new frontend applications, dashboards, games, creative websites, hero sections, and visually driven UI from scratch, or when the user explicitly asks for a redesign/restyle/modernization. Builds from clean, airy, high-taste, readable image-generated concept design with section-specific references, faithful implementation, and browser testing.

Makes websites, landing pages and UI look designed by a person with taste instead of generic "AI slop". Bans the tells every AI-built site shares (purple/blue gradients, gradient text, neon accents, glow shadows, glassmorphism, Inter/Poppins-by-default, sparkle emojis, the hero → logo cloud → 3 feature cards → pricing template, "Unlock the power of" copy) and replaces them with a short design process that produces deliberate, specific choices. Use this skill whenever you build, redesign, restyle or review any website, landing page, portfolio, web app UI, HTML/CSS page, React/Vue/Svelte component, Tailwind layout, email template or artifact page, even if the user never says "design" or "AI slop". Also use it when the user says a page "looks AI-generated", "looks like every other site", "too generic", "make it look human/handmade/real", or "de-slop this", or asks which fonts suit a business or niche.

Use when testing, debugging, or making targeted improvements to rendered frontend apps through the Build Web Apps or web dev plugin: local dev servers, UI regressions, interaction bugs, console errors, responsive layout, and visual QA. Check whether the Browser plugin is available and use it first when it is; otherwise use regular Playwright with the recorded reason.

Design UI surfaces for browser games. Use when the user asks for HUDs, menus, overlays, responsive layouts, or visual direction that must protect the playfield.

Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.

Guide for building, configuring, and deploying microfrontends on Vercel. Use this skill when the user mentions microfrontends, multi-zones, splitting an app across teams, independent deployments, cross-app routing, incremental migration, composing multiple frontends under one domain, microfrontends.json, @vercel/microfrontends, the microfrontends local proxy, or path-based routing between Vercel projects. Also use when the user asks about shared layouts across projects, navigation between microfrontends, fallback environments, asset prefixes, or feature flag controlled routing.

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

Extract a website's observed design system from a URL and deliver a validated ZIP containing design.md, token.json, variables.css, and theme.css. Use for website style references, design-token extraction, or RICOUI-compatible design packages; not for redesigning a website.

Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling

The superhero of webdesign skills — builds new websites and audits existing ones against one bar: does it have a real reason to exist, does it solve a business problem, is it beautiful, usable, secure, and GDPR-compliant. For “build me a website” requests, runs a content-approval interview before any implementation. For "check/audit my site" requests, runs the same skill in audit mode against the identical checklist. Use whenever Sinaida asks to build, design, redesign, or review a website, landing page, or web app.

Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. Use when building or reviewing React or Next.js components, state, or render performance.

Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.

Implement or refine the portfolio's landing page Prism-style project carousel and Projects page album-rail graphic gallery. Use when the user refers to either carousel, its scroll transitions, or asks to reuse the visual/interaction pattern in this project.

Release develop to main (the live site): release notes, merge, tag, push, and check the Netlify production deploy. Run only when Karolina asks for a release.

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

Commit a finished change on develop the way this repo expects - yarn verify, semver bump, CHANGELOG entry, own files staged by name, version in the subject, push. Use whenever a change is ready to commit.

Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

Personal developer blog and portfolio design with a narrow reading column, serif post text, warm neutrals and one green accent, light and dark mode with a toggle, writing grouped by year, reading time, post outline, author box, previous and next posts, project tiles with tech pills and an experience timeline.

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).

Next.js 16+ and Turbopack guidance — incremental Rust bundling, file-system caching, faster dev startup and HMR, Turbopack vs webpack tradeoffs, and the middleware.ts to proxy.ts filename change. Use when developing or debugging Next.js 16+ apps, diagnosing slow dev startup or hot reload, choosing between bundlers, or reviewing middleware/proxy file naming.

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.

>- Build and improve user interfaces with coherent visual design, responsive layout, accessible interaction, and reliable state. Use for pages, components, forms, frontend behavior, and UI polish. Follow the project's framework and design system and verify rendered behavior rather than relying on source or screenshots alone.