Menü
Use when TypeScript work involves naming, abstractions, classes, local reasoning, semantic centers, full cutovers, type assertions, or design cleanup.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use when designing, reviewing, refactoring, or implementing code that should stay simple, testable, readable, and sustainable. Applies principles for investigating before changes, keeping few layers, making I/O explicit, using dependencies deliberately, organizing by feature, naming consistently, and presenting plans progressively.
Makes answers easier to start reading, scan, resume, and understand without losing important detail. Uses useful-answer-first structure, short paragraphs, clear literal headings, simple language, preserved nuance, natural voice, and small ASCII diagrams when they clarify structure or flow.
Use when working on TypeScript code and needing to choose the smallest focused TypeScript skill for coding standards, boundaries, composition, configs, async control, error handling, observability, security, or testing.
Use when TypeScript code coordinates async work — Promise.all vs sequential, bounded concurrency, AbortSignal cancellation, cleanup/teardown, or process lifecycle (SIGTERM, graceful shutdown).
Use when TypeScript code moves provider, SDK, API, request, response, generated, or raw input shapes across owned application boundaries.
Use when TypeScript work involves dependency construction, composition roots, factories, lifecycle, scope, singletons, caching, or runtime provider selection.
| name | typescript-coding-standards |
| description | Use when TypeScript work involves naming, abstractions, classes, local reasoning, semantic centers, full cutovers, type assertions, or design cleanup. |
Use this skill for local design quality in owned TypeScript code: names, abstractions, classes, semantic centers, and cutovers.
| If you see... | Read |
|---|---|
| wrapper, base class, shared helper, interface, manager, adapter-like abstraction | rules/abstraction-and-local-reasoning.md |
| class proposed for stateless behavior | rules/functions-vs-classes.md |
| confusing name, leaked implementation word, hidden important branch | rules/naming-and-semantic-center.md |
| old and new implementations coexisting | rules/cutovers.md |
!, as, as unknown as, as any, @ts-ignore, non-null assertion, forced type | rules/type-narrowing-over-assertion.md |
| blank-line groups in a function, comment labels, long function, mixed levels of abstraction, extraction question, reader must jump up/down through helpers | rules/vertical-discipline.md |
| same-shape primitives mixed (UserId vs OrderId), validated value losing its proof | rules/branded-and-opaque-types.md |
switch on union without default: never, "what if a new variant is added", silent fallback | rules/exhaustive-narrowing.md |
function copy-pasted per type, generic with any, conditional/mapped type question | rules/generics-and-conditional-types.md |
Abstraction cost and local reasoning.
Function vs class defaults.
Names in owned code.
Clean cutover policy.
Type narrowing over assertion as hard gate.
Branded types and nominal typing for domain primitives.
Exhaustive narrowing of discriminated unions.
Generics, conditional types, and mapped types — when each earns itself.
Vertical discipline: comment labels first, then extraction by responsibility.
../typescript-boundaries/SKILL.md.../typescript-composition/SKILL.md.../typescript-configs/SKILL.md.../typescript-testing/SKILL.md.Preserve local reasoning. Add structure only when it removes more confusion than it creates.