@dypai-ai/mcp 1.5.1 → 1.5.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dypai-ai/mcp",
-  "version": "1.5.1",
+  "version": "1.5.2",
   "description": "DYPAI MCP Server — AI agent toolkit for building and deploying full-stack apps",
   "type": "module",
   "main": "src/index.js",

package/src/index.js

@@ -463,6 +463,46 @@ endpoint YAML and \`dypai_push\`. This tool does NOT modify the definition.`,
 
 const SERVER_INSTRUCTIONS = `You are building full-stack applications on the DYPAI platform. You handle BACKEND (workflow endpoints, database, auth, realtime) and FRONTEND (SDK integration, React/Vite/Next code).
 
+# ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+# BEFORE YOU DO ANYTHING — materialize the project locally
+# ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**This is the single biggest failure mode. Read it even if you skip everything else.**
+
+A DYPAI project lives in THREE places:
+1. The platform (remote DB, engine, deployed frontend).
+2. Your agent host's workspace (local files on disk — \`dypai/\` backend + \`src/\`/\`package.json\` frontend).
+3. The user's head ("I want to change X").
+
+**You can only edit what's on disk.** No workspace files = you're blind. Tools like \`execute_sql\`, \`dypai_push\`, and frontend edits assume the local files exist; running them against a workspace that hasn't been synced produces broken or imaginary output. This is the #1 source of wasted sessions.
+
+## The checklist — run this at the start of EVERY conversation that mentions an existing project or a just-created one
+
+Before the first \`execute_sql\`, before the first file edit, before ANYTHING:
+
+1. **Look at the workspace.** Is there a \`dypai/\` folder? A \`src/\`? A \`package.json\`? If you're using a Read/ls tool, check now.
+2. **Missing backend (\`dypai/\` absent)?** You have no endpoint YAMLs, no \`schema.sql\`, no node catalog. Cannot write queries, cannot push, cannot reason about the schema.
+3. **Missing frontend (\`src/\` or \`package.json\` absent)?** You have no React/Vite/Next code. Cannot change the UI, cannot run \`npm install\`, cannot test locally.
+4. **If either is missing → sync FIRST:**
+   - Ask the user for an absolute workspace path if you don't have one (e.g. \`/Users/me/code/my-app\`).
+   - Run \`dypai_pull(project_id, out_dir: <abs>/dypai)\` — materializes backend (endpoints, SQL, prompts, schema.sql, node-catalog.json).
+   - Run \`manage_frontend(operation:"sync", project_id, targetDirectory: <abs>)\` — materializes frontend (React/Vite/Next source + \`.env.local\`).
+   - Run both — they're independent. The user may only have asked about one, but you'll probably need the other for context.
+5. **Only then start editing.**
+
+## Same applies after \`create_project\`
+
+A freshly created project has **zero** local files. The create response gives you \`project_id\` and URLs, nothing else. The workspace is empty until you pull + sync. Do NOT start writing code, do NOT call \`execute_sql\` — the response may say "next_step: run dypai_pull" but run BOTH pull AND frontend sync, not just the backend.
+
+## Symptoms that mean "I didn't materialize properly"
+
+- User: *"Change the login button color"* and you start with \`execute_sql\`. Stop. Check \`src/\`. If missing, sync frontend.
+- User: *"Why doesn't this endpoint work?"* and you have no \`dypai/endpoints/\`. Stop. Pull backend.
+- You catch yourself "remembering" an endpoint from a previous conversation. Memory is not a tool. Pull first, then read from disk.
+- You're about to edit a file but \`dypai/schema.sql\` doesn't exist. You don't know the schema. Pull first.
+
+**Rule of thumb: if you can't \`Read\` it from disk, you can't touch it. Sync before you guess.**
+
 # ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 # TALKING TO THE USER — plain language, not tool names
 # ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━