Skill UI

Guide for setting up an Obsidian plugin development environment with Node.js, TypeScript, esbuild, and hot-reload, including cloning the sample template, installing deps, configuring a dev vault, and verifying builds for rapid iteration.

Sets up a fast local workflow for Obsidian plugin development with hot-reload, watch mode builds, and dedicated test vaults so authors can iterate quickly on Node.js/TypeScript extensions.

Sets up isolated Obsidian vaults for development, testing, staging, and production plugin workflows, covering symlinked builds, test data scripts, and CI-friendly multi-version testing to keep environments clean.

Provides production-ready reference architecture patterns for Obsidian plugin development, guiding project layout, service layers, and event management so teams can organize new builds and reviews consistently with best practices.

Outlines secure Obsidian plugin development steps for protecting vault data, validating inputs, minimizing permissions, and enforcing HTTPS when handling sensitive operations.

Coordinates environment configuration, secret management, promotion workflows, and health checks for OpenEvidence across development, staging, and production, ensuring smooth clinical AI deployments.

Automates autonomous overnight software development by wiring Git hooks, TDD, and logging so Claude can build features, refactor code, and fix bugs while guaranteeing all tests pass before committing.

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.

Guides measuring, analyzing, and optimizing web performance with Lighthouse scripts, DevTools insights, bundle audits, and a baseline-to-validation workflow so teams can keep Core Web Vitals healthy across development, CI/CD, and production environments.

Sets up Perplexity Sonar API clients across development, staging, and production by routing sonar vs. sonar-pro models per workload, enforcing environment-specific limits, and controlling costs for multi-environment search deployments.

Implements a persistent, file-based planning methodology, allowing users to treat markdown files (task_plan.md, findings.md, progress.md) as an external, reliable working memory. Ideal for managing large, multi-step projects, deep research, or complex development cycles where context window limitations pose a risk. It enforces strict workflows for logging progress, capturing findings, and managing errors across sessions.

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.