Skill UI

A comprehensive guide for developers to diagnose and fix the six most common errors encountered when building Obsidian plugins. It covers critical technical issues such as null pointer exceptions, manifest loading failures, incorrect CSS paths, command registration timing, and state persistence bugs, ensuring reliable and stable plugin functionality.

A comprehensive guide to the Obsidian event system, detailing how to handle various lifecycle and state changes within plugins. Learn to register listeners for vault events (file creation, modification, deletion), workspace events (layout changes, view activation), and metadata cache updates. Essential for building highly reactive and deeply integrated Obsidian plugins.

This guide details the recommended pattern for managing per-project plugin settings and state within a development environment. Plugins store their configuration in a dedicated `.claude/plugin-name.local.md` file. This file utilizes YAML frontmatter for structured settings (like enabling flags, retry counts, and parameters) and a Markdown body for additional context or instructions. It provides techniques for reading these settings using Bash hooks, commands, and agents.

This guide outlines best practices for building highly flexible and maintainable React components. It addresses common architectural pitfalls, such as 'boolean prop proliferation,' by recommending advanced patterns like compound components, state lifting, and context providers. Use this when refactoring large component libraries, designing robust APIs, or reviewing component architecture, including considerations for React 19 APIs.

A senior specialist for building modern, production-grade React applications using React 19, Server Components, and Next.js App Router. Expertise includes implementing complex state management (Redux, Zustand), optimizing performance with memoization, handling data fetching with TanStack Query, and ensuring strict TypeScript typing and accessibility standards. Ideal for architecting large-scale frontend systems.

A comprehensive architectural guide for building production-grade flowcharts using ReactFlow. This pattern set covers key challenges including hierarchical tree navigation (expandable/collapsible nodes), performance optimization via incremental rendering and memoization, and advanced state management using Redux-like reducer patterns with history tracking (undo/redo).

This skill provides comprehensive patterns and templates for developing custom, reusable node components within the React Flow library. It ensures adherence to best practices by integrating proper TypeScript types and facilitating connection with global application state stores. Ideal for building complex, interactive workflow diagrams and visual programming interfaces.

This skill provides production-ready architectural patterns for building robust mobile applications using React Native and Expo. It covers complex topics like state management, sophisticated navigation flow, integrating native modules, and implementing offline-first capabilities. It is ideal for starting new projects or optimizing existing large-scale React Native applications.

A comprehensive guide to modern React state management patterns. It covers various state types—including local, global, server, and form state—and demonstrates best practices using industry-leading libraries like Redux Toolkit, Zustand, Jotai, and React Query. Use this when building complex, scalable React applications and needing to select the optimal state solution.

A comprehensive guide to modern React UI patterns. It covers best practices for managing application states, including determining when to use skeleton loaders vs. spinners, implementing robust error handling hierarchies (inline, toast, banner), and designing effective empty states. Essential for building high-quality, user-friendly components that handle asynchronous data gracefully.

Summarizes React’s official guidance on when to use or avoid useEffect by highlighting derived state handling, expensive calculations, subscriptions, and cleanup strategies for data fetching.

Guidelines for responding to code review feedback with technical rigor: read every comment, restate requirements, verify against the codebase, ask clarifying questions, push back when technically needed, and implement fixes one at a time with testing.