What problem does it solve? Mixing Node.js server code into React Native client bundles causes build failures, runtime crashes, and security vulnerabilities like client-side password hashing or JWT validation. This Skill detects platform separation violations and guides developers toward compliant import patterns. ## Core Features & Use Cases - Import Path Validation: Checks that React Native files use /client library imports and never pull in Node.js modules like crypto, fs, or bcrypt. - Security Boundary Enforcement: Ensures cryptography, password hashing, and JWT signing remain server-side while clients only parse tokens for UX. - Violation Detection & Fixes: Identifies common anti-patterns (client-side bcrypt, JWT verification, file system access) and provides corrected code examples. - Use Case: When reviewing a pull request that adds authentication to a React Native app, use this Skill to verify all auth-lib imports use /client paths and that password handling goes through API endpoints instead of client-side hashing. ## Quick Start Review the changed files in this pull request for platform separation violations and report any Node.js imports or client-side crypto operations.