authoring-tests

Write and run automated tests for Elements components including unit, accessibility, visual, SSR, and lighthouse tests. Use this skill whenever the user wants to write, create, update, or debug test files (.test.ts, .test.axe.ts, .test.visual.ts, .test.ssr.ts, .test.lighthouse.ts). Also trigger when the user asks about createFixture, removeFixture, elementIsStable, emulateClick, untilEvent, runAxe, visual baselines, theme testing, or test structure patterns like describe block naming.

跳到安装查看文件

仓库: NVIDIA/elements
最近来源活动: 2026年8月12日 00:30
检测到的 SKILL.md 语言: 英语
星标: 102
Forks: 19

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 AI 助手安装

复制这段 Prompt，发给你正在使用的 AI 助手。

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/NVIDIA/elements/tree/main/.agents/skills/authoring-tests.

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/NVIDIA/elements --skill authoring-tests

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

name: authoring-tests
description: Write and run automated tests for Elements components including unit, accessibility, visual, SSR, and lighthouse tests. Use this skill whenever the user wants to write, create, update, or debug test files (.test.ts, .test.axe.ts, .test.visual.ts, .test.ssr.ts, .test.lighthouse.ts). Also trigger when the user asks about createFixture, removeFixture, elementIsStable, emulateClick, untilEvent, runAxe, visual baselines, theme testing, or test structure patterns like describe block naming.

# Authoring Tests You MUST review @projects/site/src/docs/internal/guidelines/testing.md before making any testing changes. ## When to Use This Skill - Creating new test files for components (`.test.ts`, `.test.axe.ts`, `.test.visual.ts`, `.test.ssr.ts`, `.test.lighthouse.ts`) - Debugging test failures or updating existing tests - Understanding testing utilities from `@internals/testing` - Setting up test configurations or HTML templates - Writing tests that follow project patterns ## Test Type Guidelines Read the specific guideline based on the test type you're working with: - **Unit Tests (`.test.ts`)**: Read [testing-unit.md](/projects/site/src/docs/internal/guidelines/testing-unit.md) - covers `createFixture`, `elementIsStable`, event testing - **Accessibility Tests (`.test.axe.ts`)**: Read [testing-accessibility.md](/projects/site/src/docs/internal/guidelines/testing-accessibility.md) - covers axe-core usage, WCAG compliance - **Visual Tests (`.test.visual.ts`)**: Read [testing-visual.md](/projects/site/src/docs/internal/guidelines/testing-visual.md) - covers Playwright screenshots, theme testing - **SSR Tests (`.test.ssr.ts`)**: Read [testing-ssr.md](/projects/site/src/docs/internal/guidelines/testing-ssr.md) - covers server-side rendering compatibility - **Lighthouse Tests (`.test.lighthouse.ts`)**: Read [testing-lighthouse.md](/projects/site/src/docs/internal/guidelines/testing-lighthouse.md) - covers performance, accessibility scores ## Key Principles 1. **Test Isolation**: Each test should be independent with proper setup/teardown using `createFixture` and `removeFixture` 2. **Wait for Stability**: Always use `elementIsStable()` before making assertions on Lit components 3. **Comprehensive Coverage**: All new components require unit, accessibility, and visual tests at minimum 4. **Real User Events**: Use `emulateClick` and `untilEvent` for realistic event testing 5. **Theme Testing**: Visual tests should cover both light and dark themes ## References - [Testing Overview](/projects/site/src/docs/internal/guidelines/testing.md) - [Unit Testing](/projects/site/src/docs/internal/guidelines/testing-unit.md) - [Accessibility Testing](/projects/site/src/docs/internal/guidelines/testing-accessibility.md) - [Lighthouse Testing](/projects/site/src/docs/internal/guidelines/testing-lighthouse.md) - [SSR Testing](/projects/site/src/docs/internal/guidelines/testing-ssr.md) - [Visual Testing](/projects/site/src/docs/internal/guidelines/testing-visual.md) - [Vite Internals](/projects/internals/vite/README.md)

在 GitHub 查看

返回搜索返回安装

elements

Use this skill by default for any UI-related work or with NVIDIA Elements (nve-*), including creating, editing, reviewing, or debugging HTML, CSS, layout, theming, components, applications, prototypes, Claude Artifacts, Codex Sites pages, and standalone UI artifacts.

2026-10-15

audit-consolidation

Audit an Elements project or directory for one concept implemented or owned in more than one place, including duplicate or parallel implementations that should share one internal module, related code scattered across feature directories, and older paths made redundant by newer ones. Use when the user asks for a consolidation or architecture cleanup audit, asks whether two components or utilities do the same thing, says a change keeps needing coordinated edits in more than one place, wants shared implementation candidates, or wants a plan to reduce maintenance complexity. Do not use for reviewing a diff or staged changes (use audit-code) or for removing copy-pasted text only.

2026-10-06

audit-simplification

Audit an Elements project, directory, or component for mechanisms that may not need to exist, including redundant state, attribute reflection, forwarding indirection, lifecycle plumbing, per-instance allocations, and custom synchronization that duplicates browser or Lit behavior. Use when the user says code feels over-engineered or heavier than it should be, asks whether a controller, field, service, or reflected attribute is necessary, or wants to reduce runtime overhead, memory, or boilerplate. Do not use for reviewing a diff or staged changes (use audit-code) or for deciding where duplicate code should live (use audit-consolidation).

2026-10-06

查看这个仓库的全部 Skills

authoring-tests

来源信息

安装方式

用 AI 助手安装

检查来源文件

同仓库更多 Skills

用 AI 助手安装

同仓库更多 Skills