Jiyu Kim
Draw the UX/UI, set the policy, build it with AI.
I started as a UX/UI designer and now carry product management as well. I draw the screens, set the policy they follow, and build them in code with Claude Code. One person, from design to deploy.
Design and product management are not split across two desks here. The words on a screen are a promise the product makes, and whether that promise can be kept is settled in policy and schedule.
I work with Claude Code. The work does not stop in Figma: the design system, the screens and the source of truth are built in code, by me. Most of the product surface, backend aside, came out that way. The tool adds hands, and what it asks in return is judgment. Deciding what should be canonical and what should be left to the machine is where this job now lives.
The failure I guard against hardest is having two sources of truth. Synchronization maintained by human comparison breaks first when things get busy, and it breaks quietly. So the source of truth lives in one place, and drift is caught by machine.
One person, working with Claude Code
Every product surface and its source of truth, backend aside, built by one person. Below is what that came to, counted by script from repository history.
- Product screens
- 444
- Shared components
- 889
- Design tokens
- 544
- Documents
- 369
2026-04-15 - 2026-08-10 · 3.8 months · 97 active days
- Design system and product surfaces
- Product decisions and delivery
- Brand and content
- Design tooling
- Mobile spike
- Company portal
- Native shell
- Public docs
- Prototype lab
- Genesis campaignPredates the repositories, planned and designed in Figma. Live today
- Marketing sitePlanned and designed in Figma. Live today
How this was measured
These figures are extracted by script from repository history, not typed in by hand. The period runs from the first to the last day of work recorded there. An earlier stretch of work lived only in Figma; that planning and design is not machine-countable and is not in these numbers.
What I do
Design systems
Two-layer separation of primitive and semantic tokens, theme completeness checks, promotion criteria for shared components.
Information architecture
Counting screens across several products in a measurable unit and managing their state on one board.
Product policy
Wording systems for regulated surfaces, definitions of confirmed state, and acceptance criteria a team can verify.
Delivery operations
Defining role boundaries, designing release gates, and structuring issue axes so progress reports itself.
Brand and content
Logos and identity, marketing sites and campaign pages, public docs. Surfaces outside the product, held to the same standard.
Building with AI
Design systems and screens implemented directly with Claude Code. Deciding what is canonical, what is left to the machine, and letting the machine catch the drift.
On the period
The figures in this portfolio are extracted by script from repository history between mid-April and August 2026. An earlier stretch of work predates those repositories and lived in design tools; it is not machine-countable and is not included in these numbers.