What is frontend-form-validation?

Guidance for forms that accept solve settings, cube notation, or corrections to stickers read by a scanner. It covers checks made before a request is sent.

Use it when changing solve inputs, limits, validation messages, scanner review controls, or form submission behavior.

It separates simple interface checks from the deeper validation performed by the API and cube engine.

frontend-form-validation — Cursor rule for Cursor by williamisnotdefined: Guidance for forms that accept solve settings, cube notation…

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/williamisnotdefined/rubiks-cube-solver/frontend-form-validation

Clone the repo

git clone --depth 1 https://github.com/williamisnotdefined/rubiks-cube-solver

Made for: Cursor.

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

When invoked 2,483 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.02483
Opus 5	$0.00000	$0.01241
Sonnet 5	$0.00000	$0.00497
Haiku 4.5	$0.00000	$0.00248

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

Security

Grade A, and why

frontend-form-validation 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.

.cursor/rules/frontend-form-validation.mdc · 165 lines

How it starts

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

Generated from ai/registry.json. Do not edit manually.

Canonical skill: ../../ai/skills/frontend-form-validation.md.

Referenced context:

../../ai/rules/frontend-rules.md
../../ai/rules/frontend-form-rules.md
../../ai/rules/frontend-quality-rules.md
../../ai/architecture/api-boundary.md

This file is compiled from canonical AI knowledge files. Edit canonical files under ai, then run npm run ai:sync.

Compiled AI Skill: frontend-form-validation

Canonical Skill: `ai/skills/frontend-form-validation.md`