Frontend: Angular. The application was built on the

Frontend: Angular. The application was built on the Angular framework as a TypeScript single-page application. Strict typing, a strong CLI, and an opinionated project structure kept generated components uniform, and lazy-loaded feature modules kept the initial payload small for students on entry-level phones and slow networks. Backend: FastAPI. The backend was built on FastAPI with async Python. Pydantic models gave every request and response a machine-readable schema, and FastAPI's auto-generated OpenAPI specification became a first-class input to our context packets: the generator always knew the exact shape of the API it was writing against.

Database: PostgreSQL. PostgreSQL was our system of record. Bookings, wallet movements, and payouts are exactly the kind of data that wants real transactions, foreign keys, and constraints; schema changes flowed through versioned migrations, and the schema fragments in each context packet came straight from the migration files. End-to-end testing: Playwright. Playwright drove browser-based end-to-end tests against real workflows on the dev environment. Key PRD scenarios, such as searching for a teacher, booking a first free session, and completing a payment, ran as scripted user journeys on every deployment, including mobile viewports and throttled-network profiles that mirror our target users. Because these tests exercised the same flows the PRD described, they were the final word on whether a generated feature actually behaved as specified.