DEV Community

Cover image for Rotifer v0.6: Web Registry — Genes Go From CLI to Browser
Rotifer Protocol
Rotifer Protocol

Posted on • Originally published at rotifer.dev

Rotifer v0.6: Web Registry — Genes Go From CLI to Browser

#ai #opensource #devtools #webdev

Rotifer is a protocol where AI capabilities are treated as genes — they compete in arenas and evolve through natural selection. v0.6 makes these genes visible to the world.

The Problem: Invisible Genes

Before v0.6, genes existed only in the CLI. You could rotifer search and rotifer install, but there was no way to browse, compare, or evaluate genes without the terminal. The registry was a database with no storefront.

Gene Detail Pages

Every published gene now has a dedicated page at rotifer.dev/genes/[name]/:

  • README — full Markdown rendering of the gene's documentation
  • Phenotype — input/output JSON schemas displayed in a readable format
  • Arena History — fitness scores over time (when the gene has competed)
  • Metadata — version, author, domain, fidelity badge, download count
  • One-click install — copy rotifer install [name] to clipboard

Developer Profiles

Every developer gets a profile at rotifer.dev/developers/[username]/:

  • Reputation score: R(d) = weighted average of all published genes
  • Full gene listing with individual scores
  • Global ranking (#N / Total developers)

Cold Start: 51 Genes

A registry needs content. We used the Skill Import pipeline from v0.5 to convert 40 community AI skills into Rotifer genes, built 5 native WASM showcase genes, and added Genesis + Simulation genes. The registry launched with 51 genes across 20+ domains.

Search and Discovery

The gene listing page supports:

  • Full-text search on name and description
  • Domain filtering (coding, writing, analysis, creative, safety...)
  • Fidelity filtering (Wrapped / Native / Hybrid)
  • Sorting by reputation, download count, or recency

Architecture

The site is statically generated with Astro. At build time, it fetches all data from the Cloud Binding API (Supabase). A GitLab CI Pipeline Schedule triggers a rebuild every 6 hours to keep data fresh. Zero runtime servers — everything is served from Cloudflare Pages CDN.

Try It

Browse genes: rotifer.dev/genes

Install the CLI:

npm i -g @rotifer/playground@latest
rotifer search
Enter fullscreen mode Exit fullscreen mode

This article was originally published on rotifer.dev. Follow the project on GitLab or install the CLI: npm i -g @rotifer/playground.

Top comments (0)