frontend-r2-connection

Audit CrashLens front-end R2 folder paths and iframe synchronization across jurisdiction tiers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ecomhub200/Douglas_County_2 --skill frontend-r2-connection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-r2-connection
Source: https://github.com/ecomhub200/Douglas_County_2/tree/main/.claude/skills/frontend-r2-connection
Command: npx skills add https://github.com/ecomhub200/Douglas_County_2 --skill frontend-r2-connection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Front-end R2 folder structure and path mapping, auditing iframe synchronization, and tier-aware routing across jurisdictions for CrashLens applications.

Core Features & Use Cases

  • Understand how CrashLens front-end connects to Cloudflare R2 storage and how folder paths are constructed.
  • Verify R2 path mappings across tiers (federal, state, region, mpo, planning district, city, county) and ensure alignment with create_r2_folders.py.
  • Audit iframe modules' R2 sync and ensure consistent data flow between parent app and iframes.

Quick Start

Use this skill to perform a quick, tier-aware audit of the R2 folder structure and path mappings for a sample jurisdiction.

Frequently Asked Questions about frontend-r2-connection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Cloudflare R2 folder paths and verify tier mappings in a frontend application?

To audit Cloudflare R2 folder paths in a frontend application, verify the tiered path mappings across seven jurisdiction tiers and ensure alignment with the create_r2_folders.py structure. This validates correct R2 uploads and downloads for jurisdictions.

How does iframe synchronization work with R2 storage across different jurisdiction tiers?

Iframe synchronization with R2 storage works by ensuring consistent data flow between the parent app and iframe modules. It audits the R2 sync to maintain correct path construction across federal, state, region, mpo, planning district, city, and county tiers.

What is the best way to debug R2 upload and download path inconsistencies in a multi-tier architecture?

The best way to debug R2 upload and download path inconsistencies is to audit the front-end folder structure and path construction logic. This process validates tier-aware routing and checks fallback behaviors for standalone use.

Can I use this approach to onboard new states into an existing R2 folder structure?

Yes, you can onboard new states by applying the comprehensive mapping rules to verify the R2 folder structure. This ensures the new state's path mappings align correctly with the parent app messaging and existing jurisdiction tiers.

Why does my frontend R2 path mapping fail when used standalone without the parent app?

Frontend R2 path mapping fails standalone when fallback behaviors are not properly configured. Auditing the iframe synchronization and mapping rules ensures standalone use correctly falls back without breaking tier-aware routing or data flow.

Do I need create_r2_folders.py to maintain consistent path mapping across jurisdiction tiers?

Yes, you need create_r2_folders.py to ensure consistency across jurisdiction tiers. Auditing path mappings against this file validates that the frontend R2 folder structure aligns with the backend architecture for uploads and downloads.