export default typescript-coding

name

typescript-coding

description

Expert TypeScript/JavaScript development guidance. Use when planning or writing TypeScript/JavaScript code, setting up TS/JS projects, configuring build tools (pnpm, Vite, TypeScript), implementing tests (Vitest), adding logging (pino for services, chalk/console for CLIs), working with React/Tailwind/Xstate, or following FP patterns. Covers stack decisions, tooling setup, testing strategies, and logging patterns for both services and CLI tools.

TypeScript Coding

Overview

Expert TS/JS development guidance across:

• Stack decisions (preferred libs)
• Tooling setup (pnpm, Vite, TS configs)
• Testing patterns (Vitest)
• Logging strategies (CLI vs services)

Quick Reference

Stack → ./STACK.md

Preferred libraries by category:

• Package mgmt: pnpm, Vite, TypeScript
• State/testing: Xstate, Vitest
• Quality: ESLint, Prettier
• UI: React, Tailwind, shadcn/ui
• Forms/data: react-hook-form, zod, tanstack query/router
• CLI: boxen, chalk, commander, ora
• Utils: date-fns, dotenv
• Release: semantic-release, husky

Tooling → ./TOOLING.md

Setup patterns:

• FP patterns (avoid this, new, classes)
• Import aliases config
• pnpm commands & workspaces
• tsconfig.json templates
• Vite setup
• ESLint/Prettier config
• Monorepo structure

Testing → ./TESTING.md

Vitest patterns:

• Parameterized (test.each) vs individual tests
• Decision framework

Logging → ./LOGGING.md

App-specific patterns:

• CLI tools → console + chalk/ora (human-readable)
• Services/APIs → pino (structured JSON)

Common Tasks

New React app:

pnpm create vite . --template react-ts

Install deps:

pnpm add <package>           # regular
pnpm add -D <package>        # dev
pnpm add <pkg> --filter @org/target  # workspace

ESLint setup: See ./TOOLING.md#eslint - Never disable rules except no-console for CLI

Tailwind setup: See ./TOOLING.md#tailwind

Monorepo: See ./TOOLING.md#pnpm-workspaces for complete structure

Testing decision:

• Pure fn w/ similar cases → test.each()
• Different setup/mocks → individual tests
• See ./TESTING.md for decision tree

Logging:

• CLI → console + chalk (see ./LOGGING.md#cli-logging)
• Service → pino (see ./LOGGING.md#pino)

FP Patterns

• Avoid this, new, prototypes
• Plain objects {}, not classes
• Exception: custom Error classes
• Small, focused functions

See @docs/CODING_STYLE.md for universal FP guidelines