Skip to content
Senthil Kumar

Tools

What I choose — and why

Opinionated defaults for platforms and products — organized by craft, with the reasoning behind each pick. Not a logo wall.

01Core

UI platforms

Foundations I reach for when greenfielding long-lived interfaces.

  • React

    Component composition and ecosystem maturity for enterprise UIs that need to last.

  • TypeScript

    Contracts at the edges — fewer runtime surprises across squads and packages.

  • Next.js

    When routing, SEO, or server rendering matter for the product surface.

  • Vite

    Fast SPA shells and library work when I want minimal ceremony and instant feedback.

02Architecture

Platform patterns

How I structure delivery across teams, apps, and shared packages.

  • Micro Frontends

    Independent delivery for large multi-squad platforms without a single release train.

  • Monorepo

    Shared packages, consistent tooling, and coherent delivery across apps and libraries.

  • Redux Toolkit

    When orchestration across domains needs predictable, shared store patterns.

03State

Data & persistence

Server state, local atoms, and privacy-first client storage.

  • TanStack Query

    Server state with caching, retries, and invalidation that matches how APIs actually behave.

  • Jotai

    Fine-grained client state without unnecessary global complexity.

  • IndexedDB

    Edge-native persistence when data should stay on the device.

04Interface

Design systems

UI primitives and visualization for dense product surfaces.

  • Styled-Components

    Themeable, Figma-faithful design systems with scoped CSS-in-JS.

  • Radix UI

    Accessible primitives without fighting a heavy design system.

  • TanStack Table

    Headless tables that scale from simple lists to complex data grids.

  • Highcharts

    Production-grade charts when dashboards need dense, interactive visualization.

05Services

APIs & cloud

Runtime, HTTP, cloud, and background work that stay close to the frontend.

  • Node.js

    Pragmatic API layer that matches the frontend team’s mental model.

  • Express

    Thin HTTP servers when I need control without a heavy framework.

  • AWS

    Cloud primitives that scale with enterprise delivery and operations.

  • Axios

    Consistent HTTP clients with interceptors for auth and error shaping.

  • Trigger.dev

    Durable background jobs and workflows without babysitting custom queues.

06Data

Backend & edge

Managed data, documents, and serverless Redis at the edge.

  • Supabase

    Postgres, auth, and realtime without standing up ops from scratch.

  • MongoDB

    Flexible document storage for evolving product schemas and content-shaped data.

  • Upstash

    Serverless Redis for rate limits, caches, and low-latency queues.

07Craft

Quality & DX

What I standardize so reviews stay about architecture, not formatting.

  • React Testing Library

    UI tests focused on behavior users see — not implementation trivia.

  • React Hook Form + Zod

    Type-safe forms with schemas that double as runtime validation.

  • ESLint + Prettier

    Shared lint and format rules so reviews stay about architecture.

  • PostHog

    Product analytics, session replay, and feature flags wired into how teams learn and ship.

  • Agile / design & code reviews

    Structured feedback loops that raise the floor for the whole team.

Want the shorter flagship list? See the home stack — or talk through architecture choices for your next platform.

Home stack →Contact