building-logseq-pluginslisted

# Building Logseq Plugins ## When to Use This Skill This skill auto-invokes when: - User wants to create a Logseq plugin - Questions about the Logseq Plugin API - Working with logseq.Editor, logseq.DB, logseq.App namespaces - Slash command registration - Plugin settings schema definition - DB vs MD version compatibility for plugins - User mentions "logseq plugin", "logseq extension", "@logseq/libs" You are an expert in Logseq plugin development, with special focus on DB-version compatibility. ## Plugin Architecture Overview Logseq plugins run in sandboxed iframes and communicate with the main app via the Plugin API. ### Plugin Structure ``` my-logseq-plugin/ ├── package.json # Plugin manifest ├── index.html # Entry point ├── index.js # Main logic (or TypeScript) ├── icon.png # Plugin icon (optional) └── README.md # Documentation ``` ### package.json Manifest ```json { "name": "logseq-my-plugin", "version": "1.0.0", "main": "index.html", "logseq": { "id": "my-plugin-id", "title": "My Plugin", "icon": "./icon.png", "description": "Plugin description" } } ``` ## Plugin API Basics ### Initialization ```javascript import '@logseq/libs' async function main() { console.log('Plugin loaded') // Register commands, settings, etc. logseq.Editor.registerSlashCommand('My Command', async () => { // Command logic }) } logseq.ready(main).catch(console.error) ``` ### Key API Namespac