ui-molecule

Guide molecule-level UI component design and review with prop-driven data flow.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/grvpanchal/elegant-opencode --skill ui-molecule
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-molecule
Source: https://github.com/grvpanchal/elegant-opencode/tree/main/skills/ui-molecule
Command: npx skills add https://github.com/grvpanchal/elegant-opencode --skill ui-molecule

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Molecule-level UI components are often assembled manually from atoms; this Skill provides guidance and patterns to design, review, and validate molecules with a cohesive purpose.

Core Features & Use Cases

  • Composing atoms from your atom library to form reusable molecules (e.g., SearchBar, FormField).
  • Enforcing single cohesive purpose and consistency across the component library.
  • Providing best practices for props passthrough, layout, and accessibility.

Quick Start

Identify a candidate particle (SearchBar) and refactor it into a Molecule by composing existing atoms, ensuring no direct state connections and maintaining clear prop interfaces.

Frequently Asked Questions about ui-molecule

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

FAQPage Schema
What are UI molecules in atomic design and when do I need them?▼

UI molecules in atomic design are components that compose multiple atoms into a single cohesive unit, like a SearchBar or FormField. You need them when building a React component library to enforce consistency and reusable presentational patterns.

How do I build a React molecule component from existing atoms?▼

To build a React molecule, compose existing atoms from your library while ensuring the molecule maintains a single cohesive purpose. Use prop-driven data flow for presentational behavior and avoid direct state management inside the molecule component.

Should a UI molecule manage its own state in a React design system?▼

A UI molecule in a React design system should avoid direct state management. Instead, it should rely on prop-driven data flow and presentational behavior, ensuring the molecule component acts purely as a composition layer for atoms.

What's the best way to audit UI molecules in an existing component library?▼

The best way to audit UI molecules in a component library is to verify they compose existing atoms correctly, maintain a single cohesive purpose, restrict component size, and avoid state management while enforcing prop passthrough and accessibility.

Can I use this molecule design pattern with any React component library?▼

Yes, this molecule design pattern applies to any React component library using atomic design principles. It provides guidelines for composing atoms, enforcing prop-driven interfaces, and validating that molecules avoid direct state management.

Why should molecule-level components avoid direct state connections?▼

Molecule-level components should avoid direct state connections to maintain a presentational behavior pattern. This ensures molecules remain reusable across different parts of the UI, relying entirely on prop-driven data flow rather than internal state management.