thedaviddias/Front-End-Checklist / skills/redundant-entry
redundant-entry
VerifiedUse when reviewing any process that spans multiple screens, steps, or modal stages. Follow the real user journey and compare fields across steps instead of reviewing screens in isolation.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.0 KB |
| references/rule.md | markdown | 4.7 KB |
SKILL.md
View on GitHub---
name: redundant-entry
description: "Use when reviewing any process that spans multiple screens, steps, or modal stages. Follow the real user journey and compare fields across steps instead of reviewing screens in isolation."
metadata:
category: accessibility
priority: high
difficulty: intermediate
estimatedTime: "20"
source: frontendchecklist.io
url: https://frontendchecklist.io/rules/accessibility/redundant-entry
---
# Avoid redundant entry in the same process
Re-entering the same information increases cognitive load, slows task completion, and introduces avoidable typing errors. Users with cognitive, motor, or speech-input limitations are affected first, but everyone benefits from fewer repeated fields.
## Quick Reference
- Do not ask users to retype information already provided earlier in the same flow
- Auto-populate repeated fields or offer a clear selection such as "same as billing"
- Review checkout, signup, onboarding, and support flows step by step
- Password confirmation can be a valid security exception, but general profile data is not
## Check
Review this multi-step flow for information that is requested more than once in the same process. Flag fields that should be auto-populated or selectable from previously entered data.
## Fix
Reuse previously entered information within the same process. Auto-populate repeat fields, add "same as" toggles where appropriate, and preserve data between steps so users do not need to retype it.
## Explain
Explain WCAG 2.2 Redundant Entry, what counts as the same process, and when security or validity exceptions allow re-entry.
## Code Review
Review multi-step forms, checkout, onboarding, support, and account flows related to Avoid redundant entry in the same process. Flag exact steps where previously entered information is required again without auto-population or a selection mechanism.
---
For full implementation details, code examples, and framework-specific guidance,
see `references/rule.md`.
Rule page: https://frontendchecklist.io/rules/accessibility/redundant-entry
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |