@biznetgio/neo-app 0.4.38 → 0.4.40
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 +1 -1
- package/prompt.md +25 -1
package/package.json
CHANGED
package/prompt.md
CHANGED
|
@@ -6,7 +6,7 @@ Keep this in sync with cli/prompt.md (the npm package's bundled copy).
|
|
|
6
6
|
-->
|
|
7
7
|
# Set this repo up on NEO App
|
|
8
8
|
|
|
9
|
-
**Version:** 0.4.
|
|
9
|
+
**Version:** 0.4.5 · **Last updated:** 2026-10-15
|
|
10
10
|
|
|
11
11
|
These are the official setup instructions from NEO App (Biznet Gio's managed-app
|
|
12
12
|
platform). If you are an AI coding agent, complete the steps below yourself by running
|
|
@@ -138,6 +138,30 @@ use `neo_enable_db_public_access` / `neo_enable_queue_public_access` (deploy it
|
|
|
138
138
|
Never deploy to **production** without an explicit request, and never default a missing
|
|
139
139
|
environment — every create/deploy names `staging` or `production`.
|
|
140
140
|
|
|
141
|
+
## Talking to non-technical users (vibe coders)
|
|
142
|
+
|
|
143
|
+
Most people deploying here are not platform engineers. Keep the conversation about
|
|
144
|
+
*their app*, not Kubernetes.
|
|
145
|
+
|
|
146
|
+
- **Ask one short question at a time**, and lead with the recommended answer, e.g.
|
|
147
|
+
"I'll deploy this as a web service (recommended) — or is it a background worker?".
|
|
148
|
+
- **Follow the user's language.** If they write in Bahasa Indonesia, reply and ask in
|
|
149
|
+
Bahasa Indonesia.
|
|
150
|
+
- **Don't ask about platform internals** — ingress, build contexts, runtime classes,
|
|
151
|
+
Dockerfile paths, namespaces. Infer them (`neo_scan_repo` gives contextDir, build
|
|
152
|
+
type, and a suggested port) or use safe defaults, and only surface a choice that
|
|
153
|
+
genuinely changes the outcome (web vs worker, which components, the cost).
|
|
154
|
+
- **Only ask which components to deploy when there's real ambiguity** — a monorepo
|
|
155
|
+
with several runnable services. For a single component, just proceed.
|
|
156
|
+
- **A scheduled job needs a target.** If the user asks for a cron but doesn't say what
|
|
157
|
+
it should hit, ask which URL or service command to run (use `neo_cron_questionnaire`).
|
|
158
|
+
- **Show the cost and get an explicit yes before anything billable** (the Approve &
|
|
159
|
+
Create / confirmation gates). Never infer consent from silence or an earlier,
|
|
160
|
+
unrelated approval.
|
|
161
|
+
|
|
162
|
+
The confirmed component/topology choice is captured in the immutable plan
|
|
163
|
+
(`neo_plan_stack`) — you don't modify the user's repository to record it.
|
|
164
|
+
|
|
141
165
|
## Environment
|
|
142
166
|
|
|
143
167
|
The CLI targets production by default. Set `NEO_APP_URL` to point it at a different
|