Results for “vite”

Migrate an existing web React app to a native iOS/Android app with Expo, screen by screen, using a strangler fig pattern.

Extract self-contained static HTML from a built web application or React components by inlining CSS and images.

Creates elaborate, multi-component HTML artifacts using React, Tailwind CSS, and shadcn/ui, then bundles them into a single self-contained HTML file.

Write Jest or Vitest unit tests with React Testing Library and Playwright E2E tests for Next.js projects. Use when testing components with RTL, mocking APIs with MSW, or creating Playwright user flow tests.

Deploy static websites to IPFS with a single command using PinMe CLI, supporting Vite, React, Vue, Next.js, Angular, and static sites. Returns a preview URL after upload.

Configure debugging, bundle analysis, and ecosystem tools for React applications. Use when setting up Vite/webpack build tooling, analyzing bundle size, debugging re-renders with React DevTools, or configuring ESLint and StrictMode for React projects.

Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations for dashboards, admin panels, or data-rich interfaces.

Scaffold, install, and compose shadcn-vue components built on Reka UI v2, including Vue variants, form patterns with vee-validate/Zod, and adaptation of existing components.

Builds elaborate, multi-component claude.ai HTML artifacts using React, Tailwind CSS, and shadcn/ui, with scripts to initialize and bundle projects into a single HTML file.

Create and present web-based slide decks using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Ideal for technical presentations, conference talks, code walkthroughs, teaching materials, or developer decks.

Builds elaborate, multi-component HTML artifacts for claude.ai using React, Tailwind CSS, and shadcn/ui, with scripts to initialize and bundle projects into single self-contained HTML files.

Guides building sites with SvelteKit 2, Svelte 5, and Tailwind CSS v4, covering setup, runes, forms, styling, deployment, and migration through curated documentation and a structured search workflow.

Captures a self-contained static HTML file from a running web app or React components by inlining CSS and images, with strategies for both simple snapshots and interactive captures.

Builds elaborate, multi-component claude.ai HTML artifacts using React, Tailwind CSS, and shadcn/ui, with scripts to initialize a project and bundle it into a single HTML file.

React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.

Guide for testing code changes in AEM Edge Delivery projects including blocks, scripts, and styles. Use this skill after making code changes and before opening a pull request to validate functionality. Covers unit testing, browser testing with Playwright, and linting.

Migrate an existing web React app to a native iOS/Android app with Expo, screen by screen, using a strangler-fig pattern that ships the web UI in a DOM-component shell on day one and nativizes screens by value.

You are an expert in SWC, the Rust-based JavaScript/TypeScript compiler. You help developers replace Babel and Terser with SWC for 20-70x faster compilation, minification, and bundling — used by Next.js, Vite, Parcel, and Deno as their default compiler, handling TypeScript stripping, JSX transformation, polyfill injection, and code minification at native speed.

Integrate, customize, and contribute to react-bits (github.com/DavidHDev/react-bits) — the largest and most creative library of animated React components. It covers Vite, Tailwind CSS v4, Three.js/Fiber, GSAP, and Framer Motion integrations. Use when the user asks about react-bits, animated React components, jsrepo registry, or contributing new animated components to the react-bits repository.

Expert knowledge for SvelteKit full-stack web applications with SSR, form actions, and Svelte 5 runesUse when "sveltekit, svelte kit, svelte 5, svelte5, runes, $state, $derived, $effect, $props, $bindable, form actions, +page.server, +page.ts, +layout, +server, load function, svelte adapter, adapter-node, adapter-vercel, hooks.server, sveltekit, svelte, svelte5, ssr, form-actions, load-functions, runes, server-routes, adapters, vite" mentioned.

Cypress E2E testing framework. Covers commands, assertions, and component testing. Use for end-to-end testing. USE WHEN: user mentions "cypress", "e2e test", "cy.get", "cy.visit", asks about "cypress intercept", "component testing", "cypress commands" DO NOT USE FOR: Unit tests - use `vitest` or `jest`; Multi-tab scenarios - Cypress doesn't support; Native mobile apps - use Appium; Performance testing - use dedicated tools

Native Gutenberg blocks without ACF — block.json, edit.js, save.js, register_block_type, @wordpress/scripts, block attributes, InnerBlocks, useBlockProps, ServerSideRender, dynamic blocks PHP render_callback, block supports, block.json apiVersion 3, block variations, block styles, block transforms, React in block editor, wp_register_block_script_handle, Vite and WordPress blocks, native block vs ACF Composer block decision, block.json editorScript viewScript, @wordpress/block-editor

WordPress performance optimization: performance, slow query, N+1 query, Query Monitor, autoload audit, autoload options, object cache, Redis, wp_cache, transient, cache invalidation, Core Web Vitals, LCP, CLS, INP, FID, profiling, Xdebug, microtime, pre_get_posts, database query optimization, TTFB, page load, Vite bundle, lazy loading, critical CSS — benchmark before/after, never optimize blind. Invoke for: slow page load, N+1 query problem, caching strategy, transient API, dequeue unused scripts, performance profiling, Core Web Vitals improvement.

[devup-ui] Routing-first front door for Devup UI — a zero-runtime CSS-in-JS library whose Rust + WebAssembly preprocessor extracts every style at build time, so no styling JavaScript ships at runtime. Use to adopt/integrate Devup UI, wire the build-time plugin into Next.js/Vite/Rsbuild/Webpack/Bun, write styles with Box/css props or the styled-components-compatible styled() API, set up type-safe theming with devup.json, or migrate off styled-components/Emotion/Tailwind/Panda/vanilla-extract to zero runtime.

Maestro — declarative E2E mobile UI testing framework by mobile.dev. YAML-based flow files, single tool for Android + iOS (and Compose Multiplatform / Flutter / React Native). Built-in cloud runner, recording mode, JS scripting for complex assertions, screen state diffing, no flakiness from explicit waits. USE WHEN: user mentions "Maestro", "maestro test", "mobile E2E", "cross-platform UI test", "maestro studio", "mobile.dev cloud", ".maestro" folder, "launchApp" YAML DO NOT USE FOR: web E2E - use `testing/playwright` DO NOT USE FOR: unit tests - use `testing/kotest`, `testing/vitest`, etc. DO NOT USE FOR: instrumented Android tests - use Espresso/Compose Test DO NOT USE FOR: snapshot tests - use `testing/compose-snapshot`

Work with Lapian Notes / 拉片笔记 (github.com/bkingfilm/lapian-notes) — a local- first React/Vite tool that turns a film into an editable shot-by-shot study notebook: local frame extraction, AI-assisted structure analysis (bring your own AI, no API key required), story-line swimlane timeline, structure tree, and audience-emotion curve. Use when the user asks about Lapian Notes, "拉片笔记", "拉片" (shot-by-shot film analysis) tooling, cloning/running this repo (npm run dev, run.bat/run.command), the AI-analysis-package (ZIP) round-trip workflow, or contributing a PR to lapian-notes. Not for generic video editing (use `opencut` for that) or generic film-analysis theory unrelated to this codebase.