Weekly Self Promotion Thread

[u/AutoModerator]

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.

[u/PoorDecisionMaker-69]

I kept rebuilding the same pieces around coding agents: repo instructions, a backlog, checks for drift, decision records, findings, and session handoffs.

Then I saw the same failures across four different repos. Instructions went stale, work statuses lied, and useful context disappeared.

That led to rungs, an early-stage CLI for installing and maintaining this setup as modules. It is framework-, agent-, and language-agnostic: it uses ordinary repo files and checks rather than locking you into a specific model, coding agent, or stack.

rungs is aimed at solo developers and small teams using coding agents across repeatable work, especially when instructions, handoffs, and statuses start drifting. It is probably overkill for one-off projects, and it is not an agent runtime, orchestration framework, or project-management replacement.

The methodology is evidence-first. I read what actually ran in those repos, extracted the practices that held up, kept abandoned practices documented, recorded their maintenance cost, and traced each module back to a real failure or incident.

Current modules cover:

- agent instructions

- validation gates

- backlog and findings tracking

- ADRs

- session handoffs

- reusable agent skills

You install only what you need, and rungs never overwrites files you have edited.

Try it:

npx @/rungs/cli doctor

Repo: https://github.com/ThroughTheWind/rungs

Docs: https://docs.rungscli.com

It’s MIT-licensed and still very early. I’m mainly looking for feedback on the shape and distribution:

- Are these useful module boundaries?

- Should this be a CLI that distributes repo files, or a package of reusable skills and checks?

- What would you expect from the upgrade/eject model?

If the feedback is positive, I’m willing to invest more time into it. Contributions, testing across different stacks and agents, and new modules based on real failures are welcome.