ozmoz 0.1.15 → 0.1.16
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/dist/ozmoz-mcp.js +1 -1
- package/package.json +1 -1
package/dist/ozmoz-mcp.js
CHANGED
|
@@ -161,7 +161,7 @@ Set the \`cycles\` parameter to \`"ref"\` to resolve cyclical schemas with defs.
|
|
|
161
161
|
a) The user confirms the screens look good and wants to switch to real data: first save of their data structure. Never assume this approval. If the moment seems right, explain the situation with pedagogical empathy: remind them in simple, jargon-free words that the app currently runs in sandbox/trial mode with dummy data to test the experience safely, and that validating the visual flow is what will unlock creating their real live OZmoz database. Ask them naturally if the interface and user journey suit their needs. DO NOT recite a robotic template: adapt your phrasing naturally to the tone and flow of the conversation. HARD STOP: NEVER call oz_update_project in the same turn...
|
|
162
162
|
b) After this first save, data is added, modified, or deleted (collection, field, type, relation, business rule, permission): hand over as soon as the view is written.
|
|
163
163
|
c) The user asks you to.
|
|
164
|
-
How: call oz_update_project with name, filePaths, rules, and userApproval (the EXACT verbatim quote of the user's message authorizing this call: their approval of the screens or their request to change data; never write it yourself), then apply point 7.
|
|
164
|
+
How: NEVER call 'oz_update_project' silently or without first announcing to the user in plain language that you are now saving their data structure with Alex. A non-technical user must never see an MCP approval popup without knowing what it does. Then call oz_update_project with name, filePaths, rules, and userApproval (the EXACT verbatim quote of the user's message authorizing this call: their approval of the screens or their request to change data; never write it yourself), then apply point 7.
|
|
165
165
|
- filePaths: all files that call oz.* or describe data fields (views AND data files, never views alone); all files in case of doubt.
|
|
166
166
|
- rules: only business rules provided by the user, in plain text. If you have none, ask them simply if there are rules to enforce (limits, durations, permissions); if they have none, do not send rules. Never invent a rule.
|
|
167
167
|
Without MCP: run 'npx ozmoz update' directly in the terminal, then apply point 7.
|