guidance-api-design

Component API design patterns following Elements conventions for properties, attributes, CSS custom properties, slots, and events. Use this skill whenever the user is designing or deciding on a component API, choosing between properties vs attributes vs slots, naming CSS custom properties, designing events, avoiding impossible states, deciding whether to reflect to an attribute, using CSS Parts, implementing the DataElement interface, or applying the internal-host pattern. Also trigger when the user asks about shorthand vs granular CSS properties or event naming conventions.

Jump to install Review files

Repository: NVIDIA/elements
Last source activity: August 12, 2026 at 00:30
Detected SKILL.md language: English
Stars: 102
Forks: 19

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

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

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/NVIDIA/elements --skill guidance-api-design

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

name: guidance-api-design
description: Component API design patterns following Elements conventions for properties, attributes, CSS custom properties, slots, and events. Use this skill whenever the user is designing or deciding on a component API, choosing between properties vs attributes vs slots, naming CSS custom properties, designing events, avoiding impossible states, deciding whether to reflect to an attribute, using CSS Parts, implementing the DataElement interface, or applying the internal-host pattern. Also trigger when the user asks about shorthand vs granular CSS properties or event naming conventions.

# Guidance API Design You MUST review the relevant API design guidelines before designing or modifying component APIs. ## When to Use This Skill - Designing properties and attributes for new components - Creating CSS custom properties for theming - Avoiding impossible states in component APIs - Choosing between properties, attributes, and slots - Designing custom events - Planning component composition patterns - Setting up package exports and dependencies ## Stateless Components When creating new components or features that may contain user state review the [Stateless Components Guidelines](/projects/site/src/docs/api-design/stateless.md). ## Properties vs Attributes When working with JavaScript properties and HTML attributes review the [Properties & Attributes Guidelines](/projects/site/src/docs/api-design/properties-attributes.md). ## Styles & CSS Custom Properties When working with CSS, CSS Custom Properties or Design Tokens review the [Styles & CSS Custom Properties Guidelines](/projects/site/src/docs/api-design/styles.md). ## Component Composition When creating a new API or determining API design of parent child relationships between components review the [Component Composition Guidelines](/projects/site/src/docs/api-design/composition.md). ## Slots When working with user provided content or container-like components review the [Slots Guidelines](/projects/site/src/docs/api-design/slots.md). ## Custom Events When creating new events or listening to existing event review the [Custom Events Guidelines](/projects/site/src/docs/api-design/custom-events.md). ## Component Registration When creating new components or using components as dependencies review the [Component Registration Guidelines](/projects/site/src/docs/api-design/registration.md). ## Packaging & Exports When creating a new component or package review the [Packaging & Exports Guidelines](/projects/site/src/docs/api-design/packaging.md).

View on GitHub

Back to search Back to installation

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

View all from this repository

guidance-api-design

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository