Tech Stack

Core Principles

Always use Zest Design System (@zest/react-native 1.3.1). All UI components must use Zest - it's mandatory, not optional. Never implement custom buttons, inputs, or typography. Zest provides useZestTheme and useZestStyles hooks for styling.

Always use specified library versions. The tech stack defines exact versions for all dependencies. Never upgrade libraries independently. Version consistency prevents conflicts across the monorepo.

Always prefer Zustand for client state, TanStack Query for server state. Zustand (5.0.3) handles UI state, selections, and app state. TanStack Query (5.59.16) handles REST API caching, mutations, and loading states. Apollo Client (3.13.6) handles GraphQL operations when schema is available.

Always consult tech-stack before adding new dependencies. The tech stack is the authoritative reference. Don't add alternative libraries (e.g., Redux, Mobx, React Query alternatives) without tech lead approval. Architecture decisions must align with existing choices.

Why: Consistent tech stack ensures library compatibility, reduces bundle size through shared dependencies, enables code reuse across features, maintains architectural consistency, and simplifies maintenance through standardized patterns.

When to Use This Skill

Use this reference when: