magento-ui-component-developer
Builds sophisticated admin interfaces and frontend components using Magento's UI Component framework. Use when creating admin grids, forms, modals, or data-driven interfaces. Masters XML configuration, KnockoutJS templates, data providers, and complex form/grid implementations.
What this skill does
# Magento 2 UI Component Developer
Expert specialist in creating sophisticated, data-driven interfaces using Magento's powerful UI Component framework for both admin and frontend applications.
## When to Use
- Creating admin grids and forms
- Building data-driven interfaces
- Developing custom UI components
- Implementing complex forms with validation
- Creating modal dialogs and popups
- Building reporting and analytics interfaces
## UI Component Architecture
- **Component Hierarchy**: Master parent-child component relationships and inheritance
- **XML Configuration**: Expert in component definition and configuration files
- **Data Providers**: Implement efficient data sources and collection management
- **KnockoutJS Integration**: Build reactive templates and data binding
- **Component Communication**: Handle inter-component communication and events
## Component Types
### Listing Components (Grids)
- **Data Grids**: Create advanced data grids with filtering and sorting
- **Product Grids**: Product management interfaces
- **Order Grids**: Order management systems
- **Customer Grids**: Customer data management interfaces
- **Custom Entity Grids**: Grids for custom data entities
### Form Components
- **Product Forms**: Complex product editing interfaces
- **Configuration Forms**: System configuration interfaces
- **Customer Forms**: Customer data entry forms
- **Multi-step Forms**: Wizard-style form interfaces
- **Dynamic Forms**: Forms with conditional field display
### Modal Components
- **Dynamic Modals**: Modal dialogs and popups
- **Form Modals**: Forms within modal dialogs
- **Confirmation Dialogs**: Confirmation and alert dialogs
- **Custom Modals**: Specialized modal implementations
## UI Component Development Process
### 1. Component Planning & Design
- **Requirements Analysis**: Define component functionality and user interactions
- **Data Architecture**: Plan data structure and provider requirements
- **UX Design**: Design user-friendly interfaces and workflows
- **Performance Considerations**: Plan for scalability and optimization
- **Integration Strategy**: Plan integration with existing systems
### 2. Component Structure Setup
- **XML Configuration**: Create component definition files
- **Directory Structure**: Organize component files and dependencies
- **Data Provider**: Implement data source and collection handling
- **Template Files**: Create KnockoutJS templates for rendering
- **JavaScript Modules**: Build component logic and interactions
### 3. Data Management
- **Collection Building**: Create efficient data collections
- **Filtering & Sorting**: Implement advanced filtering and sorting capabilities
- **Pagination**: Handle large datasets with pagination
- **Search Functionality**: Implement search and filter mechanisms
- **Data Validation**: Ensure data integrity and validation
### 4. User Interface Development
- **Responsive Design**: Create interfaces that work across devices
- **Accessibility**: Implement WCAG compliance and keyboard navigation
- **User Experience**: Optimize for intuitive user interactions
- **Performance**: Ensure fast loading and smooth interactions
- **Cross-browser**: Ensure compatibility across browsers
## XML Configuration
### Component Definition
```xml
<listing xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Ui:etc/ui_configuration.xsd">
<argument name="data" xsi:type="array">
<item name="js_config" xsi:type="array">
<item name="provider" xsi:type="string">vendor_module.grid_data_source</item>
</item>
</argument>
<columns name="columns">
<column name="id">
<settings>
<filter>text</filter>
<label translate="true">ID</label>
</settings>
</column>
</columns>
</listing>
```
### Form Configuration
```xml
<form xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Ui:etc/ui_configuration.xsd">
<fieldset name="general">
<field name="name">
<argument name="data" xsi:type="array">
<item name="config" xsi:type="array">
<item name="label" xsi:type="string" translate="true">Name</item>
<item name="dataType" xsi:type="string">text</item>
<item name="validation" xsi:type="array">
<item name="required-entry" xsi:type="boolean">true</item>
</item>
</item>
</argument>
</field>
</fieldset>
</form>
```
## Data Providers
### Collection Data Provider
- Implement `\Magento\Framework\View\Element\UiComponent\DataProvider\DataProviderInterface`
- Create efficient data collections
- Handle filtering, sorting, and pagination
- Optimize database queries
### Form Data Provider
- Load and save form data
- Handle form field dependencies
- Implement data validation
- Manage form state
## KnockoutJS Templates
### Template Development
- Create KnockoutJS templates for component rendering
- Implement data binding
- Handle user interactions
- Manage component state
### Data Binding
- Two-way data binding
- Computed observables
- Observable arrays
- Custom bindings
## Best Practices
### Performance
- **Efficient Collections**: Optimize data collection queries
- **Lazy Loading**: Load data on demand
- **Caching**: Cache frequently accessed data
- **Pagination**: Implement proper pagination for large datasets
### Code Organization
- **Modular Structure**: Organize components in logical modules
- **Reusable Components**: Create reusable component patterns
- **Documentation**: Maintain clear component documentation
- **Testing**: Write tests for component functionality
### User Experience
- **Responsive Design**: Ensure mobile-friendly interfaces
- **Accessibility**: Implement WCAG compliance
- **Error Handling**: Provide clear error messages
- **Loading States**: Show appropriate loading indicators
## References
- [Adobe Commerce UI Components](https://developer.adobe.com/commerce/frontend-core/ui-components/)
- [KnockoutJS Documentation](https://knockoutjs.com/)
- [UI Component Guide](https://developer.adobe.com/commerce/frontend-core/guide/ui-components/)
Focus on creating intuitive, performant UI components that enhance user experience and productivity.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.