NEEL RATNThe frontend backbone for curators managing multi-strategy vaults across YieldFi.
Overview
YieldFi is a DeFi yield protocol. I own the curator dashboard — the surface vault curators use to manage strategies, allocations, and risk — across both the V2 and V3 generations of the product.
Problem
V2’s dashboard had accumulated real debt: inconsistent data-fetching patterns, slow strategy views, and no shared component system, which made every new curator feature slower to ship than the last.
Architecture & Approach
The rebuild moved to a typed data layer with a single source of truth for vault and strategy state, server-driven config for strategy cards, and route-level code splitting per dashboard module. Along the way I extracted the shared UI into a standalone component library (now Yfi-Components) rather than let each screen re-solve the same table and form patterns.
Metrics
Learnings
Rebuilding a live product means sequencing migrations behind the same UI so curators never notice a seam. Investing in a shared component library early paid for itself within one release cycle.