メニュー
Use when TypeScript work involves dependency construction, composition roots, factories, lifecycle, scope, singletons, caching, or runtime provider selection.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | typescript-composition |
| description | Use when TypeScript work involves dependency construction, composition roots, factories, lifecycle, scope, singletons, caching, or runtime provider selection. |
Use this skill when code decides what dependencies exist, how long they live, or which runtime implementation is selected.
| If you see... | Read |
|---|---|
| provider/client selected inside behavior code | rules/composition-root.md |
| singleton, cache, pool, memoization, request scope | rules/dependency-scope.md |
| question of ready dependency vs factory | rules/ready-instance-vs-factory.md |
| logger/tracer/exporter lifecycle or provider setup | ../typescript-observability/SKILL.md plus rules/composition-root.md |
../typescript-boundaries/SKILL.md.../typescript-configs/SKILL.md.../typescript-testing/SKILL.md.../typescript-observability/SKILL.md.Assemble dependencies at the edge. Pass ready dependencies inward unless construction must vary at call time.
Use when designing, reviewing, refactoring, or implementing code that should stay simple, testable, readable, and sustainable. Covers investigation, architecture, dependency boundaries, cohesive units, naming, and clear plans. Also use when code hides I/O or dependencies, adds unnecessary layers, mixes business and infrastructure concerns, or fragments one flow across tiny helpers.
Makes answers easier to start reading, scan, resume, and understand without losing important detail. Use when the user asks for simpler, clearer, less dense, dyslexia-friendly, step-by-step, more scannable, more natural, less robotic, less AI-sounding, or better explained answers.
Use when TypeScript code design, implementation, review, debugging, or testing needs focused guidance on coding standards, boundaries, composition, configs, async control, error handling, observability, security, or testing. Do not use for prose-only, formatting-only, or history requests that merely mention TypeScript.