@plasmickit/cli 0.2.5 → 0.2.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plasmickit/cli",
-  "version": "0.2.5",
+  "version": "0.2.6",
   "description": "Plasmic skill bootstrap and NAS workflow resource manager",
   "license": "MIT",
   "repository": {

package/skill/plasmic/SKILL.md

@@ -25,6 +25,14 @@ Read every returned `mustRead` file, starting with `referencePath`. Resolve link
 
 The published resolver checks the NAS release manifest and verifies resource hashes. Stop dependent work on failure; do not silently use stale references. If it requires a newer CLI before npm has that version, install its returned `cliUrl` and rerun. Relay meaningful preparation progress from stderr; stdout contains the result. Report local versus published resources accurately.
 
+## Ensure Desktop MCP access
+
+Before Desktop work, check the **current session's** actual tool inventory. When Plasmic Desktop MCP is present, use it directly; do not re-register it. An entry in another client or a skill installation is not a connection.
+
+If tools are missing, read `references/desktop-transports.md` from the resolved `resourceRoot` and follow its automatic setup steps. Identify the current client, verify its active MCP configuration path/schema and installed Plasmic executable through public configuration/help, then add the missing `plasmic-desktop` stdio entry with arguments `["--mcp"]` within the user's authorized task and host permissions. Preserve unrelated settings, comments and existing server options. Do not register every installed Agent, guess a config path, overwrite a conflicting entry, add auto-approval rules or change credentials.
+
+Use the client's documented MCP reload/reconnect if available; otherwise state which configuration was updated and that a new session is needed. Only a successful native `get_app_state` proves this session is connected. Never claim a config write loaded tools, or invent tool calls that the session cannot access. If setup cannot be verified, report the specific missing path/contract and continue independent work; authenticated script RPC follows the same routing document and must be described as script access, not native MCP.
+
 ## Prototype principles
 
 Select components before composing markup. Discover existing business components and matching templates, prefer them and registered library components, and read their current Props, Slots and event contracts. Do not redraw available functional components with HTML/CSS. Follow `references/libraries/index.md` for selection and verified contract gaps.