vibecodng.com

Free MCP betaIndex and tools live

Measured entry

efferd-form-2

inputminimal-flat

A compact project-submission panel with name, repository, and description fields plus decorative border accents. It ships as a TypeScript shadcn registry block and composes Button, Field, Input, InputGroup, and Textarea primitives. It also expects Lucide icons, Tailwind theme tokens, path aliases, and the utility setup used by those primitives.

Specimen
Harness screenshot of efferd-form-2 at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of efferd-form-2 at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of efferd-form-2 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-2
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal36.2 KB (101.6 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 36s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/input.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A tidy, adaptable shell with clear labels and no detected runtime or accessibility issues in the prepared harness. It needs a shadcn-style setup to build, and it is only presentation: teams must add the actual form semantics, validation, and submission logic.

Use it if

  • You want a styled starting point for an open-source project submission screen.
  • Your app already uses shadcn conventions and the referenced field and input primitives.
  • You plan to supply validation, submission state, and backend behavior yourself.

Skip it if

  • You need a complete form with validation, error handling, and a submit action already wired.
  • Your design system does not use Tailwind theme tokens or shadcn component aliases.
  • You want to avoid bringing in the grouped-input and field abstractions for a small form.

Install

Installation record for efferd-form-2
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

In a non-shadcn project, add or replace the Button, Field, Input, InputGroup, and Textarea primitives; configure the at-sign source alias; provide the shared class-name utility those primitives import; install Radix and Lucide dependencies; and map the Tailwind theme tokens and utility classes to your styling system. Wrap the fields in a real form and add validation and submission handling.

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 input pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.