@vibetocloud/mcp 1.0.1 → 1.0.2
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
CHANGED
|
@@ -415,3 +415,31 @@ git push --set-upstream <remote from config> <current branch>
|
|
|
415
415
|
```
|
|
416
416
|
|
|
417
417
|
Tell the user: "✅ Your code is on vibetocloud. Run `/vibetocloud-deploy` to trigger your first deployment."
|
|
418
|
+
|
|
419
|
+
---
|
|
420
|
+
|
|
421
|
+
## Step 7 — Write CLAUDE.md
|
|
422
|
+
|
|
423
|
+
Check whether `CLAUDE.md` exists in the project root using the Read tool.
|
|
424
|
+
|
|
425
|
+
If it exists, read it and check whether it already contains a "VibeToCloud" section. If it does, skip this step.
|
|
426
|
+
|
|
427
|
+
If it does not exist, or exists but has no VibeToCloud section, append the following block (create the file if needed):
|
|
428
|
+
|
|
429
|
+
```markdown
|
|
430
|
+
## VibeToCloud development
|
|
431
|
+
|
|
432
|
+
This project is deployed on VibeToCloud. The `docker-compose.yml` defines how the application runs **in the cloud** — you do not need Docker locally and should never run `docker compose up`.
|
|
433
|
+
|
|
434
|
+
Use the VibeToCloud MCP skills to work with the project:
|
|
435
|
+
- Push code and deploy: `/vibe`
|
|
436
|
+
- Debug running services: `/vibetocloud-debug`
|
|
437
|
+
|
|
438
|
+
All interaction with running containers happens through the MCP tools, not locally.
|
|
439
|
+
```
|
|
440
|
+
|
|
441
|
+
Commit the CLAUDE.md if it was created or changed:
|
|
442
|
+
```bash
|
|
443
|
+
git add CLAUDE.md
|
|
444
|
+
git diff --cached --quiet || git commit -m "chore: add VibeToCloud development instructions to CLAUDE.md"
|
|
445
|
+
```
|