your-ai-workflow-firebase-os 1.2.38 → 1.2.39

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "your-ai-workflow-firebase-os",
-  "version": "1.2.38",
+  "version": "1.2.39",
   "description": "Your AI Firebase — a complete Firebase-powered admin app in one React component.",
   "type": "module",
   "main": "dist/your-ai-workflow-firebase-os.cjs.js",

package/scripts/postinstall.js

@@ -279,6 +279,14 @@ change the owner can use and a change they cannot.
    Forms are the same: link a form the owner made with
    \`<ContactPopup formId="..." />\` — never remake it. A new
    \`*Form.config.ts\` only when they ask for a NEW form in the chat (rule 5).
+8. Everything you draw must look like the app it lands in. Style with the
+   theme only — \`bg-background\`, \`text-foreground\`, \`text-accent\`,
+   \`border-[var(--panel-border)]\`, \`glass-panel\`, \`btn-primary\`, and the
+   built-in \`Input\` / \`CustomSelect\` for fields — never \`bg-white\`,
+   \`bg-gray-900\`, hex colours or a palette of your own: hard-coded fields
+   stay dark on the light theme. And NEVER a \`<style>\` tag or any global
+   CSS in a component — one global rule restyles and re-pads every page of
+   the app at once.
 
 Before you answer, re-read the request and this list, and delete anything you
 built that breaks a line of it.
@@ -300,10 +308,14 @@ stops the build with one sentence that says the fix.
   \`Config\`; a content file with no default export; a \`*Form.config.ts\` whose
   \`systemName\` is not the id from its file name; a page config with no
   preset and no matching content file (the page would render empty — the
-  error names the exact \`*Content.tsx\` to create).
+  error names the exact \`*Content.tsx\` to create); a \`<style>\` tag in a
+  content file (global CSS — it restyles and re-pads every page of the app,
+  style with theme classes instead).
 - A hand-written form — a \`<form>\` or an \`onSubmit\` in a content file with
   no \`<ContactPopup />\` — prints a warning, because its entries never reach
-  the Inbox and never show on the Forms screen.
+  the Inbox and never show on the Forms screen. So does a hard-coded colour
+  like \`bg-gray-900\` — it ignores the owner's theme and stays dark on the
+  light theme.
 
 When the build fails, read the sentence, do what it says, build again. Do not
 work around it, do not delete the check, do not touch \`vite.config.ts\`.
@@ -388,6 +400,23 @@ export default function ProdTimerContent({ config, actions }: { config: any; act
 The file is auto-discovered by its name and location. There is no registration
 step, no import to add, and no web address to wire.
 
+### The pages that already exist, and the one file each is filled by
+
+Three pages already exist and are NEVER created, re-created or re-addressed.
+Each is filled by exactly one file, the same way as any other page:
+
+| page          | web address | the one file to write                                              |
+| ------------- | ----------- | ------------------------------------------------------------------ |
+| Home          | \`/\`         | \`src/your-ai-workflow-firebase-os/Home.tsx\` (edit it, do not add one) |
+| Contact       | \`/contact\`  | \`microcomponents/ContactContent.tsx\`                                |
+| Support       | \`/support\`  | \`microcomponents/SupportContent.tsx\`                                |
+
+Contact and Support show their form as a pop-up until one of those files
+exists; the moment it does, the page draws that file instead. So "put the
+contact form INTO the page instead of a pop-up" is one file —
+\`ContactContent.tsx\` rendering \`<ContactPopup isInline formId="contact" />\` —
+and never a new page, a new config file or a new form.
+
 ## Rules for microcomponents
 
 Rules 1-6 apply to microcomponent files only. Rules 7-9 (styling) apply
@@ -668,24 +697,38 @@ Third — a request copied from a page's own row on the Pages screen. The owner
 added the page there first (who it is for, its name, its web address, a
 starting layout, its form), then pasted the row's sentence and finished it:
 
-> "Fill the page at /onboarding — it already exists, so do not create a page,
-> a form, a config file or a web address, and do not edit src/App.tsx or
-> src/main.tsx. Write only one file:
-> src/your-ai-workflow-firebase-os/microcomponents/ClientOnboardingContent.tsx
-> with a default export. It starts from the board preset — use its data hooks
-> and draw the UI yourself. It has no form; do not add one. Here is what it
-> should show: columns, in this order: To do, In progress, Done. Each card has
-> a client name (short text), a contact email, a start date and a short note
-> (long text). Anyone on the team can add a card, drag it between columns,
-> edit it and delete it. The button at the top says New client. No file
-> uploads on this page. Build only this — no other pages, forms or sample
-> cards."
+> "My app already has a page called Client onboarding at /onboarding. It is
+> already made and it is already in the menu — do not create a page, a web
+> address or a settings file for it, and do not edit any other file.
+> Write one file:
+> src/your-ai-workflow-firebase-os/microcomponents/ClientOnboardingContent.tsx,
+> with a default export. That file is what the page shows.
+> The page already starts from the board layout — the heading and the saving
+> are already built and stay on the page. Your file draws only what goes
+> inside the panel.
+> Your component receives everything it needs as props: ({ config, actions })
+> — actions.tasks and actions.categories hold the saved items;
+> actions.saveTask(id, data), actions.deleteTask(id),
+> actions.saveCategory(id, data) and actions.deleteCategory(id) change them;
+> actions.openInlineEditor(categoryId, item) opens the built-in editor;
+> actions.user is the signed-in person, and every item you save must include
+> uid: actions.user.uid. Read and change data ONLY through these props — do
+> not import firebase and do not write your own loading, saving or uploading
+> code.
+> Here is what I would like on it: columns, in this order: To do, In
+> progress, Done. Each card has a client name (short text), a contact email,
+> a start date and a short note (long text). Anyone on the team can add a
+> card, drag it between columns, edit it and delete it. The button at the top
+> says New client. No file uploads on this page. Build only this — no other
+> pages, forms or sample cards."
 
 Every line is a decision already made. The audience, the web address
 (\`route\`), the name (\`tabName\` / \`pageName\`), the heading (\`tabTitle\` /
-\`pageTitle\`) and "Start from the ... preset" (\`template\`) were set on the
-Pages screen — read them from the \`config\` your content file receives, and
-never write them again. THE FILE NAME RULE: the content file is the page's
+\`pageTitle\`) and "already starts from the ... layout" (\`template\`) were set
+on the Pages screen — read them from the \`config\` your content file receives,
+and never write them again. When the sentence lists props, they are real: the
+layout renders your component with exactly those, so a content file that
+ignores them and opens its own Firestore connection is wrong even if it runs. THE FILE NAME RULE: the content file is the page's
 name in PascalCase plus \`Content.tsx\` (a page called "Client onboarding" ->
 \`ClientOnboardingContent.tsx\`); use exactly the name in the request, or the
 page never finds your file. "No file uploads" means draw no upload control;