What problem does it solve?
It solves inconsistent, unreliable, or non-scalable admin UI implementations in VTEX IO by enforcing VTEX Admin design-system patterns, explicit UX states, and safe interaction patterns.
Core Features & Use Cases
- VTEX design-system compliance for Admin: Prefer
vtex.styleguide (default) and allow @vtex/shoreline for official VTEX admin contexts while avoiding generic third-party UI libraries in Admin apps.
- Admin UX guardrails: Ensure admin pages expose loading, empty, and error states; provide clear feedback for async mutations; and use accessible semantics via design-system components.
- Scalable data-heavy interfaces: Use bounded rendering patterns like paginated tables and prefer server-side filtering for large datasets.
Use case example: Implement an admin dashboard for moderating submissions where tables remain performant, users always see what’s happening (loading/empty/error), and save actions report success or failure.
Quick Start
Apply this skill when generating an admin settings page for a VTEX IO app that uses VTEX Admin layout components and must include loading, empty, and error states plus toast/feedback for mutations.