admin-only-notus

Admin pages require strict isolation from public-facing pages, meaning they cannot share any layout, design, or asset files. This separation prevents cross-contamination and maintains distinct visual systems for internal versus external users.

Design drift occurs when admin pages in React Native gradually deviate from the established Notus design system through inconsistent color, component, or layout choices. Enforcing standardized design rules prevents this visual fragmentation across internal application interfaces.

No, the Notus design system enforces an isolation rule where admin pages cannot share layout, design, or asset files with public-facing pages. You must maintain separate visual structures to prevent design drift between internal and external interfaces.

To apply Notus React design rules to an admin dashboard component like adminDashboard.tsx, you run the enforcement skill which validates color palettes, component usage, and layout against the design system before deployment.

Yes, admin routing is a required dependency before enforcing the Notus React design system on internal pages. You must have routing configured to properly isolate and manage admin page navigation within Goliath React Native Expo applications.

A pre-flight checklist verifies that all Notus design system rules are followed before deploying an admin page, covering color palette adherence, proper component usage, layout consistency, and isolation from public-facing page assets.