generate-frontend-forms
Guide for creating forms using Sentry's new form system. Use when implementing forms, form fields, display-only form content, validation, or auto-save functionality.
Install
With your agent
Install OMGSkills skill "getsentry/sentry:generate-frontend-forms" 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/getsentry/sentry /tmp/sentry && ln -s /tmp/sentry/.agents/skills/generate-frontend-forms ~/.claude/skills/generate-frontend-formsFrom README
Form System Guide This skill provides patterns for building forms using Sentry's new form system built on TanStack React Form and Zod validation. Core Principle Always use the new form system (useScrapsForm, AutoSaveForm) for new forms. Never create new forms with the legacy JsonForm or Reflux-based systems. All forms should be schema based. DO NOT create a form without schema validation. Imports All form components are exported from @sentry/scraps/form: Important: DO NOT import from deeper paths, like '@sentry/scraps/form/field'. You can only use what is part of the PUBLIC interface in the index file in @sentry/scraps/form. --- Form Hook: useScrapsForm The main hook for creating forms with validation and submission handling. Basic Important: Always spread defaultFormOptions first. It configures validation to run on submit initially, then on every change after the first submission. This is why validators are defined as onDynamic, and it's what provides a consistent UX.
More from this repo
design-system
Guide for using Sentry's layout and text primitives.
backend-conventions
Sentry backend conventions for logging, tracing/spans, span/tag attribute naming, metrics tags, and the options system.
feature-flags
Gate a Sentry feature behind a FlagPole feature flag.