Obsidian Plugin React Components

Use this skill when a React-based Obsidian plugin needs cleaner component architecture, not just better visuals.

Reach for it when the code already works but the component API is getting awkward, brittle, or hard to extend.

Typical triggers

• "This component has too many props"
• "Can we refactor this settings panel to be more composable?"
• "I keep adding boolean flags to this modal or view"
• "Should this use context or compound components?"
• "How should I structure reusable React components for this plugin?"
• "This dashboard/view hierarchy is turning into prop drilling"

What this skill focuses on

• composition over configuration
• compound components over monolithic configurable widgets