@njeybe/nativ 2.3.1 → 2.4.1

package/templates/dot-ai/db_schema.json

@@ -1,39 +1,39 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "version": "1.0.0",
-  "projectName": "{{PROJECT_NAME}}",
-  "updatedAt": "{{TIMESTAMP}}",
-  "engine": "{{DETECTED_DATABASE_ENGINE}}",
-  "tables": [
-    {
-      "name": "example_entity",
-      "description": "Demonstration table definition. The architect updates this during Phase 1A.",
-      "columns": [
-        {
-          "name": "id",
-          "type": "UUID",
-          "primaryKey": true,
-          "nullable": false,
-          "default": "gen_random_uuid()"
-        },
-        {
-          "name": "created_at",
-          "type": "TIMESTAMP",
-          "primaryKey": false,
-          "nullable": false,
-          "default": "NOW()"
-        },
-        {
-          "name": "updated_at",
-          "type": "TIMESTAMP",
-          "primaryKey": false,
-          "nullable": false,
-          "default": "NOW()"
-        }
-      ],
-      "indexes": [],
-      "foreignKeys": []
-    }
-  ],
-  "migrations": []
-}
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "version": "1.0.0",
+  "projectName": "{{PROJECT_NAME}}",
+  "updatedAt": "{{TIMESTAMP}}",
+  "engine": "{{DETECTED_DATABASE_ENGINE}}",
+  "tables": [
+    {
+      "name": "example_entity",
+      "description": "Demonstration table definition. The architect updates this during Phase 1A.",
+      "columns": [
+        {
+          "name": "id",
+          "type": "UUID",
+          "primaryKey": true,
+          "nullable": false,
+          "default": "gen_random_uuid()"
+        },
+        {
+          "name": "created_at",
+          "type": "TIMESTAMP",
+          "primaryKey": false,
+          "nullable": false,
+          "default": "NOW()"
+        },
+        {
+          "name": "updated_at",
+          "type": "TIMESTAMP",
+          "primaryKey": false,
+          "nullable": false,
+          "default": "NOW()"
+        }
+      ],
+      "indexes": [],
+      "foreignKeys": []
+    }
+  ],
+  "migrations": []
+}

package/templates/dot-ai/subagents/frontend.md

@@ -10,6 +10,14 @@ from the design, you do not redesign it. You do not make generic AI-looking page
 - `.ai/design/style-tile.html`, when it exists. Match its fonts, colors, corners and spacing.
 - Read a whole contract file only when a slice is missing. Do not load everything up front.
 
+## 2.5 Design read (before coding)
+For Standard or Full work that renders a page or screen, state in one line what you build:
+"Reading this as: [page kind] for [audience], in the [chosen direction] style."
+Take it from the design brief, the chosen direction and the style tile. If they do not
+settle it, escalate with `architectural_ambiguity`. Do not guess a direction.
+For Quick work, work with no screen, or a project with no design brief, match the existing
+components and `.ai/codebase_map.md` instead.
+
 ## 3. Build from the design
 `.ai/ui_specs.md` is the source of truth. Use these parts of it:
 - **Design brief and chosen direction:** who uses it, the tone, what to avoid.
@@ -65,6 +73,23 @@ These match the Anti-Generic Checklist in `.ai/ui_specs.md`:
 - No greeting banners ("Welcome back!"). Let the content speak.
 - No emojis anywhere in code or UI. Icons are inline vector SVG.
 
+### 7.1 Build-time details
+The font, color and layout choices are made at design time (the Anti-Generic Checklist in
+`.ai/ui_specs.md`). These are the details that go wrong while building:
+- One accent color and one corner-radius scale, from the tokens, on every component.
+  A button or link that needs a different color is a spec gap: escalate it.
+- Large display type with tight line height clips the tails of y, g, j, p and q, worst in
+  italics. Keep display line height at 1.1 or more.
+- Images come from the spec. If one is missing, leave a clearly labeled placeholder and
+  list the images still needed in your report. Never fake a product screenshot out of
+  boxes, and never fill space with hand-drawn illustrations.
+- Logos are real vector files, never a company name typed out as text.
+- Numbers shown in the UI come from the spec's content samples or real data. Do not
+  invent precise-looking figures such as "92%" or "4.1x".
+- One label per action: if the spec says "Contact us", do not add "Get in touch" elsewhere.
+- Marketing or landing page: also follow the Marketing pages part of the checklist, when
+  `.ai/ui_specs.md` has one.
+
 ## 8. States and access
 - Loading: a skeleton with the same size as the loaded content, so nothing jumps.
 - Empty: a short explanation and a primary action.
@@ -81,3 +106,11 @@ These match the Anti-Generic Checklist in `.ai/ui_specs.md`:
 2. Check the source for emojis. There must be none.
 3. Check the UI has no sideways scrolling or clipping on phone, tablet and desktop widths.
 4. Check every item in the task's `acceptanceCriteria`.
+5. Pre-flight, all must pass:
+   - Button labels, inputs, placeholders and form labels meet contrast: 4.5:1 for body
+     text, 3:1 for large text.
+   - Button labels fit on one line at desktop width.
+   - The accent color and corner radius are the same everywhere.
+   - Re-read every string you wrote that the spec did not give. Rewrite anything vague,
+     broken or invented.
+   - Marketing or landing page: run the Marketing pages checks, when the checklist has them.

package/templates/dot-ai/ui_specs.md

@@ -183,6 +183,23 @@ One or two. Everything else stays restrained.
 - [ ] No decorative blobs.
 - [ ] No greeting banners.
 - [ ] No emojis. Icons are vector SVG.
+- [ ] No serif by default. A serif needs a stated reason (editorial, heritage) in the brief.
+- [ ] One font family, unless the tokens define a heading and body pairing.
+- [ ] No purple or blue glow gradients and no neon mesh backgrounds unless the brief asks.
+- [ ] No warm beige with brass accents as the automatic "premium" look. Pick it only on purpose.
+- [ ] One accent color and one palette temperature (warm or cool grays, not both).
+- [ ] One corner-radius scale for every surface.
+
+**Marketing pages** (landing, product and pricing pages)
+- [ ] The hero fits the first screen: headline of at most 2 lines, subtext of about 20 words, the main button visible without scrolling.
+- [ ] The hero holds at most 4 things: an optional small label, headline, subtext, buttons (one primary, at most one secondary). Logo walls go in their own section below.
+- [ ] No more than 2 image-and-text split sections in a row.
+- [ ] Small uppercase labels above headings: at most one for every 3 sections.
+- [ ] Each section layout (3-column cards, split, bento) appears once per page.
+- [ ] Real images and real vector logos. No mock screenshots built from boxes, no text-only page.
+- [ ] Sections stay short: a headline of about 8 words, about 25 words of text, one visual or one button. More than 5 items need a grid, tabs or a carousel.
+- [ ] Every figure comes from real data or is marked as a sample.
+- [ ] One label per action across the page ("Contact us" everywhere, not three variants).
 
 **Mobile**
 - [ ] No default Material seed blue.