@plasmickit/cli 0.1.0 → 0.1.2

package/package.json

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

package/skill/plasmic/SKILL.md

@@ -17,9 +17,9 @@ npx -y @plasmickit/cli@latest context resolve --mode codegen
 
 Inspect uses accessible Desktop MCP reads and does not require edit permission or save/change designs. Prototype mutations require edit permission. Codegen reads models/contracts through MCP and writes code in the target architecture; it does not use `export_code` or official Plasmic sync. For explicitly requested official `@plasmicapp/cli` integration, resolve inspect and follow the guide's official-CLI reference instead of replacing that request with native coding.
 
-The command checks the NAS release manifest every time, downloads changed resources and verifies their hashes before returning absolute paths. Read all returned `mustRead` files, starting with `referencePath`; resolve subsequent links relative to the reference file. Use the returned `resourceRoot` for verification scripts. For a task spanning multiple modes, resolve and read each mode before its work begins.
+The command checks the NAS release manifest every time, downloads changed resources and verifies their hashes before returning absolute paths. Read all returned `mustRead` files, starting with `referencePath`; resolve subsequent links relative to the reference file. Use the returned `resourceRoot` for verification scripts and follow the guide's conditional section-reading/evidence rules. For a task spanning multiple modes, resolve and read each mode before its work begins.
 
-For prototype work, follow the workflow's project-management reference to resolve Team → Workspace → Project before entering Studio design operations.
+For prototype work, resolve Team → Workspace → Project, pass the workflow's MCP contract preflight, then use the workflow's controlled task for supported new full-project generation of standalone fixed-viewport Overseas/Antd-v6 Pages. Before markup, discover existing business/library components by required role and read candidate contracts. Prefer those components and their compositions for every functional widget; plain semantic content/necessary containers remain valid. Follow the resolved component-selection rule for verified gaps. Directory Page/group names and business copy default to Chinese; internal tree nodes use English PascalCase. Explicit user language/name choices prevail. Admin Pages inside AppShell have no standalone Page title/header/subtitle/intro unless explicitly requested by the current user. Keep requirement/process explanations outside UI. Prepare source-reviewed component/copy inventories and current-Page Slot intent before its first content write; omitted components cannot justify an acceptance exemption. Complete each Page's reference mapping, generation, structural checks, image comparison and native Preview interactions before writing sibling business content. Focused edits retain their scoped workflow.
 
 The CLI streams readable progress to stderr and reserves stdout for the final JSON result. Tell the user when resource preparation starts, then relay meaningful stage changes in their language: current and latest versions, already up to date, or download and integrity verification. Do not narrate cache saving, update locking, compatibility checks or workflow entrypoints. When the command runs longer than the tool's initial response window, use its background/session mode and retrieve incremental output so the user sees progress while it runs. Waiting messages report elapsed time, not an estimated completion percentage. If the tool buffers all output until exit, explain that limitation and report that preparation is still running; do not invent progress. A ready workflow means its files are available for you to read, not that you have already read or executed them. Read `mustRead` before starting dependent work.