dextinity-admin-ui

Build admin UI pages, forms, and grids with @dextinity/admin components and theme.

52|9|Updated Mar 4, 2019
One-click install
npx skills add https://github.com/vivid-planet/dextinity --skill dextinity-admin-ui-vivid-planet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dextinity-admin-ui
Source: https://github.com/vivid-planet/dextinity/tree/main/skills/dextinity-admin-ui
Command: npx skills add https://github.com/vivid-planet/dextinity --skill dextinity-admin-ui-vivid-planet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When building admin interfaces in a project using @dextinity/admin, developers often fall back to custom sx props, inline styles, hard-coded pixel values, and Box-based layouts, which produces inconsistent screens and markup that is hard to review and upgrade. This Skill guides the AI to always prefer Dextinity's theme tokens, ready-made components, and helpers over hand-written CSS. ## Core Features & Use Cases - Component-first UI construction: Use Dextinity components such as MainContent, Toolbar, FieldSet, FormSection, DataGrid, Alert, Dialog, and specialized buttons (SaveButton, DeleteButton) instead of assembling equivalents from Box and custom CSS. - Theme-driven styling: Apply spacing, palette, elevation, and typography tokens from the Dextinity theme, write custom styling only with named styled() components, and customize existing components through slotProps or theme styleOverrides. - Internationalization and layout: Format text, numbers, and dates with react-intl helpers, and arrange content with Stack and Grid rather than manual margins and flex math. - Use Case: When asked to add a dashboard page with a data grid, toolbar actions, and a form dialog, the Skill produces markup built from StackMainContent, Toolbar parts, FieldSet, and Dextinity pickers, with all text translated via FormattedMessage. ## Quick Start Build an admin page with a toolbar, a full-height data grid, and a save form using @dextinity/admin components and theme values instead of custom CSS.

Frequently Asked Questions about dextinity-admin-ui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I style components in a @dextinity/admin project?

Prefer Dextinity theme tokens and component props over custom CSS. When custom styling is needed, use styled() from @mui/material/styles with a named component, reading spacing and colors from the theme rather than hard-coding pixels or hex values.

How do I build a page layout with toolbar and data grid in Dextinity admin?

Use Toolbar with ToolbarTitleItem, FillSpace, and ToolbarActions for the action bar, and wrap the page body in MainContent or StackMainContent. For a full-height DataGrid, add the fullHeight prop or wrap it in FullHeightContent.

Should I use sx prop or styled() for custom styling in MUI-based admin apps?

Use styled() with a descriptive name for custom styling, keeping it separate from markup. The sx prop is acceptable only for occasional layout properties like flexGrow that Stack or Grid props do not cover.

How do I change the appearance of a Dextinity Admin component?

Configure the theme via createDextinityTheme's components map using the DextinityAdmin* key with styleOverrides or defaultProps, which applies to every instance. Use slotProps to forward props to a named inner slot for behavior changes.

How do I translate text and format dates in a Dextinity admin UI?

Use react-intl: FormattedMessage for text, useIntl().formatMessage() for string attributes like alt and placeholder, and FormattedNumber, FormattedDate, or FormattedTime for locale-aware number and date rendering.

When is custom CSS acceptable instead of Dextinity components?

Only when no component, prop, theme token, or helper can produce the result, or when explicitly instructed. Deliberate project-specific design differences should be applied through theme styleOverrides rather than per-instance styling.