Menu
Theme

Years I contributed:2020–2024Design systems · Component library

Soramitsu UI Kit

A design system I created from scratch and helped adopt across Soramitsu to reduce repeated work and make delivery easier across teams.

My role
Creator, technical lead & component engineer
Context
Soramitsu · Company-wide component library
Explore the project

Soramitsu UI Kit is a shared Vue and TypeScript component library for the company’s product teams. It provides common component APIs and behavior, with styles that can be adapted to each application.

I created the library and led its development and adoption across the company. My work covered the component code, developer tooling, themes, and ongoing maintenance of a package used by multiple product teams.

Built with
VueTypeScriptSCSSCSS custom propertiesStorybookJestRollup

Inside the product

The same Soramitsu form controls reconstructed in light and dark neumorphic themes.

One component family, two themes

Runtime color variables carry the theme through inputs, selections, and actions. My work covered the reusable components and their behavior, alongside the team’s visual design.

Soramitsu inputs, switches, tabs, and buttons arranged into a settings interface.

Components that become an application

The library provided shared APIs, examples, and releases that product teams could adopt. I led that adoption through application refactoring, reviews, and knowledge-sharing sessions.

  • Building the shared library

    Created the initial package structure and implemented component families including buttons, inputs, forms, layouts, menus, tabs, selectors, and pagination, with Storybook examples and test support.

  • Runtime themes and neumorphic controls

    Introduced CSS color variables for live theme changes and worked with the team on dark-theme and neumorphic styles. Refined shadows, focus states, selected controls, and expanded components.

  • Tooling and package maintenance

    Maintained Storybook and the build configuration, reviewed component contributions, and prepared package releases. Added workspace publishing configuration and made the Vue package available for public distribution.

The case for changing a working product

When I joined Soramitsu in 2020, I reviewed the company’s entire product portfolio as part of my onboarding. I started working on several of those products on my first day. The same controls appeared in the design mockups for nearly every product, so I looked for shared components and conventions I could use in my own work. In most cases, each team had built its own version. A fix in one application still left the others with the same work to do. I took that problem to my project manager and proposed a shared UI kit. He backed the idea, and we set aside time for me to build it alongside my product work.

The harder decision came when I asked teams to adopt the kit in applications that already worked. Each project manager would have to make room in an upcoming release. I organized company-wide presentations for the executive team and brought estimates and examples from other companies. In product meetings, we compared the cost of migration with the engineering time a team could save on later features and fixes. In front-end meetings, we worked through which behaviors each product relied on and how to preserve them during the switch.

I led the refactoring and worked on the applications myself. In July, I migrated the Unkai application and connected it to the UI Kit. In September, I used that same setup in the first commit of a new exchange application. In October, I put it in the getting-started guide and added an interactive example where engineers could try their product’s colors on the controls. Teams left our sessions with a setup they could use in their own codebase.

By the end of 2020, almost every active front-end project at Soramitsu used the kit, and new projects started with it. Engineers moving between products could bring their knowledge of component behavior, styling, and shared utilities with them. They could spend their onboarding time learning what made the new product different.

My work at Soramitsu

At Soramitsu, I grew from Senior Front-end Developer to Front-end Team Leader, then Head of Front-end Development. That progression covered work across banking, wallets, exchanges, and shared front-end infrastructure.

Career timeline January 2020–2026

  1. Head of Front-end Development

    May 2024–2026

  2. Front-end Team Leader

    January 2021–May 2024

  3. Senior Front-end Developer

    January 2020–January 2021

Broader responsibilities

Progressed from senior engineering to leading the front-end department, while continuing implementation and code review.

  • Created the front-end department and established its structure, engineering workflows, and quality standards.
  • Built shared design-system foundations and helped migrate projects to a common front-end technology stack.
  • Hired and mentored developers, coordinated roadmaps and delivery, and supported collaboration across product, design, and engineering.
  • Organized internal meetups and knowledge-sharing sessions, and contributed to technical direction across company projects.
Full CV
Start a conversation

What are you
working on?

An engineering role, a product to build, or a technical problem to work through. I’d like to hear about it.