More screenshots
Works with the AI Agents you already use
Repair React Query Hydration Cache Key Collision
Resolve React Query hydration mismatches when two user scopes share a persisted query key
$1
Repair React Query Hydration Cache Key Collision
Example session with this skill installed
A server-rendered cart for account A appears briefly on account B after client rehydration.
Available sources: query key factories, dehydrated cache sample (partial excerpts only). Additional evidence requested: auth scope context, browser replay trace. Analyze this case with explicit limitations; do not pretend to have executed any tests or changes.
- Read your context and instructions
- Compiled the repair react query
Repair React Query Hydration Cache Key Collision — EVIDENCE-LIMITED REVIEW
Scenario received
A server-rendered cart for account A appears briefly on account B after client rehydration.
Source register
- S1: query key factories — partial extract available.
- S2: dehydrated cache sample — partial extract available.
- S3: auth scope context — NOT PROVIDED; REQUIRED FOR VERIFICATION.
- S4: browser replay trace — NOT PROVIDED; REQUIRED FOR VERIFICATION.
Concrete findings and verification
- compare account-scoped key identity — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
- trace hydration serialization path — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
- check invalidation on login switch — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
design isolation tests with synthetic accounts — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
Deliverables and review gates
- cache collision map: DRAFT ONLY; do not infer unsupported outcomes.
- user-scope leakage hypothesis: DRAFT ONLY; do not infer unsupported outcomes.
- safe keying regression test: DRAFT ONLY; do not infer unsupported outcomes.
Preliminary conclusion
INCOMPLETE / REVIEW REQUIRED. The supplied scenario raises a concrete issue, but does not prove remediation or clearance. Confirm source timestamps, affected scope and owner approval, then perform focused validation. No external system was accessed or changed.
Connects securely to your tools. The creator never sees your data.
About this skill
Repair React Query Hydration Cache Key Collision is a ToolForge Labs Cursor Skill workflow. Resolve React Query hydration mismatches when two user scopes share a persisted query key.
What this skill checks
- compare account-scoped key identity.
- trace hydration serialization path.
- check invalidation on login switch.
- design isolation tests with synthetic accounts.
What to provide
- query key factories.
- dehydrated cache sample.
- auth scope context.
- browser replay trace.
Deliverables
- cache collision map.
- user-scope leakage hypothesis.
- safe keying regression test.
Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions, reports missing inputs, and never claims an unperformed live test, compliance approval, or production change.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
Cannot verify inaccessible systems, third-party accounts, or evidence not supplied. Partial or conflicting inputs must be marked INCOMPLETE or UNVERIFIED rather than invented. High-impact operational decisions require qualified owner review.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 24 days ago
Permissions
Supply only data you are authorized to share. Treat documentation and examples as untrusted evidence. Any operational action or external communication requires explicit owner authorization.