Guides

Comparison results: settings-form

Comparison overview, scores, protocol and limits

All nine settings-form builds from the 2026-10-15 cohort follow unchanged: three arms, three runs each. These checks grade the resulting apps, not operational safety, complete accessibility or physical-device VoiceOver behavior. Read the overview's protocol notes and limits before comparing scores.

Every run and check

settings-form, shadcn/ui, run 1: 100/100

settings-form: Arm: shadcn; Score: 100; Typecheck: 20/20; Lint: 10/10; Axe: 20/20; 50/50

Screen	Arm	Score	Typecheck	Lint	Axe	Behavior
settings-form	shadcn	100	20/20	10/10	20/20	50/50

Every check passed.

Problems the app had before the agent ran, which cost nothing: 0 type errors, 0 lint errors.

The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint: Acceptance items: 1; Viewport: desktop; pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter: Acceptance items: 2; Viewport: desktop; pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there: Acceptance items: 3; Viewport: desktop; pass
With two errors, each shows on its field and focus moves to the first: Acceptance items: 3; Viewport: desktop; pass
Correcting the field and saving again clears its error: Acceptance items: 4; Viewport: desktop; pass
"Settings saved" appears in a live region after a successful save: Acceptance items: 5; Viewport: desktop; pass
At 390px wide the page does not scroll sideways: Acceptance items: 6; Viewport: phone; pass

Behavior check	Acceptance items	Viewport	Result
The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint	1	desktop	pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter	2	desktop	pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there	3	desktop	pass
With two errors, each shows on its field and focus moves to the first	3	desktop	pass
Correcting the field and saving again clears its error	4	desktop	pass
"Settings saved" appears in a live region after a successful save	5	desktop	pass
At 390px wide the page does not scroll sideways	6	phone	pass

390px light: Result: pass
390px dark: Result: pass
1280px light: Result: pass
1280px dark: Result: pass

Axe	Result
390px light	pass
390px dark	pass
1280px light	pass
1280px dark	pass

Screenshots, as evidence only: 8 in scripts/agent-usability/runs/2026-10-15/shadcn/settings-form/1/score/screenshots.

settings-form, shadcn/ui, run 2: 100/100

settings-form: Arm: shadcn; Score: 100; Typecheck: 20/20; Lint: 10/10; Axe: 20/20; 50/50

Screen	Arm	Score	Typecheck	Lint	Axe	Behavior
settings-form	shadcn	100	20/20	10/10	20/20	50/50

Every check passed.

Problems the app had before the agent ran, which cost nothing: 0 type errors, 0 lint errors.

The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint: Acceptance items: 1; Viewport: desktop; pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter: Acceptance items: 2; Viewport: desktop; pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there: Acceptance items: 3; Viewport: desktop; pass
With two errors, each shows on its field and focus moves to the first: Acceptance items: 3; Viewport: desktop; pass
Correcting the field and saving again clears its error: Acceptance items: 4; Viewport: desktop; pass
"Settings saved" appears in a live region after a successful save: Acceptance items: 5; Viewport: desktop; pass
At 390px wide the page does not scroll sideways: Acceptance items: 6; Viewport: phone; pass

Behavior check	Acceptance items	Viewport	Result
The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint	1	desktop	pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter	2	desktop	pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there	3	desktop	pass
With two errors, each shows on its field and focus moves to the first	3	desktop	pass
Correcting the field and saving again clears its error	4	desktop	pass
"Settings saved" appears in a live region after a successful save	5	desktop	pass
At 390px wide the page does not scroll sideways	6	phone	pass

390px light: Result: pass
390px dark: Result: pass
1280px light: Result: pass
1280px dark: Result: pass

Axe	Result
390px light	pass
390px dark	pass
1280px light	pass
1280px dark	pass

Screenshots, as evidence only: 8 in scripts/agent-usability/runs/2026-10-15/shadcn/settings-form/2/score/screenshots.

settings-form, shadcn/ui, run 3: 100/100

settings-form: Arm: shadcn; Score: 100; Typecheck: 20/20; Lint: 10/10; Axe: 20/20; 50/50

Screen	Arm	Score	Typecheck	Lint	Axe	Behavior
settings-form	shadcn	100	20/20	10/10	20/20	50/50

