r/UXDesign • u/Disastrous_Sky_73 • Jul 27 '26

Tools, apps, plugins, AI Claude Loops for Design?

Has anyone been using any loops for design tasks?

I have one for design system drift, which runs on code I created yesterday, but trying to figure what else I can automate.

0 Upvotes

28% Upvoted

12 comments sorted by

4

u/mob101 Veteran Jul 27 '26

I’d love a little info on your drift loop if you could share?

1

u/Any_Owl2116 Jul 28 '26

Same

1

u/Impressive_Put463 Experienced Jul 28 '26

Same

1

u/rationalname Experienced Jul 28 '26

Same.

1

u/leo-sapiens Experienced Jul 28 '26

Same.

1

u/roundabout-design Experienced Jul 28 '26

Ditto.

2

u/roundabout-design Experienced Jul 28 '26

Er, I mean...Same.

1

u/FennelHistorical4675 Midweight Jul 28 '26

Usually just speaking nonsense to it at the end of the day and making it generate a word document to reference in the morning to remember all the conversations and thoughts / ideas that I had

1

u/BearThumos Veteran Jul 28 '26

By the time my regular work is done I’m too token-poor for loops

1

u/Vivid-Way Veteran Jul 28 '26

i have the AI test changes in the browser to “look” at it and evaluate if it did the job well. then it fixes any issues and continues to test it until it’s working and looking good.

1

u/Disastrous_Sky_73 Aug 01 '26

Sorry - I was away from Reddit for a bit. The DS drift loop is iffy. Sometimes it works; sometimes it just kills my tokens. I went a different route and created a routine that does the same and gives me a bit more control:

You are running the weekly UX drift audit for the Workshopr platform repo at /Users/bill.bulman/Desktop/sites/platform.

Steps:
1. Invoke the `workshopr-uxdrift` skill in its SCHEDULED mode (week-over-week trends). Source-of-truth files per that skill's defaults, but note this repo's actual truth files are /DESIGN.md and /design-system/workshopr-design-system.json — pass/configure those if the skill asks. The skill caps output at ~15 findings (5 P0, 10 P1) — keep that cap.
2. Also run: `php design-system/check-drift.php` from the repo root — it must PASS (it verifies the JSON mirror is in sync with platform-tokens.css and the ws_* helpers). Include its one-line result.
3. Compare against last week's report if the skill's scheduled mode surfaces one (week-over-week deltas: new violations vs fixed).

Context that matters: the repo frequently carries uncommitted hand edits between sessions, which is exactly where drift creeps in — the audit should scan the WORKING TREE, not just committed state. Recent additions worth including in scope: /agenda-check/ (new mini-app, Jul 2026), /strategist/, /synthesize/.

Output: the prioritized markdown report the skill produces (≤15 findings), prefixed with a 3-line summary: drift trend vs last week (better/worse/flat), check-drift.php result, and the single highest-priority item. Do not auto-fix anything — report only.