What problem does it solve? Developers building DaaS applications often recreate UI elements that already exist in the Buildpad component library, leading to inconsistent patterns, raw Mantine misuse, and runtime crashes in React Server Components. This Skill enforces a Buildpad-first workflow so generated components reuse the existing 40+ component catalog and follow platform conventions. ## Core Features & Use Cases - Buildpad-First Enforcement: Before generating any .tsx file, it requires reading the Buildpad component reference and checking whether an existing component (Input, SelectDropdown, CollectionList, VForm, etc.) already covers the need. - Pattern-Compliant Generation: Produces TypeScript strict-mode components with JSDoc, correct 'use client' directives for Mantine usage, and proper imports from @/components/ui and @/lib/buildpad. - Post-Generation Validation: Runs a grep-based violation scan to detect forbidden raw Mantine imports (TextInput, Select, DatePicker, useForm) and maps each violation to its Buildpad replacement. - Use Case: When asked to build a new record listing page, the Skill directs you to use CollectionList with search, FilterPanel, permission-gated actions, and pagination instead of hand-rolling a Mantine table. ## Quick Start Ask the assistant to create a new React component such as a batch detail card for the DaaS app, specifying the component name and type.