how it works: you describe what you want, it generates ASCII art, shows you a mockup on an actual shirt, and you can check out right there.
pip install ascii-tee
ascii-tee "sunflower"
- CLI: Typer + Rich for the interactive flow (prompts, spinners, panels)
- ASCII generation: Claude API, with a system prompt tuned for a 40×30 character canvas that prints well
- Preview: Pillow composites the ASCII (rendered with JetBrains Mono) onto a shirt mockup template
- Terminal images: Detects iTerm2/Kitty/WezTerm for native inline images, falls back to timg or chafa, then browser
- Backend: Cloudflare Workers handling API calls
- Checkout: Stripe, with the preview image shown on the payment page
- Fulfillment: Printful prints and ships (Bella+Canvas 3001)
I built an app called SingTogether because I was tired of trying to get my bandmates to install complex DAWs just to practice over a demo. I wanted something that works instantly in the browser.
It’s designed to help bands and choirs practice and collaborate using their own multitracks.
The Main Use Cases:
1. Rehearsing a Song
The Problem: Sending MP3s back and forth is messy, and you can't isolate instruments.
The Solution: The band leader uploads multitracks to the app and sends a link. The team opens it (on phone or desktop) and can practice using standard tools like solo, mute, pan, and volume faders to isolate their specific part.
2. Asynchronous Jamming
The Problem: We want to experiment with ideas but can't meet up.
The Solution: A band member adds a base track (instrumental or vocal). They send the invite link, and other members can record a vocal or instrumental part straight from the browser. Everyone can listen to the layered contributions immediately.
I'd love for you to try it out and let me know what features would make your practice sessions easier.
Hive is designed to manage mixed environments (native processes, containers, whatever) through a single YAML config with built-in reverse proxy and zero-downtime deploys.
Key ideas:
- Everything is a plugin (runners, env providers, health checks, log handlers) - Plugins auto-install on first use - Blue-green deployments built into the spec - Native support for secrets (1Password, Vault, dotenv) - Think docker-compose but runner-agnostic with traffic management
Example: define a service with script runner, 1password secrets, blue-green rollout on ports 8080/8081, reverse proxy at /api, and http health checks. Run "adi hive up" and it handles the rest.
This is just the spec – not built yet. Sharing to get feedback before implementation.
Spec: https://github.com/adi-family/cli/blob/main/.adi/docs/hive-yaml.md
Side question: Are there funds/accelerators that invest in open-source dev tools? I've been self-funding my projects but curious if there's a sustainable path while keeping things open.
Still dealing with a tail of bugs, some of which look like overzealous optimizations leading to loss of pointer capability (leading to a filc panic). But it works well enough that I can say "hi" on here.