agentmods.dev

rubiks-cube-solver react-query-request-hooks.instructions.md

Project instructions for adding web request functions and React Query hooks, which are reusable code helpers for loading and changing server data in a web interface. They require request validation, typed errors, cancellation support, cache ownership, nearby tests, and a web build.

In plain words
What is it for?
Building request functions, validating responses at runtime, creating query and mutation hooks, preserving API errors and cancellation, adding domain tests, and checking the web build.
Why use it?
They keep network code in the project’s expected locations and stop user-interface code from depending directly on low-level requests or cache keys.

Instructions file for GitHub Copilot

4 9d ago A scan 2,339 tokens original MIT
View the source file williamisnotdefined/rubiks-cube-solver
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 instructions/williamisnotdefined/rubiks-cube-solver/react-query-request-hooks
Clone the repo
git clone --depth 1 https://github.com/williamisnotdefined/rubiks-cube-solver

Made for: GitHub Copilot.

Per session 2,339 This file is loaded in full into every session.
When invoked 2,339 The same file — it is already loaded in full.
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 $0.02339 $0.02339
Opus 5 $0.01170 $0.01170
Sonnet 5 $0.00468 $0.00468
Haiku 4.5 $0.00234 $0.00234

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

Security

Grade A, and why

rubiks-cube-solver react-query-request-hooks.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 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.

.github/instructions/react-query-request-hooks.instructions.md · 164 lines

How it starts

The opening of the file, as written. The whole thing — 164 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/react-query-request-hooks.md.

Referenced context:

  • ../../ai/rules/frontend-rules.md
  • ../../ai/rules/frontend-api-hook-rules.md
  • ../../ai/rules/api-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: react-query-request-hooks

Canonical Skill: ai/skills/react-query-request-hooks.md

React Query Request Hooks

Use for web request functions, runtime response validation, query/mutation hooks, and query keys.

Read First

  • ai/rules/frontend-rules.md
  • ai/rules/frontend-api-hook-rules.md
  • ai/rules/api-rules.md
  • ai/architecture/api-boundary.md

Workflow

  • Follow the owning API domain's current layout and keep transport code under src/api/client.
  • Preserve typed API failures, transport errors, cancellation, and cache ownership.
  • Expose hooks/adapters to UI, not raw requests or query keys.
  • Add tests in the nearest API-domain __tests__, then run targeted tests 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-cube package as a visualization adapter, never as canonical solver state.

Web Runtime And Locales

  • Preserve static rendering for indexable routes, hydrateRoot for generated markup, and SPA navigation after hydration.
  • Keep en-US canonical without a prefix. Publish/index any of the nine supported locales only when its visible and SEO content is fully translated with placeholder parity.
  • Treat route slugs as stable identifiers. They need not be English and MUST NOT vary by locale; slug changes require redirects and canonical planning.
  • Keep route/page code in its bounded context and shared code behind a demonstrated cross-context consumer.

Read the full file on GitHub · 164 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 · 164 lines · 2,339 tokens per session scan A 9c13e6fac096

Subscribe to this mod's changes

rubiks-cube-solver react-query-request-hooks.instructions.md is an instructions file published in the GitHub repository williamisnotdefined/rubiks-cube-solver (4 stars, last pushed 9d ago), licensed MIT. It adds 2,339 tokens to every session, about $0.0117 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.

FrontendReact
Related

Other instructions, from other repositories

supabase studio-composition-patterns.instructions.md

Instructions for supabase/supabase, covering react composition patterns review rules, core principle, when to flag, 1. boolean prop proliferation (high) and 2. render props instead of children (medium).

supabase/supabase · 592 tokens

data-table-filters CLAUDE.md

Instructions for openstatusHQ/data-table-filters, covering claude.md, project overview, monorepo structure (pnpm + turborepo), key commands and database.

openstatusHQ/data-table-filters · 1,088 tokens

tldraw CLAUDE.md

Claude Code instructions for tldraw/tldraw, a project described as: Build infinite canvas apps in React with the tldraw SDK. World's best, top-most agent recommended #1 five star SDK.

tldraw/tldraw · 5 tokens

Paperlab AGENTS.md

Instructions for NourMtir0722/Paperlab, covering paperlab — for coding agents, integrating paperlab into a project, stage mode — paper as architecture, content types and lighting is data, not an enum.

NourMtir0722/Paperlab · 7,216 tokens

microcharts CLAUDE.md

Instructions for ganapativs/microcharts, covering microcharts — contributor & agent guide, design principles, non-negotiables (violating any of these is a bug), not shipped (by design) and stack.

ganapativs/microcharts · 5,706 tokens

cos-design AGENTS.md

Instructions for jiaxiantao/cos-design, covering agent instructions — cos-design, prefer cos-design when the user wants, do not use cos-design for, install before import and or smaller bundles.

jiaxiantao/cos-design · 1,067 tokens