ks Kaide Salo
Software Engineer
Independent mind, Engineering mindset. Open to interesting conversations

Good ideas.
Great Engineering.

Explore My Work

I'm Kaide, a software engineer turning
complex problems into intuitive digital experiences.

SCROLL TO EXPLORE
01 / Thought, built, shipped.

Selected Works.

Collection of current and future projects
Built with intention Made for people Built with intention Made for people
Project 01 / 03

Personal project · Web

Spellbranch

A web app for building Magic: The Gathering decks with friends: search cards, fork a deck into branches, and compare every change.

Screenshot of Spellbranch’s deck page: the Gruul Stompy deck with tags, a branch link, a Scryfall card search for Embercleave with a card preview and Add card button, and the deck list grouped by card type with quantity controls

Screenshot · Deck page

Screenshot of the Spellbranch landing page: the headline ‘Build decks with friends. Fork ideas. Compare every change.’ beside a branch view panel listing card changes
Landing page
Screenshot of Spellbranch’s compare view: the Gruul Stompy source list beside a friend’s branch, with added, removed, quantity, and replaced card counts and a table of card changes
Branch compare
Screenshot of the Spellbranch dashboard with deck, branch, and friend counts and two deck cards, Boros Burn and Gruul Stompy
Dashboard
Two mobile screenshots of Spellbranch side by side: the dashboard and the branch compare view
Mobile

Role

Solo designer/developer

Stack

Next.js, React, TypeScript, Tailwind CSS, shadcn/ui; Scryfall API; local data store for now, with a Supabase schema ready for hosted auth and data

Status

In progress

Overview

Spellbranch is a Magic: The Gathering deck builder I’ve been meaning to ship for a while. It started as a card-sorting page and grew into a place to build decks with friends: search cards, put a list together, and share it publicly or with friends only.

The core idea is branching. A friend can fork your deck and try their own cuts, then you compare the branch against the source side by side, with added, removed, and replaced cards called out, so game-night experiments never overwrite the original list. Friends can also leave comments on a deck or a branch. Card search and card data come from the Scryfall API. For now the app runs on a local data store, with a Supabase schema (including row-level security policies) ready for hosted auth and data.

I’m building it as a personal portfolio piece and a daily driver for my own decks. The repo is private for now while I finish the first public version.

Next

  • Polish empty, loading, and error states plus the mobile layout
  • Deploy a live demo
  • Make the repo public once the first version is ready

Screenshots are from a local development build using demo accounts. The repo is private for now, and a live demo is coming soon.
Project 02 / 03

Client project · Booking platform · Web

Clean Slate

A booking platform for a cleaning service: customers book as guests and only see times the team can actually staff, while staff run the schedule from a private dashboard.

Screenshot of Clean Slate’s booking flow on the Time step: the step indicator (Service, Property, Price, Time, Contact, Review), a Deep Cleaning estimate of $335 for 4 hours, and open appointment slots grouped by day with 10:00 AM selected

Screenshot · Booking: available times

Screenshot of the Clean Slate landing page: the headline ‘Book a spotless home on your schedule.’ with Book a cleaning and Manage appointment buttons
Landing page
Screenshot of the Clean Slate booking confirmation: ‘You’re booked’ with a management code for rescheduling or cancelling, and Manage appointment and Book another buttons
Booking confirmation
Screenshot of the Clean Slate staff dashboard: counts for today’s appointments, this week, pending quotes, and active employees, with upcoming jobs, pending quotes, and recent cancellations
Staff dashboard
Two mobile screenshots of Clean Slate side by side: the available-times booking step and the staff dashboard
Mobile

Role

Designer & developer (client project)

Stack

React 19, TypeScript, Vite 8, Tailwind CSS 4, React Router 7, date-fns; Vitest and Oxlint; a local demo data store for now, with a Supabase schema (Postgres, Auth, row-level security) and the supabase-js client included; Google Calendar, Resend, and Twilio adapters that run as mocks until configured

Data model

Ten Postgres tables in the Supabase migration: business users, employees, services, customers, appointments, quote requests, weekly employee availability, availability exceptions, notification logs, and business settings. Status enums track appointments and quotes, every table has row-level security turned on, and a GiST exclusion constraint stops one employee from holding two overlapping active appointments.

Status

In progress

Overview

Clean Slate is a booking platform for a cleaning service. Customers book as guests through a step-by-step flow (service, property, estimate or quote, schedule, contact, and review) and receive a management code they can use later to reschedule or cancel. Staff work from a private dashboard with appointments, a day/week/month calendar, employees, availability, services and pricing, and quote approvals.

Scheduling reliability is the core of the product. Available times are computed from business hours, employee schedules, appointment length, blocked time, and calendar busy periods, and each booking re-checks its slot before it’s saved so the same time can’t be double-booked. When the pricing rules can’t produce a confident estimate, the request becomes a custom quote instead.

The MVP runs on a local demo data store, with the Supabase schema, row-level security policies, and Vitest coverage for availability, pricing, and the booking lifecycle already in place. Calendar, email, and SMS integrations go through adapters that log mock output until real credentials are connected.

Next

  • Move guest booking writes to Supabase server-side functions
  • Connect Google Calendar, Resend, and Twilio through a server proxy
  • Roadmap: Stripe deposits and automated appointment reminders

Screenshots are from a local development build using the demo data store and sample customers. The repo is private.
Project 03 / 03

Fintech · Concept

Kitbook

A personal finance tracker concept that turns everyday spending into a clear, friendly picture of where your money goes, with a small origami fox keeping watch.

Concept mockup of the Kitbook dashboard with a total balance, spending-by-category donut chart, monthly budget bar, recent transactions, and an origami fox beside a savings goal; all figures are sample data

Concept image

Stack

React, TypeScript, D3.js, Node.js, PostgreSQL (concept stack)

Status

Concept (design mockup; all figures are sample data)

Overview

Budgeting tools tend to either bury people in spreadsheets or nag them with alerts. Kitbook explores how one calm overview (a balance, a monthly budget, spending by category, and a savings goal) can make money feel manageable instead of stressful.

Approach

  • A one-screen overview that answers the everyday questions first: how much is left, where it went, and whether a goal is on track.
  • Charts built with D3 and paired with plain-text labels and totals, so no figure is conveyed by color alone.
  • A typed data model for accounts, transactions, and budgets in PostgreSQL, shaped for fast monthly roll-ups.

Focus

Data Visualization · Product Design · Accessibility

Kitbook is a concept project. The dashboard above is a design mockup, and every figure in it is sample data.