Case Study

Gear Advisor

An AI shopping agent for snowboard gear that's allowed to say "don't buy that." Designed, researched, and vibe-coded with real API calls.

Timeline
Spring 2026 · 10 weeks · Independent study
Collaboration
Brinda Joshi (designer, plugin) · Jason Levine (AWS UX Lead, mentor)
My Role
Product Designer · UX Research · Front-End Build + AI Integration
Tools
Figma, Figma Make, Kiro, Vite.js, TypeScript, Claude
Shipped
Survey flow · Results dashboard · Chrome plugin
Introduction

Shoppers weren't scared of the price. They were scared of buying the wrong board.

So I designed how the AI should think before designing any screens. Then I learned to code so it could actually run: a survey, a results dashboard, and a Chrome plugin that judges the board you're already looking at.

From our mentor
"You [Brinda] and Alina Mao rocked it, and I was so impressed how you both embraced the technology and innovated so quickly in building a customer-focused, AI Agent experience. Nice work!"
Jason LevineAWS UX Lead · Project mentor LinkedIn ↗
Survey flow. A chat-style quiz: sport, terrain, turns, days per season, budget.
The Challenge

Buying a snowboard is a high-stakes guessing game.

Sidecut. Flex. Camber. Beginners can't translate any of it into how a board rides. And the people explaining it usually have inventory to sell.

01

Information overload

Specs don't map to feel. Nobody knows what "5/10 flex" means on the mountain.

02

Trust gap

Retailers have stock to clear. Neutral advice is hard to find.

03

Decision fatigue

High price plus a 7 year lifespan makes every choice feel permanent.

Core insight

"Users aren't afraid of high prices. They're afraid of buying the wrong thing."

6In-depth rider interviews
7 yrsAverage purchase cycle
3Core user personas
User Research

What riders told us, and what they didn't say out loud.

We interviewed 6 riders across skill levels and affinity-mapped everything. Three psychological patterns kept showing up.

Insight 01

Expert ego vs. safety

People buy boards above their level because they look cool. Nobody wants to admit they're still a beginner. That's how injuries happen.

Insight 02

Math as permission

Renters don't balk at the total price. They need a clear break-even point before they let themselves buy.

Insight 03

The 7 year silence

Brands disappear between purchases. That's 6 years of relationship nobody is building.

Three personas, one shared pain

Different skill levels. Same wall: nobody trusts the advice they're getting.

Persona 01

The Hesitant Outsider

Rides under 5 days a year. Mostly rents. Scared to commit.

  • Needs the math to justify buying
  • Worried about overpaying
  • Leans on friends' opinions
Persona 02

The Informed Progressor

Owns basic gear. Ready to upgrade as skills grow.

  • Cares about technical fit
  • Will spend, but wants expert input
  • Thinks about what helps them improve
Persona 03

The Aesthetic Motivator

Brand and looks come first. Fit comes second, if at all.

  • Heavily brand driven
  • May pick gear beyond their ability
  • Needs style and safety balanced
What they all share

Trust deficit + jargon overload

Every persona hit the same wall.

  • Can't turn specs into feel
  • Distrusts retailers with stock to move
  • No neutral place to get a straight answer
Design Solution

From sales assistant to neutral broker.

Most shopping AI is a chatbot bolted onto a store. We flipped it. Before any UI, we defined how the AI should think: what it's allowed to say, what it must cite, and when it has to push back.

Principle 01

Anti-sycophancy

The AI has to be willing to say no. If a board is unsafe for your level, safety beats making you happy.

  • Survey results outrank personal preference
  • Risks and mismatches get flagged clearly
  • Always offer an alternative, never just "no"
Principle 02

Show your sources

Every recommendation cites where it came from, so users can check the reasoning themselves.

  • Industry standards: PSIA-AASI
  • Expert reviews: OutdoorGearLab
  • Community: Reddit long-term feedback
Results page: AI recommendation with an honest con, cited sources, and a value calculator
Results page. An honest con, cited sources, and the value calculator showing buying saves $46 over 3 years.

The plugin: advice right where you shop

To test the idea in the wild, the advisor lives inside real product pages as a Chrome extension. It sits beside the page, not on top of it.

Evaluate the board you're looking at first. Suggest alternatives second.

Four features, each tied to an insight

Feature 01 · Expert ego

Assessment before preference

Skill check first, based on PSIA-AASI standards. Style and brand come after. If they conflict, safety wins.

Feature 02 · Trust gap

Traceable truth sources

A layered "truth library": standards, expert reviews, community voice, and real rental and resale prices.

Feature 03 · Math as permission

Value calculator

3 year total cost of ownership with a visible break-even day, so Hesitant Outsiders get permission to buy.

Feature 04 · 7 year silence

Product breadth

Boards and boots, then helmets, then wax and tuning tools, with off-season reminders that keep the relationship alive.

Design Feedback

