Taste that ships as installable code

Problem

Teams that care how their product looks must ship that look in code. Every existing path forces a compromise: shadcn/Tailwind is structurally sound but visually anonymous; viral effect libraries look identical across thousands of sites; Figma Community files never ship; building in-house costs engineer-days nobody authorizes for 'the background.'

The gap isn't a shortage of images. Taste does not currently ship as code.

Process

I defined Frameline as a commercial surface & materials system: typed React components, token-bound, production-safe, with a live configurator and plain-language licensing.

Discovery Phase 01 focused on Gate 01 evidence — waitlist, willingness-to-pay, and install intent — before locking commerce architecture.

The catalog includes screen templates (e.g. Softwave hero and feature cards) that demonstrate how materials compose into real product surfaces, not isolated demos.

Built with Next.js App Router, WebGL shaders, and a solo-operable publishing pipeline so each new material ships in hours, not days.

Outcome

Live product at frameline.ai with a growing material catalog, configurator, and discovery instrumentation in place.

Frameline doubles as portfolio proof: I own the full narrative from problem definition through shipped code.

What I'd do differently

Publish fewer materials earlier with stronger before/after case studies — buyers need to see transformation on a real app shell, not just the material in isolation.