Menu
Use when TypeScript code moves provider, SDK, API, request, response, generated, or raw input shapes across owned application boundaries.
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.
Based on SOC occupation classification
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 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.
| name | typescript-boundaries |
| description | Use when TypeScript code moves provider, SDK, API, request, response, generated, or raw input shapes across owned application boundaries. |
Use this skill when external shapes meet owned code. The goal is to keep foreign semantics at the edge and expose smaller local models inward.
| If you see... | Read |
|---|---|
| provider/SDK/generated type imported by business logic | rules/provider-containment.md |
| request/body/query/env-like raw shape passed inward | rules/raw-input-to-internal-model.md |
| proposal to add a mapper/adapter | rules/earned-mapping.md |
| local model named after provider vocabulary | rules/local-naming.md |
provider-containment.md owns vendor SDK / generated / external API client types. raw-input-to-internal-model.md owns HTTP request/response/transport shapes, env-like input, webhook payloads, CLI args, untyped JSON. When in doubt: is the type defined by us or by an external runtime contract?
A payload can violate both at once: a webhook body cast to a vendor SDK type (e.g. req.body as Stripe.Event) is raw transport input that needs parsing/verification AND a vendor type that should not flow past the handler — parse the input at the edge, then translate the vendor shape to a local event model before business logic sees it.
../typescript-composition/SKILL.md.../typescript-coding-standards/SKILL.md.../typescript-configs/SKILL.md.Translate at the edge when meaning differs. Do not create a mapper that only adds ceremony.