frontend-visualization

Guidance for the part of a web app that draws a Rubik’s Cube, plays moves, and shows results from a cube scanner.

In plain words
What is it for?
Use it when changing cube displays, move playback, visualization adapters, or the interface that shows scanned cube stickers.
Why use it?
It keeps rendering, playback, and scanner behavior consistent with the project’s cube-solving engine and data rules.

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/williamisnotdefined/rubiks-cube-solver/frontend-visualization
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,838 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 86% copy Near-identical to another mod 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.02838
Opus 5 $0.00000 $0.01419
Sonnet 5 $0.00000 $0.00568
Haiku 4.5 $0.00000 $0.00284

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

Security

Grade A, and why

frontend-visualization 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 2d 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

This is a copy

86% identical to frontend-state-management — 106 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/frontend-visualization.mdc · 199 lines

How it starts

The opening of the file, as written. The whole thing — 199 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-visualization.md.

Referenced context:

  • ../../ai/rules/frontend-rules.md
  • ../../ai/rules/frontend-quality-rules.md
  • ../../ai/architecture/frontend-visualization.md
  • ../../ai/architecture/rubiks-cube-visualization-package.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-visualization

Canonical Skill: ai/skills/frontend-visualization.md

Frontend Visualization

Use for cube rendering, playback, visualization adapters, or scan visualization.

Read First

  • ai/rules/frontend-rules.md
  • ai/rules/frontend-quality-rules.md
  • ai/architecture/frontend-visualization.md
  • ai/architecture/rubiks-cube-visualization-package.md

Workflow

  • Identify the owning puzzle/page context and preserve the Rust solver boundary.
  • Use the active package's narrow puzzle subpath; keep imperative rendering sync in focused hooks/refs.
  • Keep scanner evidence and reviewed stickers in typed scan contracts, with disclosure before camera permission and automatic analysis after permission.
  • Verify rendering, cancellation, accessibility, reduced motion, mobile sizing, and the relevant solve/scan E2E flow.

Referenced Context

Reference: ai/rules/frontend-rules.md

Frontend Rules

Boundaries

  • Keep solving, notation semantics, puzzle validity, and replay verification in Rust. React renders and coordinates typed product workflows.
  • Keep HTTP mechanics and normalization in apps/web/src/api; UI consumes domain hooks/adapters.
  • Typed scan-session contracts MAY contain reviewed stickers, confidence, and manual overrides. Notation solve UI MUST NOT expose facelet, Kociemba, or raw cube-state inputs.
  • Keep API load, form, page workflow, solve result, scanner review, and visualization playback state separately owned unless a focused page owner coordinates them.
  • Use the active @rubiks-cube-solver/rubiks-cube package as a visualization adapter, never as canonical solver state.

Read the full file on GitHub · 199 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. 2d ago First seen · 199 lines · 0 tokens per session scan A 2d13eb7a0a8f

Subscribe to this mod's changes

frontend-visualization is a cursor rule published in the GitHub repository williamisnotdefined/rubiks-cube-solver (4 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,838 tokens. A static security scan graded it A with 0 findings. It is 86% identical to frontend-state-management, differing in 106 lines, and is treated as a copy.