TypeScript Functional Patterns

Write TypeScript around three complementary ideas: transform, result, and match. Remeda makes data flow readable and inference-friendly; neverthrow makes expected failure explicit in a function's type; ts-pattern makes finite state and union decisions exhaustive. Use the idea that solves the local problem, then compose the ideas at boundaries. The goal is a small, honest API surface—not functional-looking syntax everywhere.

Read PATTERNS.md when implementing or reviewing a non-trivial pipeline, error boundary, or discriminated-union decision.

Process

1. Establish and enforce the project baseline

Inspect package.json, lockfiles, TypeScript configuration, scripts, and nearby code before editing. This skill establishes a project-wide behavioral baseline, not a package-wide dependency baseline.