Simpler forms and settings

Reduces unnecessary fields and clarifies validation, grouping and when settings actually take effect.

forms-settings-simplification

See how it helps

When is it useful?

Use when users struggle to complete a form or understand whether changes are saved.

What does it help you do?

Questions each field's necessity and supplies meaningful defaults.
Orders related inputs around the user's task and prevents avoidable errors.
Distinguishes automatic saving, explicit submission and pending changes.

Try asking this

Simplify notification settings so users see which changes are saved and which still need confirmation. Change one immediate preference and one setting requiring confirmation. Show their distinct save states and retain the pending value if the server rejects it.

Detailed documentation

Read the skill’s original instructions, examples and checks in their authored language.

Details…Show less

Forms & Settings Simplification

Forms and settings pages are where internal engineering complexity leaks most visibly onto users. Turn intimidating walls of inputs into calm, logical, error-resistant interactions.

Workflow

Audit every field for necessity:
- For each input field, ask:
  - Can this be derived automatically (e.g., slug from title, repo name from URL, timezone from browser)?
  - Can this be deferred until the user actually uses the sub-feature that needs it?
  - Can a raw number/text input be replaced by 3–4 meaningful presets with an optional "Custom..." escape hatch?
Group and order fields by human logic:
- Order fields from natural starting intent (Title / Goal) to specifics, ending with the primary submit action.
- Group settings into task-based sections with plain-language headings and 1-sentence descriptions explaining what changing the setting actually affects.
- Prefer single-column form layouts for sequential reading so the user's eye never zig-zags across unrelated columns.
Prevent errors before they happen (Nielsen):
- Format inputs forgivingly (strip accidental leading/trailing spaces, accept pasted values with spaces/dashes and normalize automatically) rather than rejecting them with cryptic regex errors.
- Validate inline at the right moment (after field blur or on submit, never screaming red errors on the first keystroke while the user is still typing).
- Write error messages that state what went wrong and how to fix it, preserving all user-typed data.
Clarify save semantics on settings pages:
- Make it unmistakable whether toggles apply immediately (auto-save with subtle confirmation) or require clicking a "Save changes" bar with a "Discard" option. Never mix both patterns on the same settings card.

Included files 1

SKILL.md