authoring-examples

Guidelines for writing example template files (*.examples.ts) including naming conventions, @summary JSDoc comments, and stateless HTML patterns. Use this skill whenever the user creates, modifies, or reviews *.examples.ts files, asks about example naming rules (PascalCase, 3-word max, no component prefix), needs to write or improve @summary JSDoc comments, encounters example-naming ESLint errors, or wants to add stateless or interactive examples to a component's example file.

Ir para a instalação Revisar arquivos

Repositório: NVIDIA/elements
Última atividade na origem: 12 de agosto de 2026 às 00:30
Idioma detectado do SKILL.md: inglês
Estrelas: 102
Forks: 19

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com um assistente de IA

Copie este prompt para o assistente de IA que você usa.

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

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

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

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

name: authoring-examples
description: Guidelines for writing example template files (*.examples.ts) including naming conventions, @summary JSDoc comments, and stateless HTML patterns. Use this skill whenever the user creates, modifies, or reviews *.examples.ts files, asks about example naming rules (PascalCase, 3-word max, no component prefix), needs to write or improve @summary JSDoc comments, encounters example-naming ESLint errors, or wants to add stateless or interactive examples to a component's example file.

# Authoring Examples (`*.examples.ts`) You MUST review @projects/site/src/docs/internal/guidelines/examples.md before making any changes to example files. ## When to Use This Skill - Creating new `*.examples.ts` files for components - Adding or updating example templates within existing example files - Reviewing example naming conventions and structure - Writing or updating `@summary` JSDoc comments for examples ## Key Principles 1. **PascalCase Naming**: Use PascalCase for example names (for example, `Default`, `StatusFlat`, `FormSubmit`) 2. **Concise Names**: Keep example names to 1-3 words maximum, describing **what** the example shows 3. **Required @summary**: Every example must include a `@summary` JSDoc comment explaining what, why, when, and how 4. **Stateless Templates**: Examples should be stateless HTML templates demonstrating UI patterns ## Naming Patterns - Single words: `Default`, `Status`, `Size`, `Color`, `Disabled` - Compound names: `StatusFlat`, `StatusIcon`, `FormSubmit`, `VerticalTabs` - Special prefixes: `Legacy*`, `Invalid*`, `Valid*` ## References - [Examples Guidelines](/projects/site/src/docs/internal/guidelines/examples.md) - [Documentation Guidelines](/projects/site/src/docs/internal/guidelines/documentation.md)

Ver no GitHub

Voltar à pesquisa Voltar à instalação

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

Ver todas deste repositório

authoring-examples

Informações da origem

Opções de instalação

Instalar com um assistente de IA

Revise os arquivos de origem

Mais deste repositório

Instalar com um assistente de IA

Mais deste repositório