The rules — the settings page
- Settings are ONE tabbed card (the tabs standard); each pane is its OWN form with its OWN submit — saving General never touches Billing, and a giant form across tabs is forbidden.
- Text/select fields follow the form layout (grid, labels, hints); ON/OFF preferences are switch rows in the
.form-check-reversesettings-row look (no.text-end). - In a real app each form rides former (fill from the load, dirty guard, save endpoint) — the framework's /profile and /company pages are the live reference of this exact pattern.
- Dangerous account operations (delete, transfer) are NOT settings tabs — they get their own section/flow with confirmation (see the accordion "danger zone" idea in accordions).