General JavaScript/TypeScript

What problem does it solve?

In JavaScript and TypeScript codebases, inconsistent naming, scattered environment access, weak error handling, and leaky imports create brittle systems that are hard to refactor and easy to break.

Core Features & Use Cases

• Environment centralization: Move all runtime configuration and validated env access into src/config, preventing scattered process.env usage and enabling fail-fast startup behavior.
• Reusable structure and boundaries: Enforce a consistent project layout with src for application code, src/utils for framework-agnostic helpers, and src/errors for typed Error classes.
• Safer API contracts: Define explicit input/output types for API boundaries so modules never return raw database objects and response shapes remain stable.

Quick Start

Tell your coding agent to apply this skill’s rules by proposing a refactor plan that centralizes environment handling in src/config, moves typed errors into src/errors, and introduces explicit src/types contracts for each API boundary.