Every check passed.

Problems the app had before the agent ran, which cost nothing: 0 type errors, 0 lint errors.

The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint: Acceptance items: 1; Viewport: desktop; pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter: Acceptance items: 2; Viewport: desktop; pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there: Acceptance items: 3; Viewport: desktop; pass
With two errors, each shows on its field and focus moves to the first: Acceptance items: 3; Viewport: desktop; pass
Correcting the field and saving again clears its error: Acceptance items: 4; Viewport: desktop; pass
"Settings saved" appears in a live region after a successful save: Acceptance items: 5; Viewport: desktop; pass
At 390px wide the page does not scroll sideways: Acceptance items: 6; Viewport: phone; pass

Behavior check	Acceptance items	Viewport	Result
The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint	1	desktop	pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter	2	desktop	pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there	3	desktop	pass
With two errors, each shows on its field and focus moves to the first	3	desktop	pass
Correcting the field and saving again clears its error	4	desktop	pass
"Settings saved" appears in a live region after a successful save	5	desktop	pass
At 390px wide the page does not scroll sideways	6	phone	pass

390px light: Result: pass
390px dark: Result: pass
1280px light: Result: pass
1280px dark: Result: pass

Axe	Result
390px light	pass
390px dark	pass
1280px light	pass
1280px dark	pass

Screenshots, as evidence only: 8 in scripts/agent-usability/runs/2026-10-15/shadcn/settings-form/3/score/screenshots.

settings-form, shadcn/ui with its skill, run 1: 100/100

settings-form: Arm: shadcn-skill; Score: 100; Typecheck: 20/20; Lint: 10/10; Axe: 20/20; 50/50

Screen	Arm	Score	Typecheck	Lint	Axe	Behavior
settings-form	shadcn-skill	100	20/20	10/10	20/20	50/50

Every check passed.

Problems the app had before the agent ran, which cost nothing: 0 type errors, 0 lint errors.

The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint: Acceptance items: 1; Viewport: desktop; pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter: Acceptance items: 2; Viewport: desktop; pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there: Acceptance items: 3; Viewport: desktop; pass
With two errors, each shows on its field and focus moves to the first: Acceptance items: 3; Viewport: desktop; pass
Correcting the field and saving again clears its error: Acceptance items: 4; Viewport: desktop; pass
"Settings saved" appears in a live region after a successful save: Acceptance items: 5; Viewport: desktop; pass
At 390px wide the page does not scroll sideways: Acceptance items: 6; Viewport: phone; pass

Behavior check	Acceptance items	Viewport	Result
The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint	1	desktop	pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter	2	desktop	pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there	3	desktop	pass
With two errors, each shows on its field and focus moves to the first	3	desktop	pass
Correcting the field and saving again clears its error	4	desktop	pass
"Settings saved" appears in a live region after a successful save	5	desktop	pass
At 390px wide the page does not scroll sideways	6	phone	pass

390px light: Result: pass
390px dark: Result: pass
1280px light: Result: pass
1280px dark: Result: pass

Axe	Result
390px light	pass
390px dark	pass
1280px light	pass
1280px dark	pass

Screenshots, as evidence only: 8 in scripts/agent-usability/runs/2026-10-15/shadcn-skill/settings-form/1/score/screenshots.

settings-form, shadcn/ui with its skill, run 2: 100/100

settings-form: Arm: shadcn-skill; Score: 100; Typecheck: 20/20; Lint: 10/10; Axe: 20/20; 50/50

Screen	Arm	Score	Typecheck	Lint	Axe	Behavior
settings-form	shadcn-skill	100	20/20	10/10	20/20	50/50

Every check passed.

Problems the app had before the agent ran, which cost nothing: 0 type errors, 0 lint errors.

The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint: Acceptance items: 1; Viewport: desktop; pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter: Acceptance items: 2; Viewport: desktop; pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there: Acceptance items: 3; Viewport: desktop; pass
With two errors, each shows on its field and focus moves to the first: Acceptance items: 3; Viewport: desktop; pass
Correcting the field and saving again clears its error: Acceptance items: 4; Viewport: desktop; pass
"Settings saved" appears in a live region after a successful save: Acceptance items: 5; Viewport: desktop; pass
At 390px wide the page does not scroll sideways: Acceptance items: 6; Viewport: phone; pass

