component-update-form

component-update-form is a cursor rule for Cursor from oakensoul/nextjs-cursor-prompts. It costs 0 tokens per session (4,223 once invoked), scanned A, original, MIT.

A set of instructions for improving an existing form component while preserving compatibility. It covers validation, accessibility, user feedback, TypeScript, performance, and related implementation details.

In plain words
What is it for?
Use it to assess and enhance validation, ARIA attributes, keyboard navigation, loading and success states, error handling, rendering performance, and TypeScript coverage.
Why use it?
It provides a structured review of common form weaknesses, such as unclear errors, poor keyboard or screen-reader support, missing loading states, and incomplete types.

Cursor rule for Cursor

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/oakensoul/nextjs-cursor-prompts/component-update-form
Clone the repo
git clone --depth 1 https://github.com/oakensoul/nextjs-cursor-prompts

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for component-update-form

README.md
[![agentmods](https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-update-form.svg)](https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/component-update-form)
Your own site
<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/component-update-form"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-update-form.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 4,223 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.1 $0.00000 $0.04223
Opus 5 $0.00000 $0.02112
Sonnet 5 $0.00000 $0.00845
Haiku 4.5 $0.00000 $0.00422

Measured 5d ago against content hash fc4407c3a051, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

component-update-form 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 5d ago.

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/prompts/component/component-update-form.mdc · 625 lines

How it starts

The opening of the file, as written. The whole thing — 625 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Form Component Update Request

Please update and enhance an existing form component following our improvement patterns and enhancement standards:

🎯 FORM UPDATE OBJECTIVES:

  1. ENHANCE validation systems with improved rules, real-time feedback, and error handling
  2. IMPROVE accessibility with better ARIA attributes, keyboard navigation, and screen reader support
  3. OPTIMIZE user experience with loading states, success feedback, and form flow improvements
  4. UPGRADE technical implementation with better TypeScript, performance optimizations, and modern patterns
  5. MAINTAIN backward compatibility while implementing meaningful improvements

📋 FORM UPDATE METHODOLOGY:

STEP 1: Current Form Assessment

Analyze Existing Implementation:
  • Current validation approach: Review existing Zod schemas and validation logic
  • Accessibility audit: Test current ARIA attributes and keyboard navigation
  • User experience gaps: Identify missing loading states, error handling, success feedback
  • Performance issues: Review re-render patterns and optimization opportunities
  • TypeScript completeness: Check interface coverage and type safety
Identify Enhancement Opportunities:
// Assessment checklist for form improvements
interface FormAudit {
  validation: {
    realTimeValidation: boolean;
    serverValidation: boolean;
    customRules: boolean;
    errorRecovery: boolean;
  };
  accessibility: {
    properLabels: boolean;
    ariaDescriptions: boolean;
    keyboardNavigation: boolean;
    screenReaderSupport: boolean;
  };
  userExperience: {
    loadingStates: boolean;
    successFeedback: boolean;
    progressIndicators: boolean;
    autoSave: boolean;
  };
  performance: {
    optimizedRendering: boolean;
    efficientValidation: boolean;
    memoryManagement: boolean;
  };
}

STEP 2: Validation Enhancement Patterns

Advanced Validation Improvements:
// Enhanced validation with contextual feedback
const enhancedFormSchema = z.object({
  email: z.string()
    .min(1, 'Email is required')
    .email('Please enter a valid email address')
    .refine(async (email) => {
      // Server-side validation for uniqueness
      const exists = await checkEmailExists(email);
      return !exists;
    }, 'This email is already registered'),
    
  password: z.string()
    .min(8, 'Password must be at least 8 characters')
    .regex(/^(?=.*[a-z])/, 'Must contain at least one lowercase letter')
    .regex(/^(?=.*[A-Z])/, 'Must contain at least one uppercase letter')
    .regex(/^(?=.*\d)/, 'Must contain at least one number')
    .regex(/^(?=.*[@$!%*?&])/, 'Must contain at least one special character'),
    
  confirmPassword: z.string()
}).refine((data) => data.password === data.confirmPassword, {
  message: "Passwords don't match",
  path: ["confirmPassword"],
});

// Real-time validation with debouncing
const useEnhancedValidation = (schema: ZodSchema) => {
  const [errors, setErrors] = useState<Record<string, string>>({});
  const [isValidating, setIsValidating] = useState<Record<string, boolean>>({});
  
  const validateField = useCallback(
    debounce(async (fieldName: string, value: any) => {
      setIsValidating(prev => ({ ...prev, [fieldName]: true }));
      
      try {
        await schema.shape[fieldName].parseAsync(value);
        setErrors(prev => ({ ...prev, [fieldName]: '' }));
      } catch (error) {
        if (error instanceof ZodError) {
          setErrors(prev => ({ 
            ...prev, 
            [fieldName]: error.errors[0]?.message || 'Invalid value' 
          }));
        }
      } finally {
        setIsValidating(prev => ({ ...prev, [fieldName]: false }));
      }
    }, 300),
    [schema]
  );
  
  return { errors, isValidating, validateField };
};

Read the full file on GitHub · 625 lines

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. 5d ago First seen · 625 lines · 0 tokens per session scan A fc4407c3a051

Subscribe to this mod's changes

component-update-form is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,223 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-08-31.