I build forms and review screens with clear validation, useful previews and inspectable output. Start with one component and a scope we can test.
Nine independent prototypes built with AI assistance. These are work samples, not commissioned client projects or endorsements. Public observations and synthetic examples are labelled.
Up to eight agreed fields, validation that keeps the draft, a readable preview and one text or JSON export. Includes source files, relevant tests, run instructions and one correction against the agreed requirements.
Send a field list, mockup or reproducible bug. We agree the scope, fixed price and timing after reviewing it. Backend connections, accounts, payments and production deployment need separate scoping.
Validate matching email fields, make consent explicit and preserve input when a simulated submission fails.
Try it: load the synthetic example, change Confirm email, then validate. Correct the email and simulate a failure to inspect draft retention.
Open form-QA sample →Review three synthetic extraction cases. Missing values stay explicit, corrections retain their source, and each decision is made by the reviewer.
Open parsing review →Export an enquiry as text and JSON. Unprovided timeline, company or budget stays unknown instead of being guessed.
Open brief export →Two differently named public parts share a normalized code. Keep the original records and flag the pair for a specialist to review.
Open Vietnamese catalogue checker →Project requests and freelance applications retain shared contact details and produce different local summaries.
Open two-path intake →Inspect a proposed discovery slot across Pakistan, Vietnam and New York, with date-specific daylight-saving checks.
Open time preview →Compose a project, freelance or other enquiry while preserving the original message and making the intent explicit.
Open summary composer →Keep six public portfolio references separate from intentionally malformed practice examples. No live-site diagnosis is implied.
Open link-review fixture →Edit a 180-character introduction while retaining the full local brief. The demo documents how it counts Unicode.
Open brief composer →