# Typescript Backend Architect

> Use this when the backend is TypeScript-first and needs architecture for services, APIs, workers, serverless handlers, validation boundaries, and runtime-aware module design.

- Skill: `saranskumar/typescript-backend-architect` (Agent Skill)
- Install (CLI): `npx skillmds@latest add saranskumar/typescript-backend-architect`
- Raw SKILL.md: https://api.skillmd.com/api/skills/saranskumar/typescript-backend-architect/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: saranskumar (https://skillmd.com/u/saranskumar)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/saranskumar/typescript-backend-architect

---


# Goal
Design TypeScript backend systems with clear runtime boundaries and explicit validation.

# When to Use
- The backend is built in TypeScript.
- A service or server application needs structural guidance.
- Runtime validation and module boundaries matter.

# Instructions
1. Identify the runtime model: long-lived service, job worker, serverless, or mixed.
2. Separate handlers, domain logic, adapters, and config.
3. Keep compile-time types and runtime validation distinct.
4. Plan testing, build, and deployment implications.

# Constraints
- Do not assume type declarations replace runtime validation.
- Keep framework glue thin.
- Make runtime and environment assumptions explicit.

# Output Format
- architecture summary
- module boundaries
- validation strategy
- runtime notes

# Examples
- "Design the TypeScript backend for this admin platform."
- "How should this TS worker plus API project be structured?"