markilo 0.4.0 → 1.0.0

package/plugin/skills/export/SKILL.md

@@ -29,8 +29,10 @@ Toolchain: `node "${CLAUDE_PLUGIN_ROOT}/dist/markilo.mjs" <command>` (written `m
 6. To place assets in the user's project, plan first: `markilo install-assets --brand <slug> --framework auto
    [--project <dir>]`. It detects Next.js, Laravel, Flutter or a static site and lists where each file goes and what
    (if anything) the user must add by hand (a head snippet). Show the plan; only with the user's OK re-run with
-   `--apply` (and `--force` only if they want existing icons replaced — those are backed up to `.markilo-backup/`).
-   Do not edit their source files; give them the snippet instead.
+   `--apply --expect <planId>` (the dry run's `planId`: the apply refuses if the project changed after the user saw
+   the plan), and `--force` only if they want existing icons replaced — those are backed up to `.markilo-backup/`.
+   Applying is all-or-nothing; `markilo install-assets --undo [--project <dir>]` previews reversing it, `--apply`
+   does it (files the user edited since are kept). Do not edit their source files; give them the snippet instead.
 7. Tell the user where everything is (`exports/`, `asset-manifest.json`, `guidelines/index.html`), that more groups
    can be added any time (`markilo deliverables --add ios` then `markilo export`), and mention that
    X (Twitter) header sizes could not be verified against x.com documentation.

package/plugin/skills/gallery/SKILL.md

@@ -17,13 +17,14 @@ Toolchain: `node "${CLAUDE_PLUGIN_ROOT}/dist/markilo.mjs" <command>` (written `m
    on this computer, needs the token, serves only the gallery and exported artwork, and stops by itself when idle.
    Without a background shell, run `markilo gallery` instead: it writes `brand/gallery/index.html`, a self-contained
    file that works offline; give the user its `file://` URL.
-2. Explain the review flow in two lines: on each concept choose Keep / Refine / Drop, add revision tags or a note, click
-   on the big mark to pin what should change at that spot, tick "Compare" on two or more concepts to see them side by
-   side and mark one "Prefer this". Then press **Send to Claude** (served) or **Download decisions** (file) and tell
-   you when done.
+2. Explain the review flow in two lines: at the sketch stage, pick one sketch per direction to develop (or "None of
+   these"); on each developed concept choose Keep / Refine / Drop, add revision tags or a note, click on the big mark
+   to pin what should change at that spot, tick "Compare" on two or more concepts to see them side by side and mark
+   one "Prefer this". Then press **Send to your agent** (served) or **Download decisions** (file) and tell you when
+   done.
 3. Read the decisions: `markilo feedback --brand <slug>` (after a download: `markilo feedback --import <file>`). It
    returns each decision with tags, notes and pinned spots (e.g. "at top-right: thicker stem"), the preferred concept
    and ready-to-act requests. Repeat them back to the user in one short summary.
-4. Act: `markilo feedback --brand <slug> --apply` marks dropped concepts rejected and kept ones shortlisted (only after
-   the user confirmed the summary). Log what was decided (`markilo answers`) and continue with the refine skill for
+4. Act: `markilo feedback --brand <slug> --apply` records sketch picks (the user's pick wins over the critic's) and
+   marks dropped concepts rejected and kept ones shortlisted (only after the user confirmed the summary). Log what was decided (`markilo answers`) and continue with the refine skill for
    each "refine" request — pinned spots tell you where on the mark the change belongs.