Back to the shelf

037

Product Catalog Manager

The local tool that powers the products section you are browsing right now.

Building · Started April 2026 · Tool · Vibe-Coded

That's the whole thing.

The site's sound is off. The narration still plays.

This reading didn't load. The transcript is below.

Read the transcript

I had more than forty projects scattered across folders, no single view, no way to decide what to publish. That bothered me.

I built this. The Product Catalog Manager scans every vibe-coding folder and other product sources, surfaces them in one visual interface, and lets me toggle what goes live on this site. Edits write back to the source files directly. It powers the products section you're browsing right now.

Every folder also gets a paired label: markdown for agents, HTML for humans. Both stay in sync.

I started in April twenty twenty-six, vibe-coded with AI, built in Node and Express. Still building. If you're curating your own footprint, I hope this gives you an idea of what's possible.

Narrated in my own cloned voice, generated with ElevenLabs v4.

Forty projects scattered across folders is not a catalog. It is a pile.

I had no single view of everything I had built, and no way to choose what to publish without hunting through directories. The products section you are reading right now needed its own infrastructure. I built it.

Product Catalog Manager scans every vibe-coding folder and other product sources, shows them in one visual interface, and lets me toggle which projects publish to the site. Every edit writes back to the source files.

Every folder carries paired labels: a markdown file for agents and an HTML file for humans. Markdown works for agents; HTML works for humans. One tool, both audiences.

It is also where the catalog reference field comes from, the thread that connects the catalog to itself.

Started April 2026. Vibe-coded with AI, in Node, Express and Tailwind. Status: Building. It runs locally; there is no public link. You are looking at what it publishes.

The making

  • Node.js
  • Express
  • HTML
  • Tailwind CSS

01 · The problem

Before it existed

What hurt

More than forty projects sat in separate folders. There was no single view of what I had built and no way to choose what to publish.

Who uses it

  • Me, as the owner of every product
  • The agents that read each folder’s label

02 · The flow

4 steps, in the order they happen

  1. 01 / 04

    Scan the folders

    You
    Starts the tool
    It answers
    Reads every vibe-coding folder and the site reference into one catalog
  2. 02 / 04

    See everything at once

    You
    Opens the catalog in the browser
    It answers
    Shows every product in one visual interface
  3. 03 / 04

    Edit a product

    You
    Changes a field
    It answers
    Writes it back to the product’s source file and rebuilds its HTML label
  4. 04 / 04

    Publish to the site

    You
    Switches a product on and runs the sync
    It answers
    Records the choice and copies published products into this site

03 · What was special

What it stands on

  1. Two labels, one truth

    A markdown file serves agents and an HTML file serves people. Editing one regenerates the other.

  2. Edits write back

    Changes go into the source files, not in a copy, so the catalog and the folders cannot drift apart.

  3. Where the catalogue number began

    The catalog reference carried by every product started here.

Every folder carries one label for agents and one for people.