Skill UI

A comprehensive guide for optimizing Obsidian plugin performance, especially when dealing with large knowledge vaults (10,000+ files). Learn advanced techniques such as profiling bottlenecks with DevTools, implementing lazy initialization to speed up startup, processing files in manageable batches with UI yielding, and utilizing LRU caches for bounded memory management. Essential for creating stable, high-performance plugins.

This comprehensive checklist guides developers through the pre-release verification process for Obsidian community plugins. It covers critical technical areas such as validating manifest structure, ensuring clean production builds (e.g., removing sourcemaps), identifying potential memory leaks, and verifying cross-platform readiness, ensuring a high-quality user experience upon submission.

This skill provides advanced patterns for handling high-volume Obsidian file operations, such as debouncing keystrokes, batching file reads, and throttling UI updates. It addresses single-threaded performance bottlenecks, ensuring plugins remain responsive and prevent UI freezes during bulk processing or rapid user interactions.

This guide provides the best-practice reference architecture for developing complex Obsidian plugins. It details a highly modular project structure, enforcing separation of concerns by implementing dedicated layers for commands, views, and services (e.g., vault operations). Use this when designing a new plugin, reviewing existing project structure, or establishing standardized development practices for maintainable and scalable Obsidian extensions.

This guide provides essential, production-ready architectural patterns for building highly reliable Obsidian plugins. It addresses common development pitfalls such as managing typed settings with versioned migration, implementing safe vault operations (check-before-act), and handling event listeners to prevent memory leaks. Use these patterns when hardening your plugin for public release or refactoring for maximum stability.

A comprehensive guide covering essential security practices for developing Obsidian plugins. Learn how to safely handle sensitive credentials (avoiding data.json), implement robust input validation, prevent Cross-Site Scripting (XSS), secure URI handlers, and adhere to modern Electron and Obsidian guidelines for data privacy and system integrity.

A comprehensive guide for developers migrating and upgrading Obsidian plugins across major API versions. It covers critical steps such as auditing plugin compatibility, implementing version-aware settings migration logic (for user data persistence), replacing deprecated API calls (e.g., Vault, Editor, FileManager), and updating configuration files like manifest.json to ensure stability on new Obsidian releases.

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.

Automates scaffolding of new Claude Code plugins within the claude-code-plugins repo, creating directories, plugin.json, READMEs, LICENSE, commands/agents/skills/MCP assets, and marketplace entries before validating schemas and syncing the catalog.

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 details the standardized directory structure and best practices for building robust and maintainable plugins for Claude Code. It covers critical components including the plugin manifest (plugin.json), commands, agents, skills, and hooks. Use this skill when you need to scaffold a new plugin, understand the required component organization, or configure the plugin's architecture according to best practices.

Automatically validates Claude Code plugin repositories by checking required files, JSON schema, frontmatter, permissions, security, marketplace metadata, and README compliance whenever a user asks to validate or check plugins.