tqwewe contributor

Umari

Guide Claude to scaffold and implement Umari event-sourcing modules—commands, projectors, effects—with correct DCB, folds, and idempotent side-effect patterns.

Overview

umari is a plugin marketplace for the Build phase that teaches Claude to author Umari event-sourcing modules with DCB, folds, and idempotent effect patterns plus CLI scaffolding.

What is this marketplace?

  • Single-plugin marketplace (umari v0.1.0) for the Umari event-sourcing runtime
  • Teaches commands, projectors, effects, DCB, and fold mechanics
  • Documents fold-check → side effect → record idempotency pattern
  • Covers `umari` CLI scaffolding for new modules
  • Tagged for event-sourcing, Rust, WASM, and DCB in marketplace metadata
  • Marketplace bundles 1 plugin (umari v0.1.0)
  • Marketplace metadata version 0.1.0
  • Plugin tags include event-sourcing, rust, wasm, dcb

Compatible agents: Claude Code, Cursor, Codex

Community signal: 3 GitHub stars.

What problem does it solve?

Solo builders on Umari waste cycles when Claude generates incorrect folds, projectors, or non-idempotent side effects in event-sourced Rust/WASM code.

Who is it for?

Indie backend developers committed to the Umari event-sourcing stack who want agent-assisted module generation without semantic bugs in folds or effects.

Skip if: Builders not using Umari or event sourcing, or teams wanting generic REST CRUD scaffolding without DCB and projector discipline.

What do I get? / Deliverables

After installing the umari plugin, Claude follows Umari conventions for modules, idempotency, and `umari` CLI scaffolding so backend pieces compile into the runtime model.

  • Installed umari marketplace plugin (v0.1.0)
  • Umari modules (commands, projectors, effects) aligned with fold and idempotency rules
  • CLI-scaffolded structure consistent with Umari conventions

Plugins in this marketplace

1 plugin — install individually after you add the marketplace.

Recommended Marketplaces

Journey fit

Umari marketplace targets backend implementation of event-sourced modules during Build, not validation landing pages or launch SEO. Backend subphase fits Rust/WASM Umari runtime work: folds, projectors, effects, and CLI scaffolding rather than UI polish.

How it compares

Domain-specific Umari/Rust event-sourcing framework plugin marketplace, not a general frontend or DevOps deploy pack.

Common Questions / FAQ

Who is Umari for?

Umari is for developers building on the Umari event-sourcing runtime who want Claude Code to respect DCB, folds, projectors, effects, and CLI scaffolding rules.

When should I use Umari?

Use Umari during Build backend work when you are adding or changing Umari modules and need correct fold-check, side effect, and record idempotency patterns.

How do I add Umari to my agent?

Register the tqwewe/Umari marketplace in Claude Code, install the Umari plugin, ensure Rust/WASM and the `Umari` CLI are set up in your repo, then prompt Claude to generate commands, projectors, or effects per the plugin guidance.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.