Behavior check	Acceptance items	Viewport	Result
The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint	1	desktop	pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter	2	desktop	pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there	3	desktop	pass
With two errors, each shows on its field and focus moves to the first	3	desktop	pass
Correcting the field and saving again clears its error	4	desktop	pass
"Settings saved" appears in a live region after a successful save	5	desktop	pass
At 390px wide the page does not scroll sideways	6	phone	pass

390px light: Result: pass
390px dark: Result: pass
1280px light: Result: pass
1280px dark: Result: pass

Axe	Result
390px light	pass
390px dark	pass
1280px light	pass
1280px dark	pass

Screenshots, as evidence only: 8 in scripts/agent-usability/runs/2026-10-15/shadcn-skill/settings-form/2/score/screenshots.

settings-form, shadcn/ui with its skill, run 3: 100/100

settings-form: Arm: shadcn-skill; Score: 100; Typecheck: 20/20; Lint: 10/10; Axe: 20/20; 50/50

Screen	Arm	Score	Typecheck	Lint	Axe	Behavior
settings-form	shadcn-skill	100	20/20	10/10	20/20	50/50

Every check passed.

Problems the app had before the agent ran, which cost nothing: 0 type errors, 0 lint errors.

The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint: Acceptance items: 1; Viewport: desktop; pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter: Acceptance items: 2; Viewport: desktop; pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there: Acceptance items: 3; Viewport: desktop; pass
With two errors, each shows on its field and focus moves to the first: Acceptance items: 3; Viewport: desktop; pass
Correcting the field and saving again clears its error: Acceptance items: 4; Viewport: desktop; pass
"Settings saved" appears in a live region after a successful save: Acceptance items: 5; Viewport: desktop; pass
At 390px wide the page does not scroll sideways: Acceptance items: 6; Viewport: phone; pass

Behavior check	Acceptance items	Viewport	Result
The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint	1	desktop	pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter	2	desktop	pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there	3	desktop	pass
With two errors, each shows on its field and focus moves to the first	3	desktop	pass
Correcting the field and saving again clears its error	4	desktop	pass
"Settings saved" appears in a live region after a successful save	5	desktop	pass
At 390px wide the page does not scroll sideways	6	phone	pass

390px light: Result: pass
390px dark: Result: pass
1280px light: Result: pass
1280px dark: Result: pass

Axe	Result
390px light	pass
390px dark	pass
1280px light	pass
1280px dark	pass

Screenshots, as evidence only: 8 in scripts/agent-usability/runs/2026-10-15/shadcn-skill/settings-form/3/score/screenshots.

settings-form, Ouro HX, run 1: 100/100

settings-form: Arm: ouro; Score: 100; Typecheck: 20/20; Lint: 10/10; Axe: 20/20; 50/50

Screen	Arm	Score	Typecheck	Lint	Axe	Behavior
settings-form	ouro	100	20/20	10/10	20/20	50/50

Every check passed.

Problems the app had before the agent ran, which cost nothing: 0 type errors, 0 lint errors.

The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint: Acceptance items: 1; Viewport: desktop; pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter: Acceptance items: 2; Viewport: desktop; pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there: Acceptance items: 3; Viewport: desktop; pass
With two errors, each shows on its field and focus moves to the first: Acceptance items: 3; Viewport: desktop; pass
Correcting the field and saving again clears its error: Acceptance items: 4; Viewport: desktop; pass
"Settings saved" appears in a live region after a successful save: Acceptance items: 5; Viewport: desktop; pass
At 390px wide the page does not scroll sideways: Acceptance items: 6; Viewport: phone; pass

Behavior check	Acceptance items	Viewport	Result
The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint	1	desktop	pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter	2	desktop	pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there	3	desktop	pass
With two errors, each shows on its field and focus moves to the first	3	desktop	pass
Correcting the field and saving again clears its error	4	desktop	pass
"Settings saved" appears in a live region after a successful save	5	desktop	pass
At 390px wide the page does not scroll sideways	6	phone	pass

