dev-parity-guard

Validate script integrity, API proxy routing, and image delivery paths against production save points.

Updated Nov 9, 2025

Search Tags:#automation #devops #api #validation #regression #proxy #parity

Ready to run

npx skills add https://github.com/canyouseeus/thelostandunfounds --skill dev-parity-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-parity-guard
Source: https://github.com/canyouseeus/thelostandunfounds/tree/main/.agent/skills/dev-parity-guard
Command: npx skills add https://github.com/canyouseeus/thelostandunfounds --skill dev-parity-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains parity between development and production environments by validating scripts, proxies, and project structure to prevent regressions.

Core Features & Use Cases

Verify Script Integrity: ensure the dev script in package.json uses vercel dev to expose API routes.
API Proxying Validation: confirm vite.config.ts proxies /api/gallery and /api/photos to http://localhost:3001.
Secure Image Delivery: enforce using /api/gallery/stream endpoints for large assets instead of direct Drive URLs.
Root-Directory Execution: ensure commands are run from the repository root, not user home.

Quick Start

Run the parity validation workflow from the repository root to verify local parity with production.

Frequently Asked Questions about dev-parity-guard

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

FAQPage Schema

How do I prevent regressions between my development and production environments?▼

To prevent regressions between development and production environments, validate script integrity, API proxy routing, and image delivery paths against production save points to ensure full parity.

Why does my Vite proxy configuration fail API routing in local development?▼

Vite proxy configuration fails API routing when vite.config.ts does not properly proxy /api/gallery and /api/photos to http://localhost:3001, breaking local development parity with production.

How do I verify that my dev script uses Vercel dev to expose API routes?▼

To verify your dev script uses Vercel dev to expose API routes, check package.json script integrity and ensure commands execute from the repository root, not the user home directory.

What is the best way to secure image delivery paths for large assets?▼

The best way to secure image delivery paths for large assets is to enforce using /api/gallery/stream endpoints instead of direct Drive URLs, maintaining alignment with production save points.

Do I need to run parity checks from the repository root or user home?▼

You need to run parity checks from the repository root, not the user home directory, to ensure build-time and runtime alignment with the production save point and prevent execution errors.

Does dev-parity-guard work with Vite and Vercel configurations?▼

dev-parity-guard works with Vite and Vercel configurations by validating vite.config.ts proxy rules and verifying package.json dev scripts use vercel dev to expose local API routes.