跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

forms-inputs-checkout

Use when designing, critiquing, or implementing forms, inputs, validation, checkout, registration, payment, or any data-entry flow.

hueyexe · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add hueyexe/frontend-agent-skills --skill forms-inputs-checkout

技能说明


name: forms-inputs-checkout description: "Use when designing, critiquing, or implementing forms, inputs, validation, checkout, registration, payment, or any data-entry flow." license: MIT metadata: author: hueyexe

Forms, Inputs, and Checkout

Purpose

Help an agent design, critique, and implement clear, accessible, high-conversion forms, inputs, validation, and checkout flows.

Treat every form as a barrier between a person and a goal. The agent's job is to reduce that barrier without collecting bad data, hiding meaningful choices, or weakening accessibility, privacy, legal, or business requirements.

When to use this skill

Use this skill for:

  • Checkout, cart, payment, shipping, billing, promo-code, account, registration, sign-in, onboarding, subscription, lead-capture, support, survey, settings, profile, upload, and data-entry forms.
  • Critiquing screenshots, wireframes, Figma descriptions, HTML/CSS/React components, design-system components, or product flows involving forms.
  • Choosing labels, input controls, grouping, progress indicators, defaults, validation, error messages, help text, submit states, and success states.
  • Making frontend guidance for semantic HTML forms, accessible names, focus, keyboard flow, validation, and responsive behavior.

When not to use this skill

Do not use this skill for:

  • General page layout, landing pages, navigation, marketing content, or visual brand work unless the page contains a form or checkout decision.
  • Backend data modeling, fraud detection, tax, legal, PCI/security implementation, or payment processor integration details beyond UX/frontend implications.
  • General conversion-copy work outside form context.
  • Native platform-specific form controls when the user explicitly asks for a platform guideline not covered by the source material. In that case, ask or use the appropriate platform skill/source.

Core principles

  1. Start outside-in. Begin with the user's goal and the moment in their journey, not with the database fields the organization wants.
  2. Remove, defer, infer, or default before designing another field. Every question creates effort and the possibility of error.
  3. Make the path to completion visually obvious. A form should have a clear scan line from title to first question to final action.
  4. Use controls that match the question. Prefer native, semantic form controls and visible options when the number of options is small.
  5. Use labels as durable context. Do not rely on placeholder-only labels for anything longer than a trivial, familiar, one-field interaction.
  6. Validate to help, not to scold. Validate after a person has finished an answer, prevent avoidable errors, and provide remedies in context.
  7. Design for mistakes. People will omit steps, choose the wrong action, mistype, misunderstand labels, and miss information under stress.
  8. Do not use color alone. Errors, success, required/optional status, disabled states, and payment/security cues need text and/or shape in addition to color.
  9. Keep checkout focused. Remove distractions, avoid forced account creation, show costs and consequences clearly, and keep the primary action aligned with the buyer's goal.
  10. Make progress honest. Use progress indicators only when the sequence and scope are stable enough that the indicator will not mislead.

See references/principle-cards.md for each principle as a reusable card.

Default recommendations

Use these defaults unless the user provides a product-specific constraint or the skill's decision prompts indicate a question is needed.

Form purpose and scope

Default: optimize for successful completion of the user's current goal with the minimum trustworthy data required.

Override when: regulatory, security, fraud, identity, eligibility, support, or fulfillment requirements demand additional data. Ask for the requirement and consequence.

Question set

Default: remove nonessential questions; postpone optional or marketing questions until after the core submission; infer answers from known context when confidence is high.

Override when: optional answers are critical to personalization, eligibility, pricing, compliance, or operational routing.

Structure

Default: use a single page for short forms with a few coherent topics; use multiple pages or one-thing-per-page for long forms, branching flows, mobile-first flows, or high-focus tasks.

Override when: users need to review many related answers together, compare choices, or complete a dense expert workflow.

Labels

Default: use visible, concise, natural-language labels above fields. Top labels usually minimize completion time, handle localization better, and work well on mobile.

Override when: a dense desktop form has severe vertical constraints, or when a complex settings form needs label scanning more than speed.

Required and optional fields

Default: avoid optional fields. When most fields are required, mark the few optional fields with text such as "Optional." When most fields are optional, mark the few required fields with text such as "Required." Do not mark every field required.

Override when: organizational standards require asterisks; still provide a legend and associate the indicator with the label.

Input controls

Default: use native controls and semantic HTML. Use radio buttons for one choice among a small set, checkboxes for yes/no or multiple choices, text inputs for free-form answers, and select/combobox patterns only when they reduce effort for long option sets.

Override when: the design system has tested accessible custom controls that preserve keyboard, screen reader, focus, and error behavior.

Select boxes

Default: use select boxes as a last resort. Prefer visible radio options for a short list, autocomplete/combobox for long searchable lists, or sensible defaults when the likely answer is known.

Override when: platform conv

阅读完整来源 ↗