skills.rest
dgoldoff-hue
dgoldoff-hueCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

jackie-report-recovery

Recover stale Jackie property reports by patching shared normalization and caches.

Updated Aug 8, 2026
Search Tags:#state synchronization#report recovery#stale cache#PDF/HTML generation#image fallback#localStorage repair#Render deployment verification
One-click install
npx skills add https://github.com/dgoldoff-hue/camelot-scout-v6 --skill jackie-report-recovery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jackie-report-recovery
Source: https://github.com/dgoldoff-hue/camelot-scout-v6/tree/main/.codex/skills/jackie-report-recovery
Command: npx skills add https://github.com/dgoldoff-hue/camelot-scout-v6 --skill jackie-report-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you recover from recurring issues where Jackie-generated property reports show stale or incorrect facts, titles, unit counts, images, or exported output that doesn’t match the latest code or data.

Core Features & Use Cases

  • Stale-source triage: Pinpoints whether wrong values originate from UI state, report generation archives, Supabase rows, localStorage, or deployed build drift.
  • Shared normalization guardrails: Introduces property-specific validation and normalization in a shared helper so fixes apply consistently across property cards, Results, Report Center, email/proposal generation, and Jackie package generation.
  • Cache and persisted-state repair: Identifies and rewrites known localStorage caches (e.g., buildings, report libraries, proposal/report libraries, uploaded-photo keys) and clarifies when hard refresh is required.
  • Render and image resilience: Prevents broken base64 images from blocking report exports by downgrading dirty payloads to warnings and using safe fallbacks or static property images.
  • Verification and deployment reality checks: Runs targeted searches for stale visible text, executes verification scripts, confirms builds, and verifies the live Render output matches merged code.

Quick Start

Run the stale-text search, fix the shared normalization helper under src/lib/, then execute npm run verify:jackie and a fresh npm run build before hard-refreshing the deployed page to confirm the live output matches the corrected facts.

Frequently Asked Questions about jackie-report-recovery

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

FAQPage Schema
Why do property reports show stale facts and incorrect images after a deployment?▼

Stale property facts in reports usually originate from persisted localStorage caches, Supabase row conflicts, or deployed build drift. Triage involves searching across src/public/.codex/dist to pinpoint whether wrong values come from UI state, report archives, or deployed Render output.

How do I fix stale property facts in generated PDF and HTML reports?▼

To fix stale property facts, locate outdated values across src/public/.codex/dist, patch the shared normalization helper under src/lib/, execute npm run verify:jackie, run a fresh npm run build, and hard-refresh the deployed Render page to confirm corrected output.

How do I repair localStorage and Supabase records that conflict with report generation?▼

Repairing localStorage and Supabase-conflicted records involves identifying and rewriting known localStorage caches like buildings, report libraries, and uploaded-photo keys. This ensures report generation archives and UI state synchronize with latest data without manual cache deletion.

What is the best way to prevent broken base64 images from blocking report exports?▼

Preventing broken base64 images from blocking report exports requires adding image guardrails that downgrade dirty payloads to warnings. The system then uses safe fallbacks or static property images, allowing PDF and HTML generation to complete despite invalid image data.

Does shared normalization work for both property card rendering and email proposal generation?▼

Shared normalization applies consistently across property card rendering, Results, Report Center, email intro, proposal generation, and Jackie package outputs. Introducing property-specific validation in a shared helper ensures fixes apply uniformly across all display and generation paths.

How do I verify that live Render deployment output matches merged code changes?▼

Verifying live Render deployment output involves running targeted searches for stale visible text, executing verification scripts, confirming successful builds, and checking the deployed page after a hard refresh to ensure live output matches corrected facts.

Related Skills

Explore More Software Engineering Skills→
freedomw1987freedomw1987
2

docker-multi-stage-dist-overwrite

Fix stale dist/ overwrites in Docker multi-stage builds with .dockerignore files.

Community
Intermediate
Adelie-SquadAdelie-Squad
17

build-test

Run npx tsc --noEmit and npm run build, then verify dist/bin/solo-agents.js exists.

Official
Intermediate
ccfccf

nx-workspace-patterns

Codify Nx workspace patterns for monorepo setup, boundary enforcement, and caching.

Community
Advanced
machenjiemachenjie
4

state-management-design

Design frontend state ownership and synchronization strategies for React-like applications.

Community
Advanced