Workloom
Developer platform
A package manager and desired-state control plane for AI coding-assistant configuration across an organization.

The challenge
Every AI coding assistant an org uses — Claude Code, Codex, Copilot, Gemini, Cursor — has its own config format and file locations, and those configs get copy-pasted between repos with no versioning, no review, and no drift detection. As the brief put it: “the pre-npm era of AI configuration, getting worse every week.”
“Bring version control, review, and drift detection to AI-assistant configuration across an entire organization.”
The approach
- 01
Modeled the system as “npm + Git objects + Terraform plan/apply + provider renderers + CI drift detection,” purpose-built for AI config.
- 02
Let teams author canonical packages of instructions and skills, then pin versions to repos through workspace manifests.
- 03
Rendered provider-specific files deterministically so each tool gets exactly the config it expects — semantics live in the renderer, not a dumb file sync.
- 04
Added sync to detect and resolve drift, governed by trust gates and audit logs for team and enterprise use.
Design iteration
A single design system that evolved in place
Workloom deliberately avoided competing prototypes in favor of one design system that matured over time — captured in a generated design spec with a “Burnt Clay” primary in OKLCH and dark-mode canonicals. The git history reads as a sequence rather than parallel experiments: first a dual light/dark token system with a shadcn sidebar migrated across every route, then runtime-switchable brand palettes and a fixed top bar, and finally an anonymous public “front door” — an install-and-quickstart onboarding surface — layered on top of the authenticated app and hardened through automated design critique.
What we built
Highlights of the work
Package registry
Author and version canonical packages of AI instructions, skills, and hooks.
Deterministic rendering
Provider-specific config files generated exactly and repeatably.
Drift detection
Sync and CI catch when a repo’s AI config falls out of alignment.
Governance built in
Trust gates, RBAC, and audit logs make it safe for whole organizations.
Capabilities demonstrated
Add these to your own project
Let’s talk
Have a project, or a product that could work harder?
Most projects begin with a short, no-pressure discovery call.