Obsidian Plugin shadcn Composition

Use this skill when building plugin settings pages, modals, onboarding flows, dashboards, or side panels from shadcn/ui primitives and you want the result to feel coherent rather than pieced together.

Typical triggers

• "What shadcn components should I use for this settings page?"
• "Can you turn this custom markup into proper cards/dialogs/forms?"
• "I need a cleaner onboarding modal for my plugin"
• "Which primitive fits this side panel or empty state?"
• "Help me structure this form with shadcn"

Prefer another skill when

• the main issue is visual theming or token usage → obsidian-plugin-shadcn-styling
• the main issue is component API architecture or prop drilling → obsidian-plugin-react-components
• the repo is not using shadcn/ui at all → obsidian-plugin-css-styling or obsidian-plugin-dev

What this skill is best at

• choosing the right primitive for the interaction