2026
Portfolio rebuild and narrative-driven architecture
Redesigned this portfolio around story-first sections, tokenized theming, stronger international UX consistency, and explicit AI-agent engineering proof.
About the builder
Calm product interfaces, clear frontend systems, and motion that earns its place.
Front-End Developer
I'm a front-end developer focused on clear product interfaces, maintainable frontend systems, and recent AI-agent workflows that still hold up under engineering scrutiny.
- Projects shipped
- 6+
- Technologies used
- 28+
- Years of practice
- 3+
I work best where product judgment, visual restraint, and implementation quality need to hold together under real delivery pressure.
Narrative
About Me
I'm a front-end developer with 3+ years of experience in building web applications using modern technologies like React. I have a strong understanding of HTML, CSS, and JavaScript, and I'm always eager to learn new frameworks and libraries. My development philosophy centers around clean, maintainable code and a user-first approach. I believe that great design is not just about aesthetics but also about usability and accessibility. I strive to create products that are both beautiful and easy to use for everyone.
My Strengths
Clean Code
UI/UX Design
Accessibility
Performance Optimization
Current focus
React architecture / Design system / Performance tuning / Agent orchestration
Recent path
Career Timeline
2025
Product-focused frontend delivery
Built and shipped multiple product interfaces with improved filtering, modal flows, and maintainable component boundaries.
2024
Foundation in modern React ecosystem
Expanded expertise in React, Next.js, and TypeScript with a strong emphasis on accessibility and performance.
Working style
Working Principles
01
Solve product problems first
Start from user and business goals, then select the simplest implementation that can scale.
02
Design and code as one system
Build reusable UI primitives and design tokens so consistency improves as features grow.
03
Communicate with clarity
Prefer explicit naming, predictable structures, and documentation-ready prompts/checklists so both teammates and agents can execute safely.