One mentor comment flipped the plugin.

Our first plugin opened with a drawer of "better" boards. It felt helpful to us. It ignored the board the user was actually looking at.

First plugin version: a list of similar boards shown before any judgment of the current board
First version. Alternatives first, the board on screen ignored.

"I would have expected it to say: this is a good buy, but it's not the best match for your skill level. That way it stays contextual."

Jason Levine, AWS UX Lead · March 23, 2026
What I changed
  • Recommendations first→Current board first
  • "Here are better options"→"Let me help you judge this one"
  • Interrupts with a pitch→Respects the user's own research
Refined version. "Not a match for your level" with reasons first, then better matches, then a full AI chat.

Contextual beats convenient. Six interviews didn't show us our own assumption. An outside eye did in one sentence.

Process

I started this project not knowing how to code.

Figma couldn't show an AI reasoning in real time. So we had to build the real thing.

  1. Weeks 1 to 2

    Research, then a Figma reality check

    Interviews and personas done. Then mockups hit a wall: they can't show reasoning or a live conversation. Jason pointed us to Kiro, which meant learning TypeScript.

  2. Weeks 3 to 5

    Kiro + TypeScript: prove the logic

    Conditional rules for anti-sycophancy, source ranking, and assessment before preference. The logic worked. The generated UI was too rigid.

  3. Weeks 6 to 8

    Pivot to Claude + HTML

    Full visual control again. A survey with real Claude API calls, a live dashboard, and the plugin, all from scratch.

  4. Weeks 9 to 10

    Ship the demo

    Files got too big, so we split them. Debugging JavaScript became a daily ritual. We shipped a recordable demo with scripted answers for reliable presenting.

Five tools, one workflow

1

Figma

Design system + first mockups

2

Figma Make

Plugin flows + demo scripts

3

Kiro

AI logic, proved in TypeScript

4

Vite.js

First React demo

5

Claude

Final build with real API

Kiro editor showing steering files: behavior_logic, financial_logic, product_breadth, tech.md
Kiro. Steering files that define how the AI behaves.
Survey step built with Claude: optional riding details form
Claude build. An optional details step, coded in HTML/CSS/JS.

Good rules survive tool changes. The same behavior logic ran in TypeScript and plain JavaScript.

Under the Hood

Write the AI's rulebook first. Then make the code obey it.

A neutral advisor isn't just a UX problem. The rules have to run. Before any UI, I wrote the AI's behavior as Markdown specs in Kiro, then turned each rule into code.

Claude API (Sonnet 3.5)React + TypeScriptVite.jsKiroStackBlitzChrome Extension API

structure.md + tech.md

The map

Folder setup and tech choices, so every builder, human or AI, works from the same plan.

behavior_logic.md

The AI's personality

It must show honest cons. It must cite sources. It can't recommend gear above your skill level, no matter what you prefer.

financial_logic.md
/* 3-year value calculator
   Anti-salesmanship rule: never hide
   maintenance or depreciation. */

rental = $R × days × 3
own    = $P + ($75/yr upkeep)
         − (18% depreciation × 3)

// "Aha Day" = the day owning wins.
// If renting is smarter, say so.
ProblemClaude API answers took 2 to 5 seconds.FixTyping indicators plus preloaded common questions.
ProblemOne HTML file passed 10MB with images.FixSplit survey and dashboard, bridged with an iframe.
ProblemAnswers got lost between pages.FixlocalStorage carries the survey into results.
financial_logic.md in Kiro defining the break-even algorithm
financial_logic.md. The full spec behind the calculator, written before any UI.

The three rules, in code

Anti-sycophancy guardNo unsafe gear for your level, even if you ask.if (gear.skill > user.skill) return REFUSE + redirect()
Truth source hierarchySources ranked by authority.["PSIA-AASI", "OutdoorGearLab", "Reddit"]
Assessment firstSkill filters run before style filters.filter_by_skill() .then(filter_by_style)
StackBlitz project with React and TypeScript interfaces for equipment specs
StackBlitz. Spec rules became TypeScript types like flex: number.
Impact

A working AI agent, and a framework that travels.

The prototype ran on real API calls. The bigger outcome was a repeatable way to design how an AI behaves, not just how it looks.

Behavior framework

Anti-sycophancy, assessment vs. preference, and truth sources. Reusable for any high-stakes purchase.

Visible reasoning

A pattern that shows how the AI reached its answer. That visibility is what builds trust.

A retention model

Neutral broker plus Tier 3 consumables keeps users around through the 7 year gap.

If we kept going

Reflection

What I'd take into my next AI product.

Design behavior, not just screens

AI design means defining its personality, its limits, and how it reasons. A chat box isn't a strategy.

Tools serve the goal

When Kiro boxed us in, we switched. Prototypes exist to test ideas, not to be perfect.

Trust is the currency

For big, rare purchases, conversion tricks fail. People want an advisor, not a sales machine.