Vladimir HlobchastyiVladimir HlobchastyiSenior Software Engineer
Back to work
Case Study
AI / vibe-coded rescue · architecture refactor

Clinical Learning Platform

Web platform for clinical training, assessment and AI-assisted learning workflows, rebuilt into a production-ready React architecture.

Role

Frontend Developer

Focus

Architecture recovery after vibe coding, RBAC, tenant scope, route stability, legacy removal and production hardening.

Stack

React 19TypeScriptViteTanStack QueryReact RouterTailwind CSS 4ZustandZodRadix UIshadcn/uiSentry
Preview & Screenshots
01 / 04
Clinical Learning Platform — image 1
Clinical Learning Platform — image 2
Clinical Learning Platform — image 3
Clinical Learning Platform — image 4

Overview

Contributed to a large clinical-education web platform combining structured learning, assessment and AI-assisted workflows. Worked across a React + TypeScript codebase to recover structure after vibe coding and turn an unstable AI-generated foundation into a maintainable production architecture.

Challenge

The work was not a small feature, but a structural rescue after vibe coding: scattered logic, duplicate legacy paths, inconsistent multi-tenant scope, broken routes and weak separation between domains. The platform needed real cleanup before it could be treated as production software.

Outcome

Delivered a production-oriented refactor with restored feature boundaries, safer access control, consistent tenant scoping, removed legacy dead ends, more predictable data flow and a codebase that could be extended without compounding earlier issues.

Responsibilities

04 areas
01

Architecture refactor

Reworked scattered AI-generated, vibe-coded code into clearer domain boundaries, reduced duplication and aligned the frontend with a predictable React project structure.

02

Access control and tenant scope

Audited and corrected role checks, tenant-scoped data flow and route protection so user data stayed isolated and predictable across the platform.

03

Legacy cleanup

Removed dead routes, legacy hooks, stale screens and mock data that were blocking production readiness.

04

Reliability and monitoring

Hardened key flows, improved error boundaries and integrated runtime monitoring so production incidents could be detected and resolved quickly.