Borrowing it
Nothing to install: this file belongs to williamisnotdefined/rubiks-cube-solver. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/williamisnotdefined/rubiks-cube-solver/main/.github/instructions/frontend-state-management.instructions.mdgit clone --depth 1 https://github.com/williamisnotdefined/rubiks-cube-solverWrote 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.
[](https://agentmods.dev/instructions/williamisnotdefined/rubiks-cube-solver/frontend-state-management)<a href="https://agentmods.dev/instructions/williamisnotdefined/rubiks-cube-solver/frontend-state-management"><img src="https://agentmods.dev/badge/instructions/williamisnotdefined/rubiks-cube-solver/frontend-state-management.svg" alt="Measured on agentmods" height="20"></a>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.1 | $0.02878 | $0.02878 |
| Opus 5 | $0.01439 | $0.01439 |
| Sonnet 5 | $0.00576 | $0.00576 |
| Haiku 4.5 | $0.00288 | $0.00288 |
Grade A, and why
rubiks-cube-solver frontend-state-management.instructions.md 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 209 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-state-management.md.
Referenced context:
../../ai/rules/frontend-rules.md../../ai/rules/frontend-state-rules.md../../ai/rules/frontend-quality-rules.md../../ai/architecture/frontend-visualization.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-state-management
Canonical Skill: ai/skills/frontend-state-management.md
Frontend State Management
Use for React state, custom hooks, stores, async workflow state, and visualization synchronization.
Read First
ai/rules/frontend-rules.mdai/rules/frontend-state-rules.mdai/rules/frontend-quality-rules.mdai/architecture/frontend-visualization.md
Workflow
- Classify the state and assign its nearest owner before moving it.
- Keep server state in React Query, scoped shared client state in existing Zustand stores only when needed, and imperative rendering details in refs/hooks.
- Define reset, cancellation, and stale-response behavior at the owner.
- Verify the changed workflow and web build.
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-cubepackage as a visualization adapter, never as canonical solver state.
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.
- 6d ago First seen · 209 lines · 2,878 tokens per session scan A e93d8e3e31b7
rubiks-cube-solver frontend-state-management.instructions.md is an instructions file published in the GitHub repository williamisnotdefined/rubiks-cube-solver (4 stars, last pushed 6d ago), licensed MIT. It adds 2,878 tokens to every session, about $0.0144 per session on Opus 5. 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.