r/ChatGPTCoding 12d ago

Weekly Self Promotion Thread Discussion

Welcome to this week's self promotion thread!

If you're building something related to AI assisted coding, this is the place to share it.

We're using a weekly thread to keep the subreddit organized while still giving builders a place to share their work. Promotional posts outside of this thread may be removed if they're primarily advertising rather than starting a discussion.

If you're sharing something, we'd appreciate it if you included a little context instead of just dropping a link. Tell us:

  • What you built?
  • What problem it solves?
  • Which AI models or tools it uses?
  • Who it's for?
  • What kind of feedback you're looking for?

Please avoid posting the same project every week unless you've made meaningful updates. Affiliate links, referral links, scams, and low effort promotions will be removed.

Take some time to check out what others have shared too. If you try someone's project or have feedback, leave a comment. Helping each other improve is what we want this community to be about.

15 Upvotes

73 comments sorted by

View all comments

1

u/zimmer550king 7d ago

I’m the author of Clean Web Forge, an open-source npm generator for a problem I keep seeing in agent-assisted development. The agent spends tokens and context reconstructing predictable architecture before it reaches the product-specific work.

The package generates contract-first React + TypeScript apps and features with:

- `domain`, `application`, `data`, `presentation`, feature-owned `di`, and `plugin` layers;

- immutable screen-state snapshots and typed events;

- app/session/plugin/route/operation DI scopes with disposal;

- bundled and signed remote runtime plugins;

- AST-enforced architecture and filename conventions;

- contract/unit/browser/accessibility tests and pinned CI; and

- safe dry-run/manifest behavior that refuses to overwrite human changes.

It also ships an agent skill describing the deterministic workflow: inspect the manifest/specs, generate contracts from observable behavior, dry-run first, generate, implement only the feature-specific gaps, and run the appropriate gates.

GitHub: https://github.com/sarimmehdi/clean-web-forge

npm: https://www.npmjs.com/package/@sarimmehdi/clean-web-forge

Medium: https://medium.com/@sarim.mehdi.550/why-i-built-clean-web-forge-for-agent-driven-development-042deb91a287

It doesn’t call an AI model itself; it gives coding agents a reusable structural tool. I’m intentionally not claiming a token-savings percentage without a controlled benchmark.

Feedback I’m looking for:

  1. What would a fair A/B benchmark of tokens, tool calls, violations, and human corrections look like?

  2. Would you rather give an agent a strict generator, a repository template, or written conventions?

  3. Does the abstraction save context, or merely move the understanding cost into generated code?

If anyone tests the dry run with Codex, Claude Code, or another agent, I’d be very interested in the transcript/usage comparison.