magicpath-ai 1.3.0-beta.10 → 1.3.0-beta.11

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/guide.md +7 -5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "magicpath-ai",
3
- "version": "1.3.0-beta.10",
3
+ "version": "1.3.0-beta.11",
4
4
  "description": "Node CLI for MagicPath",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
package/skills/guide.md CHANGED
@@ -14,8 +14,10 @@ Run `magicpath-ai info` to check auth status and project context.
14
14
 
15
15
  ## Workflow
16
16
 
17
+ > **Always use `-o json`** for all data-returning commands (`search`, `list-projects`, `list-components`, `info`, `add`, `integrate`). This gives you structured output to work with instead of human-readable tables.
18
+
17
19
  1. **Check auth** — run `magicpath-ai whoami` to verify authentication.
18
- 2. **Find components** — use `magicpath-ai search <query>` to search across all projects, or `list-projects` then `list-components <projectId>` to browse.
20
+ 2. **Find components** — use `magicpath-ai search <query> -o json` to search across all projects, or `list-projects -o json` then `list-components <projectId> -o json` to browse.
19
21
  3. **Understand components visually** — `search` and `list-components` results include a `previewImageUrl` field. Download and analyze these images to understand what each component looks like before recommending it. This helps you make better decisions about which components fit the user's needs without opening a browser preview. Preview images are for your own understanding — use the `view` command when the user needs to see a component.
20
22
  4. **Confirm with the user (STOP and wait)** — unless the user specified an exact generatedName, tell the user what you found (name, generatedName, project), open a browser preview with `magicpath-ai view <generatedName>`, and ask if it's the right component. If multiple matches, list them all and ask which one. **This is a STOP point — end your response here and wait for the user to reply. Do NOT proceed to steps 5-8 until the user explicitly confirms.** Do not run `add` or `add --inspect` yet.
21
23
  5. **Inspect source** — only after the user confirms in step 4, use `magicpath-ai add <generatedName> --inspect` to see the component's source code without installing. Decide how it needs to be adapted (props to add, behavior to wire up).
@@ -40,10 +42,10 @@ magicpath-ai login # one-click browser login
40
42
  magicpath-ai whoami # check auth status
41
43
  magicpath-ai info # full project context
42
44
 
43
- # Find components
44
- magicpath-ai search "input box" -o json # search across all projects
45
- magicpath-ai list-projects # list all projects
46
- magicpath-ai list-components <id> # list components in a project
45
+ # Find components (always use -o json)
46
+ magicpath-ai search "input box" -o json # search across all projects
47
+ magicpath-ai list-projects -o json # list all projects
48
+ magicpath-ai list-components <id> -o json # list components in a project
47
49
 
48
50
  # Inspect components
49
51
  magicpath-ai view <generatedName> # preview in browser