Run any Skill in Manus with one click

typescript

Stars25

Forks6

UpdatedMay 8, 2026 at 20:48

Best practices for TypeScript code including type safety, discriminated unions, type guards, and exhaustive checking. Use this skill whenever the user asks about TypeScript patterns, type safety, type assertions (as any, as unknown), non-null assertions, discriminated unions, exhaustive switch/never patterns, type guards, boolean trap parameters, race conditions in async code, memory leaks from closures, or sequential vs parallel async operations. Also trigger when reviewing TypeScript code for unsafe patterns or refactoring types.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

NVIDIA

NVIDIA/elements

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name

typescript

description

TypeScript

You MUST review @projects/site/src/docs/internal/guidelines/typescript.md before making any TypeScript changes.

When to Use This Skill

Writing or modifying component classes, utilities, or type definitions
Adding or updating TypeScript interfaces, types, or enums
Reviewing code for type safety issues
Implementing type guards or discriminated unions
Working with union types that require exhaustive checking

References

TypeScript Guidelines

More from this repository

same repository

availability-report

NVIDIA/elements

Generate a production availability report for NVIDIA Elements packages and documentation.

2026-07-0925

component-creation

NVIDIA/elements

Guide for creating new Elements components with all required files, base classes, metadata patterns, and test boilerplate. Use this skill whenever the user wants to create, scaffold, or set up a new component from scratch, needs to understand the required 10-file structure, asks about base classes and mixins (LitElement vs ButtonFormControlMixin), define.ts vs index.ts patterns, static metadata, component registration, or sub-component parent relationships. Also trigger when the user mentions creating test boilerplate for all 5 test types.

2026-06-0325

accessibility

NVIDIA/elements

Unified accessibility auditing workflow across static analysis, runtime testing, ARIA patterns, keyboard navigation, and color contrast. Use this skill whenever the user mentions accessibility, a11y, WCAG, ARIA roles, axe tests, screen readers, focus management, keyboard navigation, color contrast, or wants to audit, verify, or fix accessibility on any component. Also use when writing or debugging .test.axe.ts files, checking tabindex management, or reviewing focus trapping behavior.

2026-05-0825

api-design

NVIDIA/elements

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.

2026-05-0825

build-system

NVIDIA/elements

Wireit orchestration, build optimization, caching strategies, and build troubleshooting for the Elements monorepo. Use this skill whenever the user asks about Wireit configuration, build tasks, build dependencies, cache invalidation, build performance, adding new build tasks to package.json, cross-package dependency patterns, sideEffects declarations, CI pipeline configuration, or diagnosing slow or failing builds. Also trigger when the user mentions wireit, vite build issues, pnpm run ci, or build output problems.

2026-05-0825

code-review

NVIDIA/elements

Comprehensive code review process for Elements monorepo changes. Provides structured feedback on type safety, testing, documentation, and adherence to project guidelines. Use this skill whenever the user asks you to review code, check staged changes, look at a diff, give feedback before committing, review a PR or merge request, or evaluate code quality. Trigger on phrases like "review my changes," "check my code," "give me feedback," "look at my staged files," "review this PR," or "before I commit."

2026-05-0825

name

typescript

description

TypeScript

You MUST review @projects/site/src/docs/internal/guidelines/typescript.md before making any TypeScript changes.

When to Use This Skill

Writing or modifying component classes, utilities, or type definitions
Adding or updating TypeScript interfaces, types, or enums
Reviewing code for type safety issues
Implementing type guards or discriminated unions
Working with union types that require exhaustive checking

References

TypeScript Guidelines