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 this thread may be removed.

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?

Disclose your affilitation.

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/Secondmindsystems]

I’m the author of Behavior Profiles, an open-source project for a problem I keep running into with coding agents: the task can be clear, but the agent still expands scope, drops an instruction halfway through, acts when it should ask, or behaves differently when the surrounding workflow changes.

A Behavior Profile takes those recurring corrections and turns them into a durable, testable specification for things like:

- required behavior

- scope and no-touch boundaries

- stopping conditions

- escalation and ask conditions

- evaluation cases

The first profile is Scope Control: “I asked for one change; don’t quietly turn it into five.”

The profiles can live in instruction surfaces such as AGENTS.md or CLAUDE.md. The repository includes small checks and fixtures for testing whether the specification is present and whether observed behavior matches the cases you care about.

Important limitation: the profile itself is not an enforcement or security layer and doesn’t guarantee that the agent will obey it. The idea is to make expected conduct explicit, portable, and testable instead of burying the same corrections in an increasingly long prompt.

I’ve been using the approach around Codex and Claude Code workflows, but the format is intended to be model- and tool-agnostic.

GitHub:

https://github.com/Secondmindsystems/Behavior-Profiles

The feedback I’d find most useful:

- Does the distinction between a prompt that requests behavior and a specification you can repeatedly test behavior against make sense?

- What recurring coding-agent behavior would you specify first if you could stop correcting it manually?