Loading...
Loading...
Found 460 Skills
Install and configure Trident UI component library for Vite and Next.js projects
[production-grade] Implements autonomous testing and self-healing workflow. After code generation, automatically runs tests (unit, integration, visual, E2E), detects bugs, attempts auto-fix, and continues development. Requires: Vitest, Playwright, Applitools, LLM access.
React component testing patterns including components, hooks, context, and forms. Covers Vitest Browser Mode with vitest-browser-react (preferred) and @testing-library/react. Use when testing React applications. For general UI testing patterns, see the front-end-testing skill.
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.
Testing guide using Vitest. Use when writing tests (.test.ts, .test.tsx), fixing failing tests, improving test coverage, or debugging test issues. Triggers on test creation, test debugging, mock setup, or test-related questions.
Scaffold a production-ready ArcGIS Maps SDK application with TypeScript, Vite, ESLint, Prettier, git hooks, and GitHub Actions CI/CD.
Write, run, and optimize project test cases (Vitest).
Build serverless applications on Cloudflare Workers. Covers runtime APIs, handlers (fetch, scheduled, queue, email), bindings (KV, R2, D1, Durable Objects, Queues, AI, Vectorize), wrangler.toml configuration, local development with Miniflare, static assets, compatibility flags, testing with Vitest. Keywords: Cloudflare Workers, serverless, edge computing, Wrangler, fetch handler, scheduled handler, bindings, KV, R2, D1, Durable Objects, Workers AI, Miniflare, wrangler.toml, compatibility_date.
Check and configure cache-busting strategies for Next.js and Vite projects
Generate or update tests for changed files in the current git branch, using statement coverage as the evaluation metric (target: 80%+). Use when: (1) the user asks to "write tests for my changes", "add tests for the current branch", or "improve coverage", (2) after implementing a feature to ensure adequate test coverage, (3) before a PR to verify changed code is tested. Supports Vitest and Cargo projects. Invoked with /test-generator or phrases like "generate tests", "test my changes", "cover the diff".
Read this skill to write, generate, or add test code. Trigger when: (1) user asks to write, add, create, or generate tests of any kind (unit tests, integration tests, API tests, E2E tests, Playwright tests, Vitest tests); (2) user has code with missing or zero tests and wants coverage; (3) user just implemented a new service, endpoint, feature, or module and needs tests for it; (4) user refactored code and wants to verify nothing broke with tests; (5) user wants to improve or expand existing test coverage. This skill produces complete, pyramid-shaped test suites — reads the code, selects only the necessary layers (unit/integration/API/E2E), and generates every file needed (schema tests, service tests, factories, helpers, cleanup utilities, spec files) following strict Vitest and Playwright patterns. Skip this skill when debugging failing tests, asking how to use testing APIs or tools, explaining testing concepts, configuring test runners, reviewing existing test code, or migrating between test frameworks.
Use when building browser-based presentation slide decks, creating training presentations, generating React+Vite slide decks with animations, or making professional slides. Triggers on slide deck, presentation, training slides, Vite slides, Framer Motion slides, animated presentations.