Hi Product Hunt, I’m Owaiz, the maker of Design System Loop. Your product has a shared input. The next screen builds another. A theme token exists, but a new button hardcodes its own color. The reason for an exception disappears between tasks. I built DS Loop to help teams do that design-system work with the coding agent they already use. It combines local source checks with a companion skill for Codex, Claude Code and Cursor. The checks give your agent findings, source locations and coverage. The skill guides it through investigating the problem, proposing a scope, implementing the work you approve, and checking the result. Components, usage examples and decisions stay with your code. You can start a foundation, connect existing screens to shared components, or work on one inconsistency. Keep the library and conventions that already serve your product. The worked example follows a small theme fix: two CSS declarations connect the action color to the existing palette. It includes the diff, token-only audits, light and dark browser checks, and a handoff. It’s a demo project, so you can inspect exactly what it proves. DS Loop is free and open source under MIT. The engine runs locally; your coding agent has its own costs and data settings. This is a supervised alpha, and changes need review before shipping. Try it on one screen or component you want to improve. I’d like to hear what you chose, where you got stuck, and whether the next task was easier to start. https://designsystemloop.dev/wor...

Design System Loop

Build and maintain your SAAS app design system

Build and maintain your SAAS app design system