skills

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 naming, abstractions, classes, local reasoning, semantic centers, full cutovers, type assertions, or design cleanup.

Use when TypeScript work involves dependency construction, composition roots, factories, lifecycle, scope, singletons, caching, or runtime provider selection.

Use when TypeScript work involves env values, config parsing, contextual config objects, config defaults, validation boundaries, or migration from legacy config reads.

Use when TypeScript code needs to express failure with a canonical app-owned error model, family-level runtime wrappers or Result-based propagation, stable error codes, retry classification, and safe boundary translation.

Use when TypeScript work involves logging, tracing, OpenTelemetry, AWS X-Ray, span design, trace context, actionable diagnostics, or observability boundaries.

Use when TypeScript work involves secrets, credentials, crypto choices, redaction, secret source pointers, sensitive endpoints, or security-sensitive logging.

Use when TypeScript work involves tests, local test style, behavior-first names, characterization before refactor, config tests, composition-root smoke tests, boundary contracts, or brittle structure assertions.