check-cross-layer

To verify cross-layer consistency after modifying shared constants, run a post-edit verification check to surface missed update sites, type mismatches, and duplicated constants across API, service, and UI layers.

Cross-layer data-flow verification is the process of validating input and output consistency across API, service, and UI layers to ensure architectural integrity and correct data handling after code changes.

To check import-path validity after batch file changes, run an automated verification skill that analyzes code reuse and validates import paths to catch misaligned interfaces and potential inconsistencies.

Yes, cross-layer verification detects type mismatches between API and UI layers by analyzing data flow and same-layer consistency to enforce correct architecture and surface missed updates.

You need to run cross-layer integrity checks after performing batch file changes or modifying shared constants and configs to ensure full consistency and identify any missed update sites across the architecture.

The best way to catch duplicated constants is to perform same-layer consistency checks that identify misaligned interfaces and duplicated values, enforcing correct architecture across API, service, and UI layers.