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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "your-ai-workflow-firebase-os",
-  "version": "1.2.37",
+  "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

@@ -262,20 +262,31 @@ change the owner can use and a change they cannot.
    extra forms, sample data or metrics the owner did not mention. Inside a page
    you design freely — "an impressive hero" is yours to make good — the limit
    is on adding THINGS, not on doing the asked thing well.
-7. YOU create pages, and a page is created as FILES — never in the app, never
-   in Firestore, never on a screen. "Add a page" (or the Add-a-page sentence
-   from the owner's Pages screen) means: write its config file and its content
-   file, both named from the page's name — a page called "Client onboarding"
-   is \`clientOnboardingTab.config.ts\` plus \`ClientOnboardingContent.tsx\`.
+7. A page the owner added on their Pages screen ALREADY EXISTS. The sentence
+   they paste says so, names its web address and names its one content file —
+   write exactly that file and NOTHING else: no config file, no second
+   address, nothing to Firestore, and never a reply telling them to create or
+   fix anything. Only a page asked for in the chat, one that exists nowhere
+   yet, is YOURS to create, and then it is created as FILES — never in
+   Firestore: its config file and its content file, both named from the
+   page's name — a page called "Client onboarding" is
+   \`clientOnboardingTab.config.ts\` plus \`ClientOnboardingContent.tsx\`.
    Nothing else registers a page: no registerPages.ts, no customRoutes, no
-   database writes, and never tell the owner to add it on a screen. When a
-   config file already exists for that page or address, edit THAT file and its
-   content file — never a second config, never a second address. When the
-   address exists but has NO config file (the owner made the page in the app),
-   write ONLY its content file, <PascalCase of the page's name>Content.tsx.
+   database writes. When a config file already exists for that page or
+   address, edit THAT file and its content file — never a second config,
+   never a second address. When the address exists but has NO config file
+   (the owner made the page in the app), write ONLY its content file.
    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.
@@ -297,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\`.
@@ -385,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
@@ -526,22 +558,28 @@ nothing to register, no import to add. The owner then sees it on the Pages
 screen (or Forms) where they can rename it, change its web address, hide it,
 reorder it or link a different form. Everything else about it is your job.
 
-A page is exactly two files, named from the same name: the config file and the
-content file (\`clientOnboardingTab.config.ts\` + \`ClientOnboardingContent.tsx\`
-for a page called "Client onboarding"). The Add button on the owner's Pages
-screen does not create anything — it hands the owner a sentence for you, with
-a free web address already chosen. Honour that address exactly.
+A page you create is exactly two files, named from the same name: the config
+file and the content file (\`clientOnboardingTab.config.ts\` +
+\`ClientOnboardingContent.tsx\` for a page called "Client onboarding").
+
+But the Add button on the owner's Pages screen creates the page ITSELF — its
+address, its name, its icon, its starting layout. The sentence that screen
+hands them says the page already exists and names the ONE content file to
+write. When you get that sentence, write exactly that file, nothing else: no
+config file, no second address, and never a message back saying the page must
+be created first. It is already in their menu.
 
 CHECK FIRST — before you create anything. When the page they are talking
 about already has a config file, or they name an address that is already
 taken, edit what exists: the config file if there is one, and its content
 file — never a second config, a form or another address for the same page.
 An address with NO config file behind it is a page the owner made inside the
-app in an older version: write ONLY its content file, named after the page in
-PascalCase plus \`Content\`. Forms follow the same line: a form the owner made
-on the Forms screen is linked with \`<ContactPopup formId="..." />\` and never
-remade; you write a new \`*Form.config.ts\` only when they ask for a new form
-in the chat, as in the examples below.
+app: write ONLY its content file — the one the owner's sentence names, or
+failing that the page in PascalCase plus \`Content\`. Forms follow the same
+line: a form the owner made on the Forms screen is linked with
+\`<ContactPopup formId="..." />\` and never remade; you write a new
+\`*Form.config.ts\` only when they ask for a new form in the chat, as in the
+examples below.
 
 ### Step 1 — ask first, build second
 
@@ -659,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;