I'm proud to present this weekend's side-project, https://www.splintiers.com/ :)
On Splintiers, you'll fine Tier lists for every edition in 
TIER LISTS
The Tier Lists are organized by edition, though I've taken the liberty to combine a few where it makes sense (e.g. rewards and promos are included within core sets, but I've split out the larger mini-sets). You can click on a card to see its full stats.
Each tier ranking comes from me based on my own experience, and if you disagree with a feel free to let me know why.
On the tier lists, you can use the buttons at the top to filter by rarity so you only see Common, Rare, Epic, or Legendary cards (or a mix if you prefer).
DECK BUILDER
In addition to the tier lists, I created what I'm calling a "deck builder". I've often gotten questions like "what cards should I buy & what will it cost?". The deck builder lets a player select editions (e.g. Conclave Arcana), tiers (e.g. S/A), and level (e.g. Diamond+) and it will show the current cost to buy those cards on the market.
It also highlights several things:
- When there isn't enough BCX on the market to buy a full card
- When the cheapest version is either a Gold Foil or a Black Foil
- When a price is a massive outlier (usually due to a thin market)
Outliers (not enough BCX or price outlier) can be filtered out as well. And for good measure, you can even export to CSV.
BACKOFFICE
To help me manage the tier lists, I built a backoffice which uses Hive authentication and is restricted to only a specific account I designated (brave.sps).
The backoffice has a drag & drop interface that makes it easy for me to swap around tiers, and allows me to tag roles and add notes to cards to justify their tiers (I'll be doing this in the future, right now they're empty).
VIBE CODING - QUICK START GUIDE
This project took me about 7-8 hours and I was able to complete it in one weekend, all thanks to Vibe Coding with Claude Code. The majority of the time was spent defining clear specs to Claude Code to ensure it could one-shot most features. Besides that, there's a decent amount of waiting time when it's building some of the more complex parts, and I have a perfect way to spend that downtime: playing Splinterlands ;)
If you want to get started vibecoding with Claude Code here's a simple bullet point list of what you need to do:
- Go to https://claude.ai/ and sign up for the Pro plan (this is necessary in order to use Claude Code).
- You can use Claude Code on your desktop (in their app or in the Terminal) but the easiest way to use it is in the browser (zero installations required) here: https://claude.ai/code/.
- Create a github account on https://github.com/ and then connect it to Claude Code. If you can't figure out how to do this, just ask Claude to guide you through it (Hint: this is true about every step). Github is where your code will live.
- Next, create an account on Vercel (https://vercel.com/). This is where your website will get deployed (i.e. where it's hosted). Vercel makes it really easy to manage deployments and basically run your website. Once you have it, connect Vercel to Github. Again, Claude can guide you on how to do that.
- Now you're ready to start working on something. First, come up with an idea and go back & forth with Claude (not Claude Code) to spec it out. THIS STEP IS IMPORTANT. Don't just ask Claude to figure everything out. You need to be CLEAR on what end result you want. Claude will help you by asking questions to help firm up the details, can help mock things up, and can come up with all the technical requirements, but YOU must be clear on what output you want. Spend at least 30 minutes to an hour discussing the idea with Claude, and once it's clear enough you can ask Claude for a spec and for the specific prompts you need to provide to Claude. You should also ask Claude to create a "CLAUDE.md" file which will contain the overall product spec and guidelines (think of this as an evergreen architecture document Claude Code will have access to).
- Once you have your spec, start by creating a repository (aka repo) in Github, and then going to Vercel and importing that project from Github. Then, go to Claude Code (https://claude.ai/code/) and start a new session and select the repo you created in Github. Then put in your first prompt and let Claude work.
- Once Claude Code's done working, you go to Github and merge the "pull request" (aka PR). If you don't know what that means, just ask Claude and it'll guide you through. You basically click a few green buttons. This moves the work Claude Code did from a "side branch" to your "main branch". In a nutshell, this is to prevent bad code from going to production. For now, don't worry about it, just merge the PR.
- Now go to Vercel and go into the project that's synced up to your Github repo. Go into deployments and you should see a deployment to your production environment. Click on that and click the "visit" button to see your live website.
Bonus items:
- If your service needs a database, I recommend using Supabase. Totally doable and Claude's great with DB work.
- If your service require authentication (e.g. Google Login) you'll also need something like Supabase. If it's HIVE login Claude Code can figure that out and doesn't need Supabase.
- If you want a custom domain, you can get that straight inside Vercel.
- I recommend having 2 windows open at all times when working with Claude; one that's talking to Claude and one that's talking to Claude Code. Think of Claude as your planner / adviser / consultant. Anything you don't understand, you ask it. All planning, specs, mockups, go to him. If Claude Code does something you don't understand, ask Claude about it. He's not a coder, and won't accidentally do code for you. Claude Code, meanwhile, is your developer. You give him clear instructions once you've sorted those out with Claude.
- In terms of model selection, Claude has a terrific base model (Sonnet) which should handle most of what you need (everything I built above used Sonnet). IF you're building something super complex, you can always go up to Opus, BUT that will consume credits MUCH faster. Your credit usage is capped based on your plan (i.e. you never spend more than $20/mo UNLESS you change your settings to allow overage spend). It's capped per 5 hour time block and per week. Building Splintiers cost roughly 35% of my weekly usage cap.
If you have questions or comments about Splintiers, suggested improvements, or any questions about vibe coding, feel free to drop them in the comments.