Cross-Layer Check

What problem does it solve?

This Skill helps you prevent subtle defects that appear when UI, API/services, and data layers don’t agree on schemas, flows, error handling, or shared constants.

Core Features & Use Cases

• Cross-layer data flow verification (A): Ensures read/write flows and type/schema propagation across Database → Service → API → UI are correct, including error propagation and loading/pending handling.
• Code reuse enforcement (B/B2/B3): Encourages searching for existing constants/utilities and prevents incomplete batch refactors that leave duplicates behind.
• Dependency-path and same-layer consistency checks (C/D): Validates import/dependency structure when adding files and checks formatting/display logic consistency for the same domain concept across the codebase.

Use case example: After implementing a new feature that touches routes/handlers, business services, and database models, use this Skill to verify that data and types are correctly threaded end-to-end and that related UI constants or formatting rules weren’t duplicated inconsistently.

Quick Start

Run the Cross-Layer Check after your changes to generate a report covering which dimensions you touched, the checklist outcomes, and any issues with concrete fix suggestions.