A project rules document for consistent user-interface patterns in authentication forms, including validation, one-time password fields, and resend timers. TypeScript and Tailwind CSS are the project's specified tools.

Use it when building sign-up or other authentication screens, multi-step forms, one-time password inputs, validation, or resend controls.

It reduces inconsistent form behavior and visual differences by documenting the patterns the project already uses.

ui-patterns — Cursor rule by proSamik

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/prosamik/starterkit-nextjs-polar-betterauth-postgres/ui-patterns

Clone the repo

git clone --depth 1 https://github.com/proSamik/starterkit-nextjs-polar-betterauth-postgres

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 1,366 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.01366
Opus 5	$0.00000	$0.00683
Sonnet 5	$0.00000	$0.00273
Haiku 4.5	$0.00000	$0.00137

Measured 3d ago against content hash 63e08480476b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ui-patterns 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 3d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

ui-patterns — 100% identical, 0 lines differ

.cursor/rules/ui-patterns.mdc · 247 lines

How it starts

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

UI Patterns and Components Guide

Overview

This project follows consistent UI patterns for authentication flows, form handling, and user feedback. All components use modern React patterns with TypeScript and Tailwind CSS.

Form Components and Patterns

State Management

Uses custom hook src/hooks/use-object-state.ts:

const [formData, setFormData] = useObjectState({
  email: "",
  password: "",
  otp: ""
});

// Update specific fields
setFormData({ email: "[email protected]" });

Resend Cooldown Hook

Custom hook src/hooks/use-resend-cooldown.ts:

const {
  isOnCooldown,
  formatCooldownTime,
  startCooldown,
} = useResendCooldown();

// Usage in component
{isOnCooldown 
  ? `Resend in ${formatCooldownTime()}`
  : "Didn't receive the code? Resend"
}

Authentication UI Components

Multi-Step Forms

Pattern used in src/app/(auth)/sign-up/page.tsx:

Step-based navigation with progress indicators
Back button functionality with proper state management
Conditional rendering based on current step
Form validation at each step

OTP Input Fields

Standardized OTP input pattern:

<Input
  type="text"
  placeholder="000000"
  value={state.otp}
  onChange={(e) => setState({ 
    otp: e.target.value.replace(/\D/g, "").slice(0, 6) 
  })}
  maxLength={6}
  className="text-center text-lg tracking-widest"
/>

Loading States

Consistent loading pattern with Lucide icons:

<Button disabled={loading}>
  {loading && <Loader className="mr-2 h-4 w-4 animate-spin" />}
  Button Text
</Button>

Card Layout Pattern

Standard Auth Card

Used across all auth pages:

<Card className="w-full max-w-md">
  <CardHeader className="space-y-1">
    <CardTitle className="text-2xl font-bold tracking-tight">
      Page Title
    </CardTitle>
    <CardDescription>
      Page description
    </CardDescription>
  </CardHeader>
  <CardContent className="space-y-4">
    {/* Form content */}
  </CardContent>
</Card>

Read the full file on GitHub · 247 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.

3d ago First seen · 247 lines · 0 tokens per session scan A 63e08480476b

Subscribe to this mod's changes

ui-patterns is a cursor rule published in the GitHub repository proSamik/starterkit-nextjs-polar-betterauth-postgres (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,366 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.

ui-patterns