Results for “form-management”

Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors.

Automates browser tasks including navigation, data extraction, screenshots, form filling, and session management via a CLI tool.

Provides practical patterns for using fp-ts with React, including hooks, state management, form validation, and data fetching.

Database management, forms, reports, and data operations with LibreOffice Base.

Database management, forms, reports, and data operations with LibreOffice Base.

Database management, forms, reports, and data operations with LibreOffice Base.

Database management, forms, reports, and data operations with LibreOffice Base.

Database management, forms, reports, and data operations with LibreOffice Base.

Controls a Chrome browser through the AIPex extension and MCP bridge, enabling navigation, clicking, form filling, screenshots, tab management, and content downloads.

Practical patterns for using fp-ts with React, covering hooks, state management, form validation, and data fetching for React 18/19 and Next.js 14/15.

Practical patterns for using fp-ts with React, covering hooks, state management, form validation, and data fetching for React 18/19 and Next.js 14/15.

Maximize form completion rates for lead capture, contact, demo, and checkout forms through field audits, layout recommendations, and A/B test ideas.

Practical patterns for using fp-ts with React: Option for optional state, Either for form validation, TaskEither for data fetching, and RemoteData for async state management.

Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms.

Design forms that minimize friction, prevent errors, and guide users to successful completion.

Form UX

Optimize non-signup forms such as lead capture, contact, demo request, application, survey, quote, and checkout forms to maximize completion while preserving data usefulness.

Optimizes non-signup forms such as lead capture, contact, demo request, application, survey, quote, and checkout forms to maximize completion while preserving data usefulness.

Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms.

When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

Maximize form completion rates for lead capture, contact, demo request, application, survey, quote, and checkout forms by diagnosing friction and applying evidence-based optimizations.

`analysis-agent`/`task-agent`/`review-agent`: use when form fields, validation, async checks, submit states, or recovery change; skip when form behavior is unaffected.

Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms.

Build signal-based forms in Angular v21+ using the new Signal Forms API. Use for form creation with automatic two-way binding, schema-based validation, field state management, and dynamic forms. Triggers on form implementation, adding validation, creating multi-step forms, or building forms with conditional fields. Signal Forms are experimental but recommended for new Angular projects. Don't use for template-driven forms without signals or third-party form libraries like Formly or ngx-formly.

Optimize non-signup forms such as lead capture, contact, demo request, application, survey, quote, and checkout forms to maximize completion while preserving data usefulness.

Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms.

When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms.

Optimizes non-signup forms such as lead capture, contact, demo request, application, survey, quote, and checkout forms to maximize completion while preserving data usefulness.

Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms. Use when the goal is to increase form completion rate, reduce friction, or improve lead quality without breaking compliance or downstream workflows.