vaadin-form-layout
Builds the visual structure and layout of a form, entity editor, or data-entry view in Vaadin Flow (Java) from any spec source — Figma URL, screenshot, text, or prompt — choosing the fields and components, FormLayout sectioning, and responsive column layout. Use when asked to create, implement, build, or generate a form, entity editor, or data entry view in Vaadin, to "add fields", "add a form", or "build a layout for editing", or when the user describes collecting structured input from users — even if they don't say the word "form" explicitly. This skill covers the form's layout and components only; to wire the fields to a Java bean with Binder, converters, and validation, look up the Binder and Form Validation guides via the Vaadin docs MCP (search_vaadin_docs).
Install
With your agent
Install OMGSkills skill "vaadin/agent-skills:skills/vaadin-form-layout" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/vaadin/agent-skills /tmp/agent-skills && ln -s /tmp/agent-skills/skills/vaadin-form-layout ~/.claude/skills/vaadin-form-layoutFrom README
Vaadin Form Creation Workflow Track these three steps as TODOs so progress stays visible and the work can be resumed if it's interrupted partway through. Work through them in order. Step 1 – Understand the input and plan Process the spec source first: fetch and inspect a Figma URL, read a screenshot, or parse a text prompt. Well-defined spec (explicit field list, or a design with clear fields and labels): implement exactly what's specified. Do not invent extra fields, rename labels, or add controls the spec doesn't call for. The output should be predictable and faithful to the input. Vague request (e.g. "make a customer form" with no field list): ask a few targeted clarifying questions before planning — which fields and their data types, how they group, and whether it should be a single section or several. Don't silently guess the contents.