Loading...
Loading...
Found 9 Skills
Improve unclear UX copy, error messages, microcopy, labels, and instructions. Makes interfaces easier to understand and use.
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.
Web platform design and accessibility guidelines. Use when building web interfaces, auditing accessibility, implementing responsive layouts, or reviewing web UI code. Triggers on tasks involving HTML, CSS, web components, WCAG compliance, responsive design, or web performance.
Use when optimizing conversion rates, designing A/B tests, or improving landing pages. Covers A/B testing methodology, landing page optimization, form design, statistical significance, funnel analysis, and CRO prioritization frameworks.
Build standalone custom pages using Amis low-code framework, independent of object records. Pages are defined as paired .page.yml (metadata) and .page.amis.json (UI schema) files in main/default/pages/. Covers page types (app, list, record), render_engine configuration, pageAssignments for desktop/mobile, and Amis schema with components like service, crud, chart, form, wizard, tabs. Includes examples for dashboards, reports, and custom forms.
When the user wants to design, optimize, or audit newsletter signup forms. Also use when the user mentions "newsletter," "email signup," "subscribe form," "email capture," or "lead magnet."
Best practices for Jetpack Compose text fields in Android apps. Use when building forms or search inputs and you need guidance on IME padding, keyboard options, focus movement, and accessible input behavior.
Use when designing, reviewing, or implementing web UIs and you need concrete MUST/SHOULD/NEVER rules for accessibility, interaction patterns, forms, layout, animation, performance, content, or visual design decisions.
Use when designing how an interface behaves rather than how it looks — user flows, navigation and information architecture, forms and validation, loading/empty/error states, confirmation and undo for destructive actions, button and error message wording, feedback for slow operations, or mobile and touch behavior. Also use when a UI looks finished but breaks on bad input, slow networks, no data, or first use.