'vite' 검색 결과

Set up a Google Classroom course, invite students by email address, and list enrolled students. The workflow covers course details such as name, section, and room, helping teachers handle the initial setup and enrollment checks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a course for a new class
• Set the course name, section, and room
• Invite students by email address

Write integration tests for core error processors by simulating API failures with a mock model. Check retry attempts, changes to conversation messages, and streamed responses, with guidance on test setup and diagnosing empty output.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check retries and message changes after API errors
• Diagnose empty output in streaming tests
• Verify unrelated errors pass through unchanged

Build Handsontable demo pages for visual regression tests, which compare screenshots for appearance changes. It guides feature routes, URL-driven display states, sample data, and decisions about testing the same feature across framework wrappers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding a demo route for a new feature
• Creating multiple visual states through URL parameters
• Planning visual coverage across framework wrappers

Develop and debug LangBot's backend and web frontend. The skill guides environment setup, API additions, authentication, database migrations, and testing, including updates to matching MCP tools so agents can use changed API features.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up the LangBot backend and frontend for development
• Add an API endpoint and its matching MCP tool
• Update the database schema with Alembic

Tests a specific Convex feature with sample data and simulated users, without deployment. It checks expected results, rejects unauthorized callers, and verifies that queries return only data belonging to the current user.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Verifying a newly implemented Convex feature
• Checking that other users cannot modify owned data
• Testing rejection of unauthenticated requests

Build NEAR Protocol web apps or add wallet features to existing projects. Covers project setup, wallet sign-in and sign-out, transaction signing, and interfaces for reading or updating smart contracts, programs that run on the blockchain.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Start a new NEAR web app
• Add wallet connections to an existing React app
• Build an interface for a NEAR smart contract

Guides the refactoring of large JavaScript files into smaller CommonJS modules within gh-aw. It covers source placement, function exports, tests, and action builds so extracted code remains testable and is included in generated actions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Splitting a large JavaScript file by responsibility
• Extracting utilities shared across workflows
• Adding tests for extracted modules

Production-tested setup for Tailwind CSS v4 with shadcn/ui, Vite, and React. Use when: initializing React projects with Tailwind v4, setting up shadcn/ui, implementing dark mode, debugging CSS variable issues, fixing theme switching, migrating from Tailwind v3, or encountering color/theming problems. Covers: @theme inline pattern, CSS variable architecture, dark mode with ThemeProvider, component composition, vite.config setup, common v4 gotchas, and production-tested patterns. Keywords: Tailwind v4, shadcn/ui, @tailwindcss/vite, @theme inline, dark mode, CSS variables, hsl() wrapper, components.json, React theming, theme switching, colors not working, variables broken, theme not applying, @plugin directive, typography plugin, forms plugin, prose class, @tailwindcss/typography, @tailwindcss/forms

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scaffold a full-stack Cloudflare app from the vite-flare-starter template — React 19 + Hono + D1+Drizzle + better-auth + Tailwind v4+shadcn/ui + TanStack Query + R2 + Workers AI. Run setup.sh to clone, configure, and deploy. Use whenever the user wants a batteries-included Cloudflare full-stack app, vite-flare-starter scaffold, or a React + Cloudflare app with auth + database + Workers AI ready to go.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write, review, filter, mock, and debug Core unit tests with the repository's installed Vitest 5 configuration. Use for tests under Core's Vitest include paths, `vi.mock`/spies/timers, jsdom component tests, coverage output, focused reruns, or unit-test failures. Do not use for browser E2E flows or async Next.js Server Components.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Modern TypeScript/JavaScript testing with Vitest. Fast unit and integration tests, native ESM support, Vite-powered HMR, and comprehensive mocking. Use for testing TS/JS projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Migrate a test suite from one framework to another, incrementally and without losing coverage. Covers Selenium→Playwright, Cypress→Playwright, Jest→Vitest, Mocha→Vitest, and Protractor→Playwright, with parallel CI running, locator/assertion translation, and a coverage-parity track. Use when: "migrate tests," "switch framework," "Selenium to Playwright," "Jest to Vitest," "framework migration." Not for: bulk selector regeneration after a UI refactor on the SAME framework — use selector-drift-recovery. Not for: healing one flaky test at runtime — use test-reliability. Not for: modernizing patterns without changing framework — use ai-qa-review. Related: playwright-automation, cypress-automation, unit-testing, ci-cd-integration, test-reliability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

VitePress 1.x — Vue-powered static site generator for documentation sites, built on Vite

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when writing unit/integration tests for Vite projects - provides Vitest configuration, test APIs, mocking patterns, and coverage setup

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

UI stack, build, and test conventions for NV oOS React SPA addons (toolkit-shell, chat-spa, schedule-anything-spa, saas-controller) — three sanctioned build patterns plus the standalone Pro SPA Vite app (examples/nvoos-pro-spa-vite), dual-React guard, headless component rules, NDS tokens, Tailwind v4, @xyflow/react v12, vitest/jsdom gotchas, the full-JS-rebuild map, and the TS-shadows-JS webpack gotcha. Use when building or modifying SPA addon UI, writing SPA JS tests, upgrading SPA deps, or rebuilding JS for packaging.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detects Vitest test-isolation hazards: unrestored vi.spyOn/vi.mock without afterEach cleanup or restoreMocks config, un-awaited resolves/rejects assertions, and shared mutable module state across tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working with Vitess — vitess tablet health, VSchema management, resharding status, VReplication workflows, and cluster topology.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Convert approved Stitch exports into accessible React and Vite dashboards with DESIGN.md tokens, TanStack Query data boundaries, responsive layouts, and optional read-only Web3 integrations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when writing unit tests, mocking dependencies, testing pure functions, or measuring coverage with Vitest. Trigger words: ユニットテスト, 単体テスト, Vitest, モック, テストを書く, カバレッジ, describe, it, expect, vi.mock.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

새 테스트와 기존 테스트가 보호하는 동작과 결함을 점검합니다. 중복과 구현 의존성을 검토하고 삭제 근거를 기록하며, 필요한 검증을 남겨 테스트 전용 코드도 정리합니다.

• 새 테스트의 필요성을 확인합니다
• 중복되거나 구현에 의존하는 테스트를 점검합니다
• 테스트만을 위해 공개한 함수를 검토합니다