Skill UI

A comprehensive guide for setting up Continuous Integration and Continuous Deployment (CI/CD) workflows for Obsidian plugins using GitHub Actions. This setup automates critical tasks like build validation on every push, manifest consistency checks, version number bumping, and structured GitHub releases, ensuring robust and reliable plugin deployment lifecycles.

Master the art of building complex, production-grade user interfaces for Obsidian plugins. This guide covers implementing custom sidebar views (ItemView), interactive modal dialogs (for forms and confirmations), context menus, status bar widgets, and advanced editor commands. Learn how to interact with the Obsidian Vault API for file manipulation, significantly enhancing your plugin's functionality and user experience.

This comprehensive guide provides a step-by-step workflow for establishing a professional Obsidian plugin development environment. It covers cloning the official sample, installing necessary dependencies (Node.js, TypeScript, esbuild), configuring essential project metadata (`manifest.json`, `versions.json`), and setting up a symlinked development vault for seamless testing and building.

This guide establishes a comprehensive and rapid development loop for Obsidian plugins. It covers the entire workflow, from setup (cloning templates, symlinking) to advanced features, including running esbuild in watch mode, achieving hot-reloading (via Ctrl+R or automatic methods), deep debugging with Chrome DevTools, and running unit tests with vitest. Essential for developers seeking fast feedback and reliable plugin iteration.

This skill provides a comprehensive guide to setting up isolated development, testing, and production vaults within Obsidian. It covers advanced techniques like symlinking plugin sources for hot reloading, implementing environment-specific configuration logic (e.g., managing debug modes and feature flags), and creating standardized vault templates for team onboarding, ensuring a robust and scalable development lifecycle.

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.

This provides a local development loop for integrating the OpenEvidence clinical decision support API. Developers can build health-tech tools and quickly iterate using mock evidence queries, citation responses, and clinical summaries. It supports toggling between mock mode for rapid development and sandbox mode for validation against the real platform, ensuring development uses de-identified data.

This guide outlines the strict multi-environment setup for the OpenEvidence clinical AI system, crucial for maintaining HIPAA compliance. It details how to configure and validate separate environments (Development, Staging, Production) to manage different data classifications—synthetic, de-identified, and full PHI. The process emphasizes environment validation checks, BAA adherence, and robust audit logging to prevent regulatory violations and PHI exposure.

This skill automates the entire software development process overnight. By leveraging mandatory Git hooks, it strictly enforces Test-Driven Development (TDD). Use this when complex features need building, large codebases need refactoring, or bugs need fixing autonomously, guaranteeing that every commit passes rigorous testing cycles and meets high production-ready standards.

Guides API development teams through pagination helper tasks by providing best-practice guidance, ready-to-run code, and validation for REST, GraphQL, OpenAPI, and related authentication/design workflows.