@plasmickit/cli 0.5.17 → 0.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/skill/plasmic/SKILL.md +2 -0
- package/src/protocol.mjs +1 -1
package/package.json
CHANGED
package/skill/plasmic/SKILL.md
CHANGED
|
@@ -44,6 +44,8 @@ Use the client's documented MCP reload/reconnect if available; otherwise state w
|
|
|
44
44
|
|
|
45
45
|
## Prototype principles
|
|
46
46
|
|
|
47
|
+
Start with the workflow's **Before content writes** checkpoint and the resolved `references/planning.md`. For new Pages or structural changes, use the existing project/Page rules cards and selection preflight before composition. Local repairs read and check the affected rules without restarting unrelated Page planning. Tool availability, `validate` and `save` do not establish design-rule compliance.
|
|
48
|
+
|
|
47
49
|
Design the in-scope Pages' region relationships before detailed generation under `references/design/page-structure.md`; reconcile the current Page with live templates and component contracts, then generate and review against that structure. Requirements constrain business behavior and explicit presentation choices; use design reasoning for unspecified layout. 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.
|
|
48
50
|
|
|
49
51
|
For admin prototypes, read `references/admin-templates.md` and its catalog, inspect applicable live templates, then adapt the selected composition to the requirement. Read the relevant component and composition references before using them. A template or component must fit the current requirement and the project's actual library.
|
package/src/protocol.mjs
CHANGED
|
@@ -7,7 +7,7 @@ export const CLI_VERSION = createRequire(import.meta.url)("../package.json").ver
|
|
|
7
7
|
export const MIN_CLI_VERSION = "0.0.59";
|
|
8
8
|
export const MODE_REFERENCES = {
|
|
9
9
|
inspect: ["references/model-reading.md"],
|
|
10
|
-
prototype: [],
|
|
10
|
+
prototype: ["references/planning.md"],
|
|
11
11
|
codegen: ["references/model-reading.md", "references/codegen/project-code.md", "references/codegen/acceptance.md"],
|
|
12
12
|
};
|
|
13
13
|
export function compareVersions(a, b) {
|