amorphous-cli 0.3.7 → 0.3.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "amorphous-cli",
-  "version": "0.3.7",
+  "version": "0.3.8",
   "mcpName": "io.github.amorphous-one/amorphous",
   "description": "Make whatever you want, yourself, with your own agent, or with others.",
   "type": "module",

package/skill/amorphous/SKILL.md

@@ -48,7 +48,7 @@ Then choose the path that matches the request:
 - **Existing abstract in a new folder:** Find the abstract with `amorphous-cli list --view all`, or use the id/name the person gave you. If the person has owner or editor access and the task needs source or records, run `amorphous-cli pull <id-or-name>` first in a new, empty project folder. This creates `.amorphous.json` and downloads the draft and records. Then run `amorphous-cli context` once, and only then read the guides and source files. `context` alone does not bind the folder; it writes guide files, so running explicit `pull <id-or-name>` afterward will fail because the directory is no longer empty. If the folder is not empty, do not risk its files: use a new empty folder or ask the person which existing project folder to use. If they have view or use access, skip pull. Run `amorphous-cli context <id-or-name>` once to load the guides. When the task needs live interaction, run `amorphous-cli open <id-or-name>` and open the printed Amorphous page; use its **Open live abstract** link to launch the app. The CLI command prints the page URL; it does not launch a browser itself. A use member can submit a source recommendation only when the source files are already available in an authorized project folder; without them, ask the owner/editor to provide the source or grant edit access.
 - If context fails, do not read existing guide files: they may belong to another account or be stale after access was revoked. Preserve unsaved edits and ask the person to restore access or reconnect. Do not run context again during this task.
 - **Access:** View members can open the live abstract and load its guides, but cannot pull, recommend, or change source. Use members can use the live abstract and submit source recommendations for the owner to review when source files are already available to them. Only owners and editors can pull and edit source or publish a version; only the owner can invite/remove members, change visibility, or make a version live. Follow the access already granted; ask the owner for a role change if the requested work needs more access.
-- **New abstract:** Run `amorphous-cli create --name "..." [--template blank|list|board|landing]`. The list, board, and landing starters are working examples, not just mockups.
+- **New abstract:** Run `amorphous-cli create --name "..." [--template blank|list|board|landing]`. The list, board, and landing starters are working examples, not just mockups. When Amorphous provides a recipe JSON (for example, **Start with an agent** on the homepage), save it in the project folder and run `amorphous-cli create --recipe-config <file>` to create and bind that recipe and write its generated files into the folder.
 
 After `context` succeeds, follow its final guide-reading instruction. It names only guide files that contain text; if neither guide contains text, continue without opening empty guide files. The private-guide handling warning appears only when that guide contains text.