justinw0ng/obsidian-plugin-skill
Unofficial agent skills for scaffolding, building, verifying, reviewing, and shipping Obsidian community plugins. Not affiliated with Obsidian.
End-to-end playbook for building an Obsidian community plugin. Use when scaffolding, implementing, verifying, reviewing, or shipping any Obsidian plugin; for vault-as-markdown architecture, Selenium E2E, plugin-review lint, GitHub releases, community directory submission, or /obsidian-plugin.
Architecture for Obsidian plugins: pure core vs Vault adapter, vault-as-data, codeblocks, path safety, caching, and mobile/minAppVersion. Use when designing plugin structure, choosing where logic lives, or /obsidian-plugin-architecture.
Bootstrap a new Obsidian community plugin from the sample plugin or a proven layout. Use when creating a new plugin repo, renaming the sample plugin, wiring esbuild/manifest/scripts, or /obsidian-plugin-scaffold.
Ship an Obsidian community plugin: semver lockstep, GitHub Release assets (no v-prefix tags), community directory submission, and review-failure re-release. Use when releasing, bumping versions, fixing directory review, or /obsidian-plugin-ship.
Obsidian plugin UI conventions: createEl DOM, data-testid hooks, settings sentence case, CSS variables, command callbacks, and community-review bans for HTML/CSS. Use when building settings tabs, views, codeblock renderers, or /obsidian-plugin-ui.
Verify an Obsidian plugin with Node unit tests, typecheck, production build, and Selenium E2E against real Obsidian. Use for test:e2e harnesses, Cloud VM Obsidian install, data-testid health checks, or /obsidian-plugin-verify.