Why SnipKit exists
A few months ago I needed a quick CSS clamp() calculator for a responsive type scale. I opened the first result on Google. Before I could see the tool I had to dismiss a cookie banner, close a newsletter pop-up, scroll past three banner ads, and then create an account — because the actual calculator was behind a “Pro” tier. I closed the tab and built my own in a single evening.
That clamp calculator is still on this site. I built it because I needed it. Then I built nineteen more for the same reason. SnipKit now has 28+ tools across CSS, layout, color, code, and WordPress, and every single one of them is and always will be free, account-free, and ad-light. There is no premium tier. There is no premium tier coming.
What makes it different
- No accounts, ever.Open the site, use the tool, close the tab. No sign-up flow exists, even for “premium features,” because there are no premium features.
- Tools that run in your browser.Almost every SnipKit tool runs entirely client-side. The colors you pick, the regex you test, the JSON you paste — none of it is transmitted to a server. The site as a whole uses standard privacy-respecting analytics so we know which tools people actually use, but the tools themselves don't phone home.
- Honest scope.Each tool does one thing. No do-everything mega-generators, no bloat, no “AI-powered color picker” buzzword features bolted onto things that don't need AI.
- Built in public.Every tool, every weird CSS bug, every refactor — written up on the blog. The site is the portfolio.
Who built it
I'm Jeremiah Ruanes. I build dev tools, write about web development, and ship side projects. SnipKit is the latest one — it started as a private folder of utilities I kept rebuilding from scratch every time I switched machines, and eventually I figured the answer was to put it on the public internet.
When I'm not shipping SnipKit tools I'm writing about whatever weird thing I learned that week, or building something else.
The stack
SnipKit runs on Next.js 16 with React 19, TypeScript, and Tailwind 4. The component primitives come from shadcn/ui on top of Base UI. Blog content is stored as markdown in Postgres via Prisma, the admin panel is gated by Clerk, and everything is deployed on Vercel. We use Vercel Web Analytics for aggregate page views (cookieless, no individual tracking) and Vercel Speed Insights for real-user performance metrics. Display advertising and affiliate links may appear on the site as part of how SnipKit pays its hosting bill — we'll always disclose what's running in the privacy policy.
How to support it
- Use the tools and tell other devs about them.
- Share feedback if something's broken or could be better — email jeremiah@meraki8.io.
That's the whole pitch. The tools are the thing.