How do I install the Typescript Patterns skill?

Run npx skillmds@latest add tomevault-io/typescript-patterns in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Typescript Patterns safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Typescript Patterns?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Typescript Patterns free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Typescript Patterns?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Typescript Patterns by tomevault-io

Name: Typescript Patterns
Author: tomevault-io

Typescript Patterns

TypeScript design patterns including bounded contexts, class-based exports, barrel exports, atomic tests, and business capability naming. Use when organizing code into domains, designing public APIs, creating barrel exports, structuring test files, or choosing between function and class-based exports. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

TypeScript Design Patterns

When applying TypeScript design patterns, read and follow the policy guide:

Policy: docs/policies/typescript-patterns.md

When This Applies

Organizing source code into bounded contexts or domain folders
Designing public API surfaces with barrel exports (index.ts)
Choosing between function exports and class-based namespace exports
Naming APIs by business capability (not vendor/tool names)
Implementing the Adapter Pattern for swappable providers
Separating system interactions into *.system.ts files
Writing atomic tests that work in parallel execution
Structuring test folders to mirror source folders

Principles Checklist

Bounded context folders: src/domains/ by business domain, not technical layer
Business capability naming: ISecretStore not IOnePasswordClient
Class-based exports: group related operations under namespace classes
Barrel exports: index.ts defines public API, hides internals
System separation: *.system.ts for external I/O, excluded from coverage
TDD: RED -> GREEN -> REFACTOR with architecture-first skeleton
Unit tests without mocks: real in-memory implementations, mocks only for integration
Atomic tests: new mock instance per test() block, no shared state

Read the full guide for patterns, examples, and anti-patterns.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: typescript-patternsdescription: TypeScript design patterns including bounded contexts, class-based exports, barrel exports, atomic tests, and business capability naming. Use when organizing code into domains, designing public APIs, creating barrel exports, structuring test files, or choosing between function and class-based exports. Use when this capability is needed.---# TypeScript Design PatternsWhen applying TypeScript design patterns, read and follow the policy guide:**Policy**: `docs/policies/typescript-patterns.md`## When This Applies- Organizing source code into bounded contexts or domain folders- Designing public API surfaces with barrel exports (`index.ts`)- Choosing between function exports and class-based namespace exports- Naming APIs by business capability (not vendor/tool names)- Implementing the Adapter Pattern for swappable providers- Separating system interactions into `*.system.ts` files- Writing atomic tests that work in parallel execution- Structuring test folders to mirror source folders## Principles Checklist1. **Bounded context folders**: `src/domains/` by business domain, not technical layer2. **Business capability naming**: `ISecretStore` not `IOnePasswordClient`3. **Class-based exports**: group related operations under namespace classes4. **Barrel exports**: `index.ts` defines public API, hides internals5. **System separation**: `*.system.ts` for external I/O, excluded from coverage6. **TDD**: RED -> GREEN -> REFACTOR with architecture-first skeleton7. **Unit tests without mocks**: real in-memory implementations, mocks only for integration8. **Atomic tests**: new mock instance per `test()` block, no shared stateRead the full guide for patterns, examples, and anti-patterns.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/lekman) — claim your Tome and manage your conversions.

Frequently asked questions