pimcore-studio-ui-react-components

Standardize Pimcore Studio UI React component structure with .styles.tsx files and interfaces.

13|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/pimcore/skills --skill pimcore-studio-ui-react-components
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pimcore-studio-ui-react-components
Source: https://github.com/pimcore/skills/tree/main/skills/pimcore-studio-ui-react-components
Command: npx skills add https://github.com/pimcore/skills --skill pimcore-studio-ui-react-components

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pimcore Studio UI component development often lacks a unified structure and clear conventions; this Skill provides a standardized approach to building, organizing, and maintaining React components within Pimcore Studio UI to ensure consistency and quality across projects.

Core Features & Use Cases

  • Component file structure and folder organization: enforce a folder-per-component layout to group related files (tsx, styles, stories).
  • CSS-in-JS with separate styles file: mandate a dedicated .styles.tsx for all component styling using the antd-style approach.
  • Props typing with interfaces: require explicit TypeScript interfaces for component props to improve type safety and editor guidance.
  • ForwardRef and advanced patterns: outline patterns for forwardRef, memoization, and render strategy for complex components.
  • Export patterns and composition: define export conventions and how to compose sub-components under a single module.

Quick Start

Create a new component under the Pimcore Studio UI components directory following the folder structure with a main .tsx file and a separate .styles.tsx file.

Frequently Asked Questions about pimcore-studio-ui-react-components

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

FAQPage Schema
How do I structure React components in Pimcore Studio UI to maintain consistency across projects?

React components in Pimcore Studio UI should use a folder-per-component layout, grouping the main tsx file, styles, and stories together. This enforces clear conventions and ensures consistency across projects by keeping related files organized.

What is the best way to manage CSS-in-JS styling for Pimcore Studio UI components?

CSS-in-JS for Pimcore Studio UI components should use a dedicated .styles.tsx file. This approach mandates separate styling files using the antd-style method, keeping component logic and styles decoupled for better maintainability.

How do I define prop interfaces for TypeScript React components in Pimcore Studio UI?

Prop interfaces for TypeScript React components in Pimcore Studio UI require explicit TypeScript interfaces. This improves type safety and editor guidance by clearly defining expected props, ensuring robust typing across the application.

When should I use forwardRef and memoization patterns for React components?

Use forwardRef and memoization patterns for React components when building complex elements requiring advanced render strategies. Outlining these patterns in Pimcore Studio UI ensures optimal performance and proper ref forwarding in intricate component hierarchies.

Does Pimcore Studio UI require specific export patterns for composing sub-components?

Pimcore Studio UI defines specific export conventions for composing sub-components under a single module. This ensures a unified folder-based structure and predictable import behavior across the codebase.

Why do my existing Pimcore Studio UI components lack a unified structure and clear conventions?

Existing Pimcore Studio UI components lack a unified structure because development often proceeds without standardized conventions. Applying a structured approach with explicit prop interfaces, forwardRef support, and separate styles files solves this inconsistency and ensures quality.