Prism

The problem

Most motion-heavy component libraries pull in an animation framework and a styling runtime. I wanted interaction and motion that feel physical, components a team can drop in without adding dependencies, and documentation that shows each piece working.

What I did

• •Designed and built 22 components and 5 experimental playgrounds, all reacting to the cursor
• •Wrote the spring physics by hand on requestAnimationFrame instead of using a motion library
• •Kept the runtime dependency count at zero and published it under MIT
• •Built a live documentation site where every component can be tried in place
• •Set up an automated daily build-and-publish pipeline for new components

What it shows

• •Design systems work that holds up in code, not just in Figma
• •Interaction and motion design with attention to performance
• •Writing components other engineers can adopt without friction