How I work
I build features as complete product paths: the screen, the state model, the API contract, the data rules, and the release checks. That keeps user flows clear and gives the team a system that is easier to change later.
Interface and state
Screen behavior, reusable components, forms, validation, loading states, accessibility, and feedback loops that make product flows predictable.
API contracts and services
Request lifecycle handling, auth-aware flows, service boundaries, REST integrations, and contracts that keep frontend and backend work aligned.
Data rules and release checks
Persistence choices, data rules, edge-case handling, and focused checks around the workflows most likely to affect users.