typescript-expert
TypeScript gotchas and decision criteria covering nullish coalescing pitfalls (|| vs ??), strict tsconfig settings (noUncheckedIndexedAccess, exactOptionalPropertyTypes), type guard patterns, discriminated unions, and as const vs enum. Use when writing TypeScript, configuring tsconfig, implementing type guards, or debugging null/undefined errors.
Best use case
typescript-expert is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
TypeScript gotchas and decision criteria covering nullish coalescing pitfalls (|| vs ??), strict tsconfig settings (noUncheckedIndexedAccess, exactOptionalPropertyTypes), type guard patterns, discriminated unions, and as const vs enum. Use when writing TypeScript, configuring tsconfig, implementing type guards, or debugging null/undefined errors.
Teams using typescript-expert should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/typescript-expert/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How typescript-expert Compares
| Feature / Agent | typescript-expert | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
TypeScript gotchas and decision criteria covering nullish coalescing pitfalls (|| vs ??), strict tsconfig settings (noUncheckedIndexedAccess, exactOptionalPropertyTypes), type guard patterns, discriminated unions, and as const vs enum. Use when writing TypeScript, configuring tsconfig, implementing type guards, or debugging null/undefined errors.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
> **AI-consumed reference.** Optimized for Claude to read during execution.
> Human-readable explanation: see [docs/architecture/HIERARCHICAL_PLANNING.md](../../../docs/architecture/HIERARCHICAL_PLANNING.md)
> or [docs/getting-started/](../../../docs/getting-started/) depending on topic.
# TypeScript Expert — Gotchas & Decisions
Use Context7 for TypeScript docs.
## Strict Config (Always Enable)
```json
{ "strict": true, "noUncheckedIndexedAccess": true, "exactOptionalPropertyTypes": true }
```
## Nullish Patterns
```toon
nullish[5]{bad,good,why}:
"if (x)",if (x != null),"Empty string/0 are falsy but valid"
"x || default","x ?? default","?? only catches null/undefined not falsy"
"x!.prop",Type narrowing or optional chain,"! asserts non-null — hides bugs"
"as Type",Type guard function,"as bypasses type checker"
"any","unknown + narrowing","any disables ALL checking"
```
## Type Guards
```typescript
// User-defined type guard
function isUser(x: unknown): x is User {
return typeof x === 'object' && x !== null && 'id' in x;
}
// Discriminated union (preferred for variants)
type Result<T> = { ok: true; data: T } | { ok: false; error: string };
```
## Gotchas
- `Object.keys()` returns `string[]` not `(keyof T)[]` — by design. Use `for...in` with type assertion if needed
- `enum` generates runtime code — prefer `as const` objects or union types
- Generic defaults: `function f<T = string>()` — T is inferred from usage, default only if no inference possible
- `satisfies` for type checking without widening: `const x = { a: 1 } satisfies Record<string, number>`
- `readonly` arrays: `ReadonlyArray<T>` or `readonly T[]` — prevents push/pop/splice
- Index signatures `[key: string]: T` make ALL properties optional — use `noUncheckedIndexedAccess`Related Skills
vue-expert
Vue 3 gotchas and decision criteria. Covers reactivity traps, Composition API pitfalls, and Pinia patterns.
refactor-expert
Guide safe, incremental refactoring that improves code quality without changing behavior.
react-native-expert
React Native gotchas and decision criteria. Covers FlatList optimization, storage hierarchy, and platform-specific pitfalls.
react-expert
React gotchas and decision criteria covering stale closure bugs in useEffect, conditional rendering traps (falsy 0/empty string), state management selection (useState vs Context vs Zustand vs TanStack Query), and hooks rules. Use when writing React components, debugging re-renders, choosing state management, or encountering useEffect infinite loops.
python-expert
Python gotchas and decision criteria. Covers async pitfalls, FastAPI/Django patterns, and type hint traps.
nodejs-expert
Node.js gotchas and decision criteria. Covers async pitfalls, Express/NestJS patterns, and common mistakes.
nextjs-expert
Next.js 14+ gotchas and decision criteria. Covers server/client boundary, caching strategy, and data fetching patterns Claude commonly gets wrong.
laravel-expert
Laravel/PHP gotchas and decision criteria. Covers N+1 prevention, Eloquent traps, and migration safety.
go-expert
Go gotchas and decision criteria. Covers error handling patterns, concurrency pitfalls, and interface design.
design-expert
UI/UX design expertise — component design, design system selection, responsive layout. Includes auto-detection from package.json and Context7 integration for library docs.
angular-expert
Angular 17+ gotchas and decision criteria. Covers signals vs observables, standalone patterns, and common pitfalls Claude gets wrong.
tree-of-thoughts
Branch, evaluate, prune, expand — structured search over solution space. Use for architecture with multi-step decisions, refactor planning, or complex debug hypothesis trees. Paper: Yao et al. 2023.