What problem does it solve?
This Skill eliminates inconsistent frontend implementation in Atomic CRM by providing clear, standardized conventions for component creation, data fetching, and responsive design, reducing bugs and cutting down onboarding time for new developers working on the project.
Core Features & Use Cases
- Standardized Component Architecture: Clear separation between admin logic components (imported from @/components/admin/) and pure UI components (imported from @/components/ui/), ensuring consistent integration with ra-core.
- Consistent CRUD Resource Structure: Enforces a standard file layout for all CRM resources, including list, show, edit, create, and shared input components, with mandatory registration in the root CRM configuration.
- Responsive Design Guidelines: Built-in rules for implementing both desktop and mobile variants of major pages, using useIsMobile() to branch layouts appropriately for different screen sizes.
- Use Case: When building a new contact management feature, this Skill ensures you use the correct input components, follow the standard resource file structure, implement both desktop and mobile layouts, and avoid common pitfalls like hardcoding domain values or making bespoke API calls.
Quick Start
Use the frontend-dev skill to build a new contact list page that adheres to Atomic CRM's frontend coding standards and responsive design requirements.
