Skill UI

This skill provides a comprehensive guide to designing and developing autonomous AI agents for code plugins. It covers the required file structure (YAML frontmatter), best practices for defining agent roles, designing robust system prompts, and setting up clear triggering conditions. Use this when you need to conceptualize, structure, or refine an agent's capabilities to handle complex, multi-step tasks autonomously.

This advanced skill analyzes an existing codebase to identify architectural patterns, dependencies, and technical stacks. It recommends tailored Claude Code automations—including Hooks, Subagents, Skills, Plugins, and MCP Servers—to optimize development workflows, improve code consistency, and enhance overall project scalability. Use this when setting up a new project or looking to refine existing Claude Code configurations.

Automates fastify plugin creation within backend development workflows by guiding through best practices, generating production-ready code, and validating configurations for microservices, caching, and database integrations.

Guides Claude Code plugin authors through creating event-driven hooks that validate tool usage, react to outcomes, and gate completion with prompt-based or command hooks, covering PreToolUse, PostToolUse, Stop, Session events, and session context loading.

Manages environment configurations and secrets across development, staging, and production deployments by invoking the environment-config-manager plugin to generate, update, or retrieve files, keeping DevOps workflows secure and consistent.

A comprehensive guide and expertise source for developing robust, high-performance Minecraft server plugins using Bukkit, Spigot, and Paper APIs. Covers advanced topics including event handling, NMS internals, performance profiling, architecture design (SOLID), and ecosystem integration (Redis, Docker). Ideal for complex, production-grade plugin development.

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.