wippy-plugin

Senior-level guidance for developing IntelliJ Platform plugins in Kotlin (extension points, plugin.xml, services, listeners, actions, tool windows, custom languages / file types, Grammar-Kit lexer/parser/PSI, LSP4IJ, threading model, Gradle IntelliJ Platform plugin) AND for inspecting a live IDE via the IDE Introspector MCP tools (arch.*, ui.*, psi.*, code.*, services.*, events.*, editor.*, screenshot.*, exec.*) surfaced through the JetBrains "idea" MCP server. Use when writing, reviewing, or debugging IntelliJ/JetBrains plugin code; registering extension points; deciding between application/project/module services or light @Service; wiring listeners or message-bus topics; building actions, tool windows, annotators, references, or completion; defining a custom language with Grammar-Kit; configuring the Gradle build; or asking "how is X done in IntelliJ", "what extension point / service / listener exists", or "inspect the running IDE".

Senior-level guidance for writing Lua code and YAML registry entries for the Wippy platform — the single-binary, actor-model AI runtime. Use whenever working with Wippy: authoring or reviewing function.lua / process.lua / workflow.lua entries, _index.yaml entry definitions, agent.gen1 agents, http.endpoint / http.router / http.service, registry entries and namespace:name IDs, the module system (require + modules:/imports:), actor processes (process.spawn, inbox, channel.select, supervision/monitor/link), funcs.call / funcs.async, typed errors (result, err pairs), SQL/store/queue/fs data access, security (actor/scope/can), the wippy/llm and wippy/agent frameworks, or wippy/test BDD tests. Trigger keywords: Wippy, wippy.ai, function.lua, process.lua, workflow.lua, agent.gen1, _index.yaml, .wippy.yaml, wippy.lock, registry entry, channel.select, process.inbox, funcs.call, llm.generate, "registry:name", Lua actor.