Petrichor, a music player for macOS: https://petrichor.page/

This has been my work outside of work, which I spend most of my weekends on. It has gotten enough downloads (23k+) and traction to motivate me to continue.

I’ve been working on a Postgres extension for running local LLM inference “inside” Postgres (inference runs in a background worker, while Postgres stores the jobs, inputs, outputs, and receipts)

https://github.com/joshmeek/otlet

I am working on a framework that allows creating very complex SaaS products with AI, that actually work. Very complex = +100k LOC of one-shotted AI-generated code. Codename o2p - outcome-to-proof.

It is a research-first method for designing or reviewing SaaS products. Its central question is: What customer outcome matters, and what evidence proves that the product delivers it?

Idea or existing product → Research real customers and current work → Identify their Jobs to Be Done → Design the minimum safe workflow, define the interface and system behavior (with a sophisticated scoring system) → Validate the workflow → Implement vertical slices → Observe proof of customer progress

A lot of Claude plugins.

https://github.com/mrieck/demoday-claude-plugin - create demo videos for your projects using Claude

https://github.com/mrieck/overboard-plugin - CTO assistant, PM helper Claude plugin

https://plugmyplugin.com - Weekly voting contest and directory for Claude Plugins similar to Devhunt/ProductHunt

I've always ran into an issue running arbitrary processes - whether it be for serious production work, or just toy scripts. So many choices with so many dependencies, featuring so many foot-guns. So I decided to take a stab at solving the problem. Would love any feedback or contributors :)

SystemG - An agent-friendly general process composer.

- https://sysg.dev/

- https://github.com/ra0x3/systemg

- https://docs.rs/systemg/latest/systemg/

A modern issue tracker enabling replay for agentic workflows (via board time-travel) and focus on ergonomics (native to the terminal).

https://ljtn.github.io/epiq/

I've been having fun building out a link-in-bio tool / micro-site builder in my spare time. It started out as just something that a solo-dev could build without a lot of experience... but it's turned out to be more complicated and interesting than I thought! Right now I'm working on getting embeds and other 'fancier' types of blocks built out. Also… if any SEO wizards are lurking, I would love tips on getting more Google impressions/CTR, lol. If you want to check it out (would love some feedback!):

https://soc.bio

Interesting to see the distribution of projects here. For people building something with the intention of eventually making it a business: what was the strongest evidence that the problem was worth pursuing before you started building? I'm especially interested in cases where the initial idea changed substantially after talking to users.

I am in the final stages of preparing to ship a 2.0 version of a fairly successful app, that has been shipping for a couple of years.

This is a complete, bottom-to-top rewrite (front- and backend). It's a huge improvement. I used an LLM, quite a bit. It's been a big help.

We're in the last stages of the first-wave testers. This is the one that affects the app UI. After this, we expand the test, and do bug fixes only.

Also, we need to start taking screenshots and app previews for the App Store. That requires setting up a test server, with anonymized (fake) users, so we don't compromise actual user anonymity. It's a bit of a pain, but it has to be done.

I’m working on “Supabase for science”: 1-click deploy of scientific databases with validation, transformation, MCP, export-for-ML, and provenance built in.

https://amacrin.com