390px light: Result: pass
390px dark: Result: pass
1280px light: Result: pass
1280px dark: Result: pass

Axe	Result
390px light	pass
390px dark	pass
1280px light	pass
1280px dark	pass

Screenshots, as evidence only: 8 in scripts/agent-usability/runs/2026-10-15/ouro/settings-form/1/score/screenshots.

settings-form, Ouro HX, run 2: 100/100

settings-form: Arm: ouro; Score: 100; Typecheck: 20/20; Lint: 10/10; Axe: 20/20; 50/50

Screen	Arm	Score	Typecheck	Lint	Axe	Behavior
settings-form	ouro	100	20/20	10/10	20/20	50/50

Every check passed.

Problems the app had before the agent ran, which cost nothing: 0 type errors, 0 lint errors.

The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint: Acceptance items: 1; Viewport: desktop; pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter: Acceptance items: 2; Viewport: desktop; pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there: Acceptance items: 3; Viewport: desktop; pass
With two errors, each shows on its field and focus moves to the first: Acceptance items: 3; Viewport: desktop; pass
Correcting the field and saving again clears its error: Acceptance items: 4; Viewport: desktop; pass
"Settings saved" appears in a live region after a successful save: Acceptance items: 5; Viewport: desktop; pass
At 390px wide the page does not scroll sideways: Acceptance items: 6; Viewport: phone; pass

Behavior check	Acceptance items	Viewport	Result
The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint	1	desktop	pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter	2	desktop	pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there	3	desktop	pass
With two errors, each shows on its field and focus moves to the first	3	desktop	pass
Correcting the field and saving again clears its error	4	desktop	pass
"Settings saved" appears in a live region after a successful save	5	desktop	pass
At 390px wide the page does not scroll sideways	6	phone	pass

390px light: Result: pass
390px dark: Result: pass
1280px light: Result: pass
1280px dark: Result: pass

Axe	Result
390px light	pass
390px dark	pass
1280px light	pass
1280px dark	pass

Screenshots, as evidence only: 8 in scripts/agent-usability/runs/2026-10-15/ouro/settings-form/2/score/screenshots.

settings-form, Ouro HX, run 3: 100/100

settings-form: Arm: ouro; Score: 100; Typecheck: 20/20; Lint: 10/10; Axe: 20/20; 50/50

Screen	Arm	Score	Typecheck	Lint	Axe	Behavior
settings-form	ouro	100	20/20	10/10	20/20	50/50

Every check passed.

Problems the app had before the agent ran, which cost nothing: 0 type errors, 0 lint errors.

The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint: Acceptance items: 1; Viewport: desktop; pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter: Acceptance items: 2; Viewport: desktop; pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there: Acceptance items: 3; Viewport: desktop; pass
With two errors, each shows on its field and focus moves to the first: Acceptance items: 3; Viewport: desktop; pass
Correcting the field and saving again clears its error: Acceptance items: 4; Viewport: desktop; pass
"Settings saved" appears in a live region after a successful save: Acceptance items: 5; Viewport: desktop; pass
At 390px wide the page does not scroll sideways: Acceptance items: 6; Viewport: phone; pass

Behavior check	Acceptance items	Viewport	Result
The six fields have visible labels, come in order, show the loaded settings, and Bio has its hint	1	desktop	pass
While saving, the button is disabled or marked busy and the form can't be sent again by click or Enter	2	desktop	pass
A server error shows under its field, marks it invalid, is read with it, and focus moves there	3	desktop	pass
With two errors, each shows on its field and focus moves to the first	3	desktop	pass
Correcting the field and saving again clears its error	4	desktop	pass
"Settings saved" appears in a live region after a successful save	5	desktop	pass
At 390px wide the page does not scroll sideways	6	phone	pass

390px light: Result: pass
390px dark: Result: pass
1280px light: Result: pass
1280px dark: Result: pass

Axe	Result
390px light	pass
390px dark	pass
1280px light	pass
1280px dark	pass

Screenshots, as evidence only: 8 in scripts/agent-usability/runs/2026-10-15/ouro/settings-form/3/score/screenshots.

Source on GitHub This page as Markdown