Repository navigation
[idea] UI loop: apply directly with one check per batch, SCSS-first, lint regressions N1–N4 #170
Description
The idea: for the same ~3 h of UI work, the toolkit arm made 1,507 calls to the MCP arm's 515. The toolkit arm's result was closer to the wireframes. The extra calls came from two things:
- 7 drafting agents each ran check → exec → mx check → fidelity on every script, then the lead re-applied it.
- Round 1 introduced four regressions (N1 shell detached, N2
.d-noneprecedence, N3 32 px autoFit columns, N4 focus ring).
Proposals:
- UI agents apply directly, with one mx check per batch.
- Cross-cutting fixes first, done once as SCSS.
- Re-review only the pages that changed.
- Add N1–N4 as a pre-apply lint in
check-page-shell.sh/learned-css-that-never-applied.md.
Field evidence: contrib/inbox/2026-09-29-ui-loop-efficiency.md (#165).
Done = the next UI round needs about half the calls, with no fidelity regression.
Activity
Merge #323: inbox promotions — exec refusal table, UI fix rounds, mea…
MendixMau commentedon Oct 20, 2026
Shipped in
skills/learned-page-patterns.md→ "UI fix rounds — fix once in SCSS, apply directly, re-look only what changed": cross-cutting fixes first as SCSS, drafters hand checked scripts toexec.shwith no pre-apply to a scratch copy, re-look only the pages the round changed (N of N), and an N1–N4 pre-apply table (shell on the layout root,.d-noneprecedence, DG2autoFitcolumns, focus ring) with an M-of-M denominator. N1–N4 shipped as a skill checklist, not acheck-page-shell.shlint, in line with skills over scripts. Landed in 31e90ae (#329), part of release v2026.10.19. The "half the calls" target can only be measured on the next field UI round.Generated by Claude Code