typescript

Apply TypeScript style rules for typed errors, decoders, and module structure.

7|Updated Jan 26, 2026

Search Tags:#typescript #linting #zod #type-safety #io-ts #decoders #runtime-safety

Ready to run

npx skills add https://github.com/bricerising/enterprise-software-playbook --skill typescript-bricerising

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: typescript
Source: https://github.com/bricerising/enterprise-software-playbook/tree/main/skills/typescript
Command: npx skills add https://github.com/bricerising/enterprise-software-playbook --skill typescript-bricerising

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TypeScript codebases often suffer from unclear boundaries, brittle type usage, and unsafe runtime behavior; this guide provides explicit rules to improve readability, type safety, and maintainable module structure.

Core Features & Use Cases

Clear guidelines for module structure, error handling, and type modeling.
Validation with decoders (Zod/io-ts) and boundary validation across services.
Real-world use: apply to new TS modules, React components, and Node services to reduce runtime errors and improve maintainability.

Quick Start

Apply this TypeScript style guide to a new module to ensure consistency and safe runtime boundaries.

Frequently Asked Questions about typescript

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce runtime type safety in TypeScript modules?▼

Use runtime decoders like Zod or io-ts to validate external inputs at module boundaries, preventing unsafe runtime behavior. This establishes robust type safety by ensuring untrusted data matches expected domain types before processing.

What is the best way to structure TypeScript codebases to prevent cyclic dependencies?▼

Prevent cyclic dependencies in TypeScript by prescribing clear module structures with explicit boundaries and domain type modeling. Enforcing strict null checks and proper error handling reduces runtime errors and improves maintainability.

How do I validate boundary inputs across Node services and React components?▼

Validate boundary inputs across Node services and React components by applying robust decoders like Zod or io-ts at service edges. This enforces typed errors and prevents untrusted data from causing runtime exceptions in shared libraries.

Does this TypeScript style guide apply to existing shared libraries?▼

Yes, this style guide applies to existing shared libraries, React apps, and Node services. It translates codebases into safer, more maintainable code by providing clear guidelines for domain type modeling, error handling, and module structure.

When should I use decoders instead of standard TypeScript interfaces?▼

Use decoders instead of standard TypeScript interfaces when validating untrusted external inputs at system boundaries. Decoders provide runtime validation and typed errors, whereas standard interfaces only enforce compile-time type checks without runtime safety.