I built a “Steam Workshop” for system architecture + product roadmaps + org blueprints (runs in your browser)'

Source: Dev.to

Introduction

Have you ever wanted to install the architecture of a product the way you install an app?
Not just a diagram, but the whole system‑architecture blueprint:

• services and dependencies
• teams and ownership
• goals → initiatives → work packages
• a 3‑year planning horizon for product managers
• a “prompt pack” so you can remix it

That’s what I’ve been building as a hobby project: SMT (Software Management & Planning Tool).

New Release

This week I shipped something I’m genuinely excited about: you can now publish blueprint packages publicly, and the community can:

• browse and install them
• star them
• comment / discuss them
• see what’s trending (social proof + discovery loops)

Think Figma Community / Steam Workshop, but for product architecture + product/team organization.

Blueprint Packages

A blueprint is a portable package (JSON) that contains:

• manifest – title, summary, tags, trust label, etc.
• prompt pack – seed + variants like MVP / Scale
• full system snapshot – teams, services, goals, initiatives, work packages

Learning through Interaction

1. Install a blueprint.
2. Explore its org, architecture, and roadmap in the app.
3. Remix it to fit your constraints.
4. Publish your remix back to the marketplace.

Why Existing Reference Architectures Fall Short

• Mostly static.
• Divorced from org/team realities.
• Not easily remixable.
• Missing the roadmap / execution story.

SMT aims to make “how a product might actually run” tangible: architecture, org design, and planning are all connected, and you can poke at it, not just read it.

What SMT Enables

• Inspect any type of tech platform.
• Think LeetCode interview prep, but for system design, architecture, team topologies, product roadmaps, and software‑delivery planning.

Local‑First Design

• Runs as a static app in the browser.
• Your systems stay in your browser unless you explicitly publish a blueprint package.

The cloud marketplace is optional and only powers:

• public publishing
• discovery
• stars / comments

No “workspace sync” SaaS lock‑in.

Backend (Free‑Tier Friendly)

• Cloudflare Workers + D1 (SQLite)
• Token‑normalized search (no paid search / no vector DB)
• GitHub OAuth for identity (scope: read:user only)

Security

Public publishing runs secret scanning on the manifest and full system payload, blocking likely API keys / tokens.

Try It Live

• Live demo:
• Repository:

How to Explore

1. Browse the curated catalog.

2. Click Preview on anything that looks interesting.

3. Install an available blueprint and inspect it across:

   • System Architecture Overviews
   • Org Design
   • Roadmap & Backlog Management
   • Year Plan / Detailed Planning

4. In the publish flow, use Publish Publicly.

5. Open Preview on your published blueprint to:

   • Star / Unstar it
   • Post a comment
   • Verify discoverability via search

If anything fails, use the Feedback feature to log issues.

Feedback Questions

• Does the blueprint concept help you understand a product faster?
• Are the “prompt packs” useful, or just noise?
• What should “trending” mean: stars, downloads, recency, or something else?
• What social features would make this fun without turning it into a moderation nightmare?

Open Source & Collaboration

The project is released under CC0. I’m happy to collaborate.

• Repo:
• Issues / PRs welcome: docs, UX polish, seed blueprints, moderation workflows, “remix lineage”, collections, reputation, etc.

Future Ideas

• Remix lineage: “Forked from…” + remixes graph
• Lightweight contributor reputation (badges, trust tiers)
• Reporting / flagging + moderation queue
• Curated collections (e.g., “Backends 101”, “B2B SaaS starters”)

Call to Action

If any part of this sparks your curiosity, try it for 5 minutes and tell me what confused you, what felt magical, and what felt pointless.

Drop a comment here, or open an issue on GitHub.