Museum of Fantasy Sports
A league history platform that treats a fantasy league’s past as an archive worth keeping.
My roleSolo, design and build
- Next.js
- React.js
- TypeScript
- PostgreSQL
- Prisma
- Auth.js
- Tailwind CSS
Aspiring UI/UX designer with a background in computer science and psychology
B.S. Computer Science · B.S. Psychology, University of Central Florida
Jun 2026 to Present
UI/UX Intern · LocalFiber
Feb 2025 to Feb 2026
Research Assistant · University of Central Florida
May 2025 to Dec 2025
Teaching Assistant · University of Central Florida
May 2024 to Jan 2026
JD Sports Associate · JD Sports
Summer 2026
University of Central Florida
Spring 2024 to Summer 2026
UCF Psi Chi
A league history platform that treats a fantasy league’s past as an archive worth keeping.
Solo, design and build
Next.js · React.js · TypeScript · PostgreSQL · Prisma · Auth.js · Tailwind CSS
A wishlist that says why, and a claim system that stops duplicate gifts without spoiling the surprise.
Solo, design and build
Next.js · React.js · TypeScript · Tailwind CSS · SQLite · Playwright
A Japanese learning app built around flashcards, writing practice and a companion that lives on your home screen.
Interface and interaction work: the app’s theming system, its move to NativeWind, the home screen, the Mahou companion screen, the memory minigame, and the settings and cards screens.
React Native · Expo · TypeScript · NativeWind · SQLite · Reanimated · Skia
A social space for rating and ranking albums: designed in Figma, then built by the five of us.
Team lead, design and build
Figma · React.js · TypeScript · Tailwind CSS · Node.js · Express · MongoDB · Spotify Web API
A sports card portfolio tracker: what a collection holds, and what it is worth.
Solo, design and build
Next.js · React.js · TypeScript · PostgreSQL · Prisma · Auth.js · Tailwind CSS
A static site written by hand, with no framework and no build step to speak of.
Solo, design and build
HTML · CSS · JavaScript (ES modules) · Node.js · Netlify
I studied psychology and computer science because I care about both sides of technology: the people using it, and the systems being built.
Currently building Museum of Fantasy SportsWishwellCardhouseThis Portfolio
What I am working on01
What is open on this machine right now. Status is where each one honestly stands, not a percentage.
A league history platform that treats a fantasy league’s past as an archive worth keeping.
Deployed at /fantasy · real league import waiting on credentials
Read the case study
A wishlist that says why, and a claim system that stops duplicate gifts without spoiling the surprise.
Source on GitHub · runs locally, not deployed yet
Read the case study
A sports card portfolio tracker: what a collection holds, and what it is worth.
Private repository · no public link yet
Read the case study
A static site written by hand, with no framework and no build step to speak of.
huntermshaps.com · revised continuously
Read the case study
02
Each one opens into a case study: the problem, the build, the decisions and where it actually stands.
A league history platform that treats a fantasy league’s past as an archive worth keeping.
My roleSolo, design and build
A wishlist that says why, and a claim system that stops duplicate gifts without spoiling the surprise.
My roleSolo, design and build
A Japanese learning app built around flashcards, writing practice and a companion that lives on your home screen.
My roleInterface and interaction work: the app’s theming system, its move to NativeWind, the home screen, the Mahou companion screen, the memory minigame, and the settings and cards screens.
A social space for rating and ranking albums: designed in Figma, then built by the five of us.
My roleTeam lead, design and build
Everything else lives in the archive.
03
Study, work and projects on one line. Every date here comes off the résumé or a repository's history.
04
Grouped, and pointed at the projects that actually use them. A tool with nothing next to it is one I have used, but not on anything published here.
05
People bring expectations, habits and goals to technology. Software brings structure, possibility and constraints. I am interested in where those meet.
Psychology How people learn, make sense of choices, and form expectations around an experience.
Mahou Learning sits inside this question: the difference between a lesson someone finishes and one they come back to.
I am interested in the exact moment a system stops feeling arbitrary and starts making sense, and in what an interface did to get someone there.
A question about technology, behaviour, and responsibility, and about who is expected to do the adapting.
Plenty of interfaces work. Fewer of them tell you what just happened, what will happen next, and what to do if you were wrong.
06
Earlier versions, kept rather than deleted. Each screenshot is a render of that actual commit.
17 August 2026 66c6d28
The version this redesign replaced. Editorial layout, a fixed index rail, and three case studies on one page.
4 August 2026 c701a28
The first version published to huntermshaps.com. Same bones, before the contrast pass and before the museum existed.
08
If you are thinking about people, technology, or a project where the two meet, I would love to hear from you.
Nothing matches that. Try a project name, or “résumé”.