Show HN: I vibecoded 177 tools for my own use (CalcBin)

Show HN (score: 5)
Found: February 11, 2026
ID: 3284

Description

Other
Show HN: I vibecoded 177 tools for my own use (CalcBin) Hey HN! I've been building random tools whenever I needed them over the past few months, and now I have 177 of them. Started because I was tired of sketchy converter sites with 10 ads, so I just... made my own.

Some highlights for the dev crowd:

Developer tools: - UUID Generator (v1/v4/v7, bulk generation): https://calcbin.com/tools/uuid-generator - JWT Generator & Decoder: https://calcbin.com/tools/jwt-generator - JSON Formatter/Validator: https://calcbin.com/tools/json-formatter - Cron Expression Generator (with natural language): https://calcbin.com/tools/cron-expression-generator - Base64 Encoder/Decoder: https://calcbin.com/tools/base64 - Regex Tester: https://calcbin.com/tools/regex-tester - SVG Optimizer (SVGO-powered, client-side): https://calcbin.com/tools/svg-optimizer

Fun ones: - Random Name Picker (spin wheel animation): https://calcbin.com/tools/random-name-picker - QR Code Generator: https://calcbin.com/tools/qr-code-generator

Everything runs client-side (Next.js + React), no ads, no tracking, works offline. Built it for myself but figured others might find it useful.

Browse all tools: https://calcbin.com/tools

Tech: Next.js 14 App Router, TypeScript, Tailwind, Turborepo monorepo.

All open to feedback!

More from Show

Show HN: GitClaw โ€“ An AI assistant that runs in GitHub Actions

Show HN: GitClaw โ€“ An AI assistant that runs in GitHub Actions

Show HN: Accept-md โ€“ One command to make Next.js sites LLM-scraping friendly

Show HN: Accept-md โ€“ One command to make Next.js sites LLM-scraping friendly I recently saw a post from the Vercel CEO pointing out that LLMs understand websites much better when they can request:<p>`Accept: text&#x2F;markdown`<p>Most websites today are built for humans. When AI agents try to consume them, they get complex HTML instead of clean, structured content.<p>So I built *accept-md* โ€“ a simple open-source package for Next.js that helps solve this.<p>Getting started is intentionally minimal:<p>``` npx accept-md init ```<p>After that, your existing Next.js routes can automatically respond with Markdown whenever an AI agent (or any client) requests it. No redesigns, no CMS changes, and no duplicate pages to maintain.<p>Right now the project is:<p>* Focused only on Next.js * Middleware-based and lightweight * Designed to work with existing apps * A small step toward more AI-friendly websites<p>This is an early experiment, but I think the idea itself matters as AI agents become first-class consumers of the web.<p>Iโ€™ve open-sourced it and would love help with:<p>* Better markdown extraction * Edge cases across Next.js setups * Performance and caching * Tests and examples * Documentation * Eventually adapters for other frameworks<p>Would love feedback from the HN community on the approach โ€“ and whether `Accept: text&#x2F;markdown` feels like a pattern worth standardizing for the AI-native web.

Show HN: Buquet โ€“ Durable queues and workflows using only S3

Show HN: Buquet โ€“ Durable queues and workflows using only S3 buquet (bucket queue) is a queue and workflow orchestration tool using only S3-compatible* object storage. S3 is the control plane making it much simpler than alternatives. This does come with tradeoffs (see docs), but I do believe there is a niche it can serve well.<p><a href="https:&#x2F;&#x2F;horv.co&#x2F;buquet.html" rel="nofollow">https:&#x2F;&#x2F;horv.co&#x2F;buquet.html</a> <a href="https:&#x2F;&#x2F;github.com&#x2F;h0rv&#x2F;buquet" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;h0rv&#x2F;buquet</a><p>* see <a href="https:&#x2F;&#x2F;github.com&#x2F;h0rv&#x2F;buquet&#x2F;blob&#x2F;main&#x2F;docs&#x2F;guides&#x2F;s3-compatibility.md" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;h0rv&#x2F;buquet&#x2F;blob&#x2F;main&#x2F;docs&#x2F;guides&#x2F;s3-comp...</a>

Show HN: Pygantry โ€“ Why ship a whole OS when you just need a Python environment?

Show HN: Pygantry โ€“ Why ship a whole OS when you just need a Python environment? &quot;Hi Hacker News, Iโ€™ve always found Docker to be overkill for simple Python deployments. It&#x27;s heavy, complex for non-tech users, and often results in 500MB+ images for a 10KB script. Thatโ€™s why I built Pygantry. Itโ€™s a minimalist &#x27;container&#x27; engine based on Python venv but made portable and relocatable. Key features: Lightweight: A full &#x27;shipped&#x27; app is usually &lt; 20MB. Zero-Config: No daemon, no root, no Dockerfile complexity. Portable: Build once, zip it, and run it anywhere with a Python interpreter. Founder friendly: Built-in licensing and stealth modes for those building a business. I built this to simplify my own VPS deployments. I&#x27;d love to get your feedback on the architecture and how you handle &#x27;Docker-fatigue&#x27; in your workflow.

No other tools from this source yet.