vibecodng.com

Free MCP betaIndex and tools live

Measured entry

efferd-form-3

auth-formminimal-flat

A responsive account-settings block for editing name, email, password, and phone details, with a separate save action for each field. It ships as a shadcn registry block built from Button, ButtonGroup, Field, Input, and InputGroup primitives, with Lucide icons and Radix-backed UI dependencies. It provides layout only, not form state, validation, or persistence.

Specimen
Harness screenshot of efferd-form-3 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of efferd-form-3 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of efferd-form-3 at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

Measured

Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.

Harness measurements recorded for efferd-form-3
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical1
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal36.9 KB (102.3 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 1m 28s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/button.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A tidy, responsive settings shell with sensible per-field actions, but it is not a turnkey form. The unnamed password visibility control is a release-blocking accessibility defect. It also needs a shadcn-style setup because it does not mount in a bare project.

Use it if

  • You need a compact profile settings screen where account fields are saved independently.
  • Your app already uses shadcn conventions and can supply the referenced UI primitives and utility styles.
  • You plan to connect each row to your own validation, mutation, and error-handling logic.

Skip it if

  • You need a login, registration, or other authentication form rather than an account settings editor.
  • You want a complete working form with submission state, schema validation, and backend integration included.
  • You cannot fix the unnamed password visibility button before release.
  • Your design system does not use shadcn-style aliases, utility classes, and composed input primitives.

Install

Installation record for efferd-form-3
Declared dependenciesradix-ui
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

For a non-shadcn project, add compatible Button, ButtonGroup, Field, Input, and InputGroup components, Lucide React and Radix UI dependencies, Tailwind-compatible theme styles, the at-sign path alias, and the shared lib/utils helper used by the UI primitives. Then add state, validation, save handlers, and an accessible name for the password visibility control.

Source and credit

This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.

Author repository

github.com/shabanhr/efferd-ui
License
MIT
Record published
2026-08-14

Alternatives

Other published entries for the auth-form pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.