Case Study

Callara logo — koala mark with script wordmark

Callara Skincare AI onboarding

Built with

Figma logoFigma
Claude logoClaude
Cursor logoCursor
GitHub logoGitHub
React logoReact
TypeScript logoTypeScript

Overview

Callara is an AI skincare startup based in Japan with a target market of U.S. consumers, and a forecasted valuation of $2M MRR by next quarter. Callara's founders reached out to me for fractional design help with their prototype to help secure seed funding.

I designed and led the entire AI and UX strategy for Callara's onboarding, resulting in a 67% increase in product input and a 98% increase in users completing skin profile analysis. I delivered a robust prototype and automated a design-to-code pipeline with LLM tools before deploying the live code to the repo.

What I shipped

Scroll to explore the full flow, from onboarding through the core experience.

Find out what your skin needs
Scan your shelf intro
Callara optimizes your routine intro
Login screen
Sign up screen
Scan at least 3 products camera screen
Photo library picker
Here's what we found — scanned items review
Scan results identified
Is this the right product — unable to identify
Is this the right product — manual product entry
Right product confirmed
Skincare goals selection screen
Add products to unlock analysis
Core AI recommendation with 94% match confidence
Core progress screen with 7-day streak

Setting up skills in Cursor to eliminate drift

Repo

I built a Cursor skill that treats Figma as the single source of truth, then audits the whole repo against it, catching anything that's drifted before it ever ships.

Hover to preview the skill
M+SKILL.md
Preview SKILL.md
~/Documents/GitHub/skin-care/.cursor/skills/sync-design-tokens/SKILL.md

Impact

00%

Increase in user product input and retention.

00%

Increase in onboarding data collection.

LLM readable design system

I used token architecture to define consistent output and eliminate drift with our AI.

MVP definition

I worked with founders and engineers to go narrow on our MVP and define crucial UX.

Problem and opportunity space

Challenges

Not clarified MVP and no data funnel

Not clarified MVP and no data funnel

Not clarified MVP and no data funnel

The initial prototype was based off of large user assumptions that had not been validated.

I pressed founders during these conversations to aggresively validate, and remove features that werent crucial to their north star metric.

We defined user product input as the main litmus for product health, and prioritized our features around this experience for phase 1 rollout.

AI prompted design caused drift

AI prompted design caused drift

AI prompted design caused drift

Callara's team initially had vibecoded their prototype using generative prompts in Figma make. The problem with this was that there was endless drift everytime a session was initiated.

Their prototype was very crude and fragmented, with no distinct branding, components, hierarchy, user states, or AI guidelines.

Product vision

MVP clarity

Initially, Callara wanted a chief-of-staff AI partner with dozens of features. I pushed back on this and brought influence to help narrow their MVP to a solid feature and problem they could solve better than anyone else.

Since their revenue model depended heavily on product input, I documented a hypothesis and a strong argument to focus on product input as a feature.

We could only achieve this if Callara's profile accuracy was strong. I decided that onboarding was a primary objective before designing our core screens.

Onboarding welcome illustration — user scanning skincare products with AI

Onboarding was crucial to gather data and improve AI accuracy for product recommendations.

Initial designs, foundations and interaction

After gathering data and user research from our founders, I put together a product vision with design principles to help guide our metrics and jobs to be done.

For initial design direction, they requested a modern but cute tone, acting as an AI skincare coach.

I did heavy research into which AI tools would be best suited for quick iterations, and how we could streamline AI production without burning through too many tokens, while keeping parity with the design foundations we had in Figma.

Once these metrics and goals were aligned, I started drafting wireframes and foundations for our LLMs to reference.

Foundations → semantic tokens

Foundation spec

ContinueContinueContinueContinue

L'Oréal

Midnight Serum

Unable to identify

Needs verification

Semantic tokens

Design principles

Design principles

AI guidelines strategy

I decided to draft an AI guidelines document to keep guardrails in place, and create a seamless user experience around how AI should be surfaced and how it should use customer data. Users have a profound initial distrust of AI. We found it was paramount for momentum and retention in the prototype to display AI's confidence level and its likelihood of failure. Graceful recovery states were essential to keep momentum in the experience. I applied this thinking to all of our design decisions during meetings.

Hallucinations
Unable to identify product — AI uncertainty state
Recovery states
Add products to unlock analysis recovery state
Guidelines
Scan results with AI identification notice
Transparency
AI match confidence and disclaimer

What I shipped

Find out what your skin needs
Login screen
Scan products camera
Photo library picker
Here's what we found
Manual product entry
Right product confirmed
Skincare goals
AI recommendation
Progress and streak

Impact and learnings

Learning 1
Learning 2
Learning 3
Learning 4