agentmods.dev

forms

USE WHEN: Constructing forms, validating inputs, and managing form state with Zod schemas.

Cursor rule for Cursor

15 6d ago A scan 0 tokens original MIT
View the source file omergulcicek/omergulcicek.com
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/omergulcicek/omergulcicek.com/forms
Clone the repo
git clone --depth 1 https://github.com/omergulcicek/omergulcicek.com

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 314 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00314
Opus 5 $0.00000 $0.00157
Sonnet 5 $0.00000 $0.00063
Haiku 4.5 $0.00000 $0.00031

Measured yesterday against content hash 8aca65cffe10, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

forms scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/forms.mdc · 46 lines

What it actually says

Form Management

Constraints

  • Library: Use react-hook-form + @hookform/resolvers/zod.
  • Schema: Store schemas in features/[feature]/schemas/.
  • Defaults: Define defaultValues fully using z.infer from the schema.
  • Performance: Use useWatch or Controller instead of watch.
  • Submission: Use handleSubmit. Prevent double clicks with isSubmitting.
  • Errors: Map server errors using setError.

Bans

  • Manually managing native form submit events.
  • Using watch() at the root level.
  • Synchronizing form state with useEffect.
  • Defining schemas inside component files.
  • Managing form inputs with useState.

Correct Implementation

Incorrect Implementation

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 46 lines · 0 tokens per session scan A 8aca65cffe10

Subscribe to this mod's changes

forms is a cursor rule published in the GitHub repository omergulcicek/omergulcicek.com (15 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 314 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.

Frontenddeveloper-portfoliomarkdown-blogpersonel-websitereactjstailwind-csstanstack-start
Related

Other cursor rules, from other repositories

jsx-and-tsx

When writing React code, use this guide for React best practices and guidance.

janhesters/react-router-saas-template · 0 tokens

facades

When writing facade functions, use this guide for facade functions best practices and guidance.

janhesters/react-router-saas-template · 0 tokens

storybook-stories

Guides the creation and modification of Storybook files specifically within the 'packages/docs' package. It covers conventions, best practices, and helps answer questions about existing story implementations within 'packages/core'.

mondaycom/vibe · 0 tokens

new-component-implementation

Provides a systematic, research-driven workflow for implementing new Vibe components - for the @vibe/core library (located in "packages/core") - from initial research through final validation. Emphasizes studying existing patterns, following established conventions, and systematic progression through types, component…

mondaycom/vibe · 2,471 tokens

base-components

Comprehensive guide for base components in @vibe/core library (BaseInput, BaseList, BaseListItem, InfoText, FieldLabel). Documents their usage patterns, accessibility requirements, form integration patterns, and what consumers need to provide for optimal accessibility and UX. These components serve as foundational…

mondaycom/vibe · 107 tokens

layout-components

Guidelines for using Box and Flex layout components in the @vibe/core library instead of custom CSS for spacing, borders, and flexbox layouts.

mondaycom/vibe · 2,182 tokens