@jay-framework/aiditor 0.17.4 → 0.18.0

package/dist/prompts/add-page-figma-brief-prompt.md

@@ -0,0 +1,163 @@
+# Add Page — Figma brief generator prompt
+
+Copy everything below the line into **ChatGPT, Claude, Cursor**, or any vision-capable AI agent. Attach a **full-page Figma screenshot** (desktop; optional mobile frame as a second image).
+
+Optionally add a few lines of project context before or after the prompt (target route, plugins, “match home header”, etc.).
+
+If you have a separate **design definitions** frame (brand colors, typography, logo), run [add-page-figma-design-definitions-prompt.md](./add-page-figma-design-definitions-prompt.md) or [add-page-figma-design-from-image-prompt.md](./add-page-figma-design-from-image-prompt.md) first and paste that output at the top of **Design** in AIditor. For a page mock only (no token board), prefer the **design-from-image** prompt.
+
+---
+
+You are helping me prepare an **AIditor Add Page brief** for a Jay Stack web project.
+
+I will attach a screenshot of my **Figma web page design** (and optionally a mobile frame). Your job is **not** to write code. Produce two markdown briefs I can paste into AIditor’s Add Page composer: **Content** and **Design**.
+
+## What I may also provide (optional)
+
+- Target URL route (e.g. `/pricing`, `/products/[slug]`)
+- Page name / purpose in one sentence
+- Plugins or headless contracts we must use (e.g. product search, cart)
+- “Match existing site header/footer from home”
+- Copy that must appear verbatim
+- Links/CTAs and where they go
+- Dynamic vs static route preference
+
+If I did not provide something, **infer cautiously from the screenshot** and mark uncertain items with `(confirm with team)`.
+
+## Output format (strict)
+
+Respond with **exactly** these sections, in order:
+
+### 1. Suggested page route
+
+One line:
+
+- **Route:** `/example` or `/products/[slug]`
+- **Route kind:** `static` or `dynamic` (dynamic only if the page clearly needs a URL parameter)
+- **One-line purpose:** what this page is for
+
+### 2. Content brief (paste into AIditor → Content)
+
+Use this structure:
+
+```markdown
+# <Page title>
+
+## Purpose
+
+<1–3 sentences>
+
+## Route notes
+
+- Target route: <same as above>
+- Dynamic params: <if any, what they represent>
+
+## Copy & content blocks
+
+<List every visible text block: hero, sections, cards, labels, buttons, legal, etc. Use exact wording from the design when readable; otherwise [placeholder: describe intent]>
+
+## Behavior & interactions
+
+- Navigation: <header/footer links if visible>
+- Buttons/CTAs: <label → destination or action>
+- Forms: <fields, validation hints if visible>
+- States: <empty, loading, error, sold out, etc. if implied>
+- Responsive behavior: <what stacks, hides, or changes on mobile if a mobile frame was provided>
+
+## Plugins & contracts (Jay headless)
+
+- If I named plugins/contracts: list each as:
+  `- Plugin: @jay-framework/<plugin-name> / contract: <contract-name>`
+- If none were named: write `None identified — static/marketing page unless user specifies` OR list **suspected** integrations as `(possible — confirm)` only when the UI clearly needs backend data (product grid, cart, search, auth, etc.)
+
+## SEO / meta (if inferable)
+
+- Title, description hints
+
+## Open questions
+
+- Bullet list of anything ambiguous from the screenshot
+```
+
+### 3. Design brief (paste into AIditor → Design)
+
+Use this structure:
+
+```markdown
+## Overall layout
+
+- Page structure top → bottom (hero, sections, grid, footer)
+- Max content width / alignment if visible
+- Match existing site chrome: <yes/no — header/footer like home if I said so>
+
+## Typography
+
+- Headings: <sizes/weight/style as seen>
+- Body: <size, line-height if inferable>
+- Notable text styles (labels, captions, prices)
+
+## Color & surfaces
+
+- Backgrounds, text colors, borders, cards, buttons (use hex if you can estimate from the image; else descriptive)
+- Primary / secondary CTA styling
+
+## Spacing & components
+
+- Section padding rhythm
+- Card/grid patterns (columns, gaps, radius, shadows)
+- Images/media treatment (aspect ratios, full-bleed, etc.)
+
+## Breakpoints
+
+- Desktop: <summary from main screenshot>
+- Mobile: <summary if mobile image provided; else “assume stack vertically, full-width CTAs”>
+
+## Reference alignment
+
+- Primary visual reference: `references/figma-desktop.png` (user will attach this file in AIditor)
+- Secondary: <other frames if any>
+
+## Assets likely needed in the build (for AIditor Assets, not References)
+
+List images/icons that should **ship on the page** (hero photos, logos, illustrations), not the whole mock:
+
+- e.g. `assets/hero.jpg`, `assets/icon-check.svg`
+  Mark `(export from Figma)` where the user must supply files.
+
+## Accessibility notes (brief)
+
+- Contrast concerns, focus states, alt text hints for key images
+```
+
+### 4. Checklist before I submit in AIditor
+
+Short bullet list:
+
+- [ ] Route does not already exist in our app (I will verify)
+- [ ] I will paste Content and Design into the two composer fields
+- [ ] I will attach the **same Figma screenshot(s)** under **References** (inspiration)
+- [ ] I will upload real images/icons under **Assets** only if they should appear on the live page
+- [ ] I filled in any `(confirm)` items
+
+## Rules
+
+1. **Separate concerns:** behavior/copy/plugins → Content; look-and-feel → Design.
+2. **Be specific:** prefer measurable notes (e.g. “3-column pricing cards, 24px gap”) over “modern and clean.”
+3. **Do not invent** plugin names, API shapes, or routes I did not imply — use `(confirm)` instead.
+4. **Do not output code** (no HTML, React, or Jay).
+5. If text in the screenshot is unreadable, use `[illegible]` and describe placement.
+6. Keep total output **under ~1200 words** unless the page is very large.
+
+## Attachments
+
+[Figma screenshot(s) attached by user]
+
+---
+
+## Lite version (power users)
+
+```text
+From this Figma screenshot, write two AIditor Add Page briefs (Content = behavior/copy/plugins; Design = layout/colors/type/spacing). Suggest route static/dynamic. Use Design log #14-style markdown, mark guesses (confirm), list references/figma-desktop.png and assets to export. No code.
+```
+
+See [add-page-figma-brief-instructions.md](./add-page-figma-brief-instructions.md) for the full workflow. Design log: [14 - aiditor-add-page-request.md](../../../design-log/14%20-%20aiditor-add-page-request.md).

package/dist/prompts/add-page-figma-design-definitions-prompt.md

@@ -0,0 +1,256 @@
+# Add Page — Figma design definitions → markdown prompt
+
+Use this when you have a **Figma design definitions** frame (brand colors, typography scale, logo treatment) **in addition to** a page mock.
+
+Typical frames look like: **Brand Colors** swatches with hex labels, **EN Brand Font** with family name and H1–H8 sizes, and a **logo / wordmark** sample.
+
+**If the user only has a page mock or reference screenshot (no token board),** use [add-page-figma-design-from-image-prompt.md](./add-page-figma-design-from-image-prompt.md) instead — it infers design tokens from visible UI.
+
+**Related docs**
+
+- Page mock → brief: [add-page-figma-brief-prompt.md](./add-page-figma-brief-prompt.md)
+- Full workflow: [add-page-figma-brief-instructions.md](./add-page-figma-brief-instructions.md)
+
+Copy everything below the line into your AI agent. Attach:
+
+1. **Design definitions** screenshot (colors + type + logo frame), and
+2. **Page mock** screenshot (optional but recommended — run the page prompt after, or combine both images in one message).
+
+---
+
+You are converting a **Figma design definitions** board into markdown sections for **AIditor Add Page**.
+
+AIditor uses two composer fields:
+
+| Field                      | What belongs here                                                                                                 |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| **Design** (`design.md`)   | Tokens (colors, fonts, type scale), logo usage, surfaces, spacing — **everything from the definitions board**     |
+| **Content** (`content.md`) | Page copy, CTAs, plugins, behavior — **not** the definitions board (unless the board specifies brand voice rules) |
+
+Your job: read the definitions image and output markdown that the **Add Page implementation agent** can follow. **Do not write code.**
+
+## Input you receive
+
+- Screenshot(s) of Figma **design definitions** (brand colors, typography, logo).
+- Optional: short note — e.g. “Brand INTIMA”, “reuse on all marketing pages”, “match existing Jay home header”.
+
+## Conversion rules (Figma → Add Page markdown)
+
+### 1. Brand colors → `## Design tokens — color`
+
+- Extract **every labeled hex** (e.g. under swatches). Use the **printed hex code**, not a guess from pixel color.
+- If a swatch color and its label disagree, output the **label hex** and add `(swatch appears different — verify in Figma)`.
+- Name tokens semantically for this brand (not `Color 1`):
+
+  | Figma label / role           | Markdown token name                   |
+  | ---------------------------- | ------------------------------------- |
+  | Tallest / primary brand pink | `brand-primary` or `color-brand-rose` |
+  | Secondary pink               | `brand-secondary`                     |
+  | Light background pink        | `background-page` or `surface-canvas` |
+  | Accent / deep accent         | `accent` or `cta`                     |
+
+- Format as a **table** plus optional CSS custom properties block:
+
+````markdown
+## Design tokens — color
+
+| Token             | Hex     | Use on page                                  |
+| ----------------- | ------- | -------------------------------------------- |
+| `brand-primary`   | #EAA3B1 | Logo, key headings                           |
+| `brand-secondary` | #D68D9A | Secondary emphasis                           |
+| `background-page` | #FFF4F6 | Page background                              |
+| `accent`          | #F9CCD3 | Accents, borders, highlights (verify swatch) |
+
+```css
+/* Suggested CSS variables for implementation agent */
+--color-brand-primary: #eaa3b1;
+--color-brand-secondary: #d68d9a;
+--color-background-page: #fff4f6;
+--color-accent: #f9ccd3;
+```
+````
+
+````
+
+### 2. Typography → `## Design tokens — typography`
+
+- Extract **font family** exactly as shown (e.g. **Didot**).
+- List **weights** shown (Regular, Bold, etc.).
+- Copy the **type scale table** (H1–H8 and px values) verbatim when readable.
+- Map each level to **semantic usage** on a web page (agent needs intent, not only numbers):
+
+```markdown
+## Design tokens — typography
+
+- **Font family (brand):** Didot, serif fallback stack: Didot, "Didot LT STD", "Bodoni MT", Georgia, serif
+- **Weights:** Regular 400, Bold 700 (confirm in Figma if other weights exist)
+
+| Level | Size | Weight | Typical use |
+| --- | --- | --- | --- |
+| H1 | 108px | Regular | Hero display (desktop; scale down on mobile) |
+| H2 | 88px | Regular | Section titles |
+| H3 | 68px | Regular | Subsection titles |
+| H4 | 58px | Regular | Card titles |
+| H5 | 48px | Regular | Feature headings |
+| H6 | 38px | Regular | Labels / large UI text |
+| H7 | 28px | Regular | Body large / nav |
+| H8 | 14px | Regular | Captions, legal, meta |
+
+- **Character set note:** Brand uses full alphanumeric + symbols as in Figma sample.
+- **Responsive:** Scale display sizes (H1–H4) down ~40–60% on mobile unless page brief says otherwise.
+````
+
+- If the board is **English-only** (“EN Brand Font”), note: `Other locales: (not defined in this board)`.
+
+### 3. Logo / wordmark → `## Brand mark`
+
+- Describe logo **text**, **color** (hex from definitions), **case** (e.g. INTIMA all caps).
+- Say whether the logo is **text-only** or includes a mark/icon.
+- Specify implementation hint for Add Page agent:
+
+```markdown
+## Brand mark
+
+- Wordmark: **INTIMA** — all caps, Didot, color `#EAA3B1` (or `brand-primary`)
+- Background behind mark in board: `#FFF4F6` (`background-page`) — use as page canvas, not necessarily behind logo on every page
+- **Asset:** If user exports logo as SVG/PNG → `assets/logo-intima.svg` (user uploads in AIditor Assets). If text-only, agent may render as styled text per tokens above.
+```
+
+### 4. What does NOT go in Design from definitions alone
+
+Do **not** invent page layout, sections, or CTAs from a definitions-only board. Those come from the **page mock** brief ([add-page-figma-brief-prompt.md](./add-page-figma-brief-prompt.md)).
+
+Put in **Content** only if the board explicitly states:
+
+- Brand voice / tone rules
+- Required legal line
+- Link domains or social handles
+
+Otherwise Content stays minimal:
+
+```markdown
+# <Page name> (fill when combining with page mock)
+
+## Brand
+
+- Apply design tokens from Design brief (INTIMA brand definitions).
+- No extra plugins unless specified separately.
+```
+
+## Output format (strict)
+
+Produce **one block** the user can paste into AIditor **Design** (and a tiny **Content** stub if definitions-only):
+
+### Design brief — paste into AIditor → Design
+
+```markdown
+# Brand design system — <Brand name>
+
+> Source: Figma design definitions board. Apply to this page and match existing site chrome if noted below.
+
+## Design tokens — color
+
+<table>
+
+## Design tokens — typography
+
+<table>
+
+## Brand mark
+
+<logo rules>
+
+## Implementation notes for Jay / AIditor agent
+
+- Use tokens above in page `.jay-html` styles (inline or project CSS).
+- Prefer CSS variables for colors; use exact px sizes for desktop, clamp or media queries for mobile.
+- If project already has global styles, **merge** — do not duplicate conflicting font imports.
+- Logo: <text-only | file assets/logo-...>
+
+## Open questions
+
+- <anything illegible or ambiguous>
+```
+
+### Content stub (only if definitions-only, no page mock yet)
+
+```markdown
+# Page TBD
+
+## Brand
+
+- Use Design brief tokens for <Brand name>.
+- Page structure, copy, and CTAs: add when page mock brief is ready.
+```
+
+### Checklist for user
+
+- [ ] Pasted **Design** section into AIditor Design field (append to page design notes if combined)
+- [ ] Attached definitions screenshot as **Reference** (`references/figma-design-definitions.png`)
+- [ ] Exported logo/icons as **Assets** if they are image files (not text-only wordmark)
+- [ ] Combined with page mock brief for layout and copy
+
+## Rules
+
+1. **Hex from labels** — always prefer printed `#RRGGBB` under swatches.
+2. **No invented tokens** — if a value is unreadable, write `[illegible]` and ask user to confirm.
+3. **No code files** — only markdown tables and optional CSS variable suggestions inside fenced blocks.
+4. **Separate brand vs page** — definitions → Design; page behavior → Content (from page prompt).
+5. Keep definitions output **under ~600 words** unless the board has many extra sections (spacing grid, shadows, components).
+
+## Example (INTIMA-style board)
+
+**Input:** Brand frame with INTIMA wordmark, Didot H1–H8 scale, four pink swatches (#EAA3B1, #D68D9A, #FFF4F6, #F9CCD3).
+
+**Output fragment (Design brief):**
+
+```markdown
+# Brand design system — INTIMA
+
+## Design tokens — color
+
+| Token             | Hex     | Use on page                                  |
+| ----------------- | ------- | -------------------------------------------- |
+| `brand-primary`   | #EAA3B1 | Wordmark, primary brand elements             |
+| `brand-secondary` | #D68D9A | Secondary text and UI                        |
+| `background-page` | #FFF4F6 | Page canvas / section backgrounds            |
+| `accent`          | #F9CCD3 | Highlights (verify swatch vs label in Figma) |
+
+## Design tokens — typography
+
+- **Font family:** Didot (serif), with system serif fallbacks
+- **Weights:** Regular, Bold
+
+| Level | Size  | Typical use          |
+| ----- | ----- | -------------------- |
+| H1    | 108px | Hero display         |
+| H2    | 88px  | Major section titles |
+| H3    | 68px  | Subsections          |
+| H4    | 58px  | Cards                |
+| H5    | 48px  | Features             |
+| H6    | 38px  | Large UI             |
+| H7    | 28px  | Body emphasis        |
+| H8    | 14px  | Captions / meta      |
+
+## Brand mark
+
+- **INTIMA** — uppercase, Didot, color `brand-primary` (#EAA3B1)
+- Canvas in board: `background-page` (#FFF4F6)
+
+## Implementation notes for Jay / AIditor agent
+
+- Apply tokens to new page; scale H1–H4 down on mobile.
+- Wordmark may be HTML text styled with Didot + `brand-primary` unless user provides `assets/logo-intima.svg`.
+```
+
+---
+
+## Combining with a page mock
+
+**Recommended order**
+
+1. Run **this prompt** with the definitions screenshot → paste into **Design** (top of field).
+2. Run [add-page-figma-brief-prompt.md](./add-page-figma-brief-prompt.md) with the page screenshot → append page layout/spacing to **Design**; put copy/CTAs in **Content**.
+3. In AIditor: attach **both** PNGs as **References**; export any raster logos/backgrounds as **Assets**.
+
+Or send **both images in one message** with this prompt first, then: “Now also produce Content + page-specific Design sections from the second image (page mock).”

package/dist/prompts/add-page-figma-design-from-image-prompt.md

@@ -0,0 +1,144 @@
+# Add Page — Design brief from image (definitions board or reference mock)
+
+Use this when you want **Design** markdown for AIditor Add Page from **any** screenshot:
+
+- A formal **Figma design definitions** board (colors, typography scale, logo), **or**
+- A **page mock**, landing page, or reference UI where tokens must be **inferred** from the visible design
+
+**Related docs**
+
+- Page mock → Content brief: [add-page-figma-brief-prompt.md](./add-page-figma-brief-prompt.md)
+- Formal definitions only (external workflow): [add-page-figma-design-definitions-prompt.md](./add-page-figma-design-definitions-prompt.md)
+- Full workflow: [add-page-figma-brief-instructions.md](./add-page-figma-brief-instructions.md)
+
+Copy everything below the line into your AI agent, or use **Fill from image** on the Design section in AIditor (Design log #17).
+
+Attach **one or more images** (definitions board, page/reference mock, desktop + mobile, etc.). Optional short note in chat or AIditor **Context notes**: brand name, “match home header”, which image is which (`Image 1 = desktop`, `Image 2 = brand colors`).
+
+---
+
+You are producing **Design** markdown for **AIditor Add Page**. **Do not write code.** **Do not** write page copy, CTAs, or plugin lists — those belong in Content.
+
+## Step 1 — Detect input mode
+
+Look at the attached image and choose **one** mode:
+
+| Mode                          | Image looks like                                                                                    | Your job                                                                  |
+| ----------------------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
+| **A — Definitions board**     | Labeled color swatches, typography scale table (H1–H8), logo specimen, “Brand Colors”, “Brand Font” | Extract **labeled tokens** (hex from printed labels, type scale verbatim) |
+| **B — Reference / page mock** | Full webpage, app screen, marketing layout, Dribbble shot — **no** token board                      | **Infer** a practical design brief from visible UI                        |
+
+If both appear in one image (definitions + mock), extract tokens from the definitions area **and** layout notes from the mock area.
+
+## Mode A — Definitions board
+
+Follow the same rules as [add-page-figma-design-definitions-prompt.md](./add-page-figma-design-definitions-prompt.md):
+
+1. **Colors** — every labeled `#RRGGBB`; semantic token names; table + optional CSS variables block.
+2. **Typography** — font family as shown; weights; H1–H8 (or equivalent) table with px and typical web use.
+3. **Brand mark** — wordmark/logo rules, colors, asset hints.
+4. Do **not** invent page sections or CTAs from a definitions-only board.
+
+## Mode B — Reference / page mock (infer design system)
+
+When there is **no** token board, build the best design brief you can from the screenshot:
+
+### Colors
+
+- Identify **dominant** background, primary text, secondary/muted text, primary CTA, secondary CTA, borders, card surfaces.
+- Output hex **estimates** from the image; suffix with `(estimated from screenshot)` unless a hex label is visible.
+- Prefer a small semantic palette (5–8 tokens), not every pixel color.
+
+### Typography
+
+- Describe **hierarchy**: hero/display, H1–H3 equivalents, body, captions — relative size, weight, serif vs sans.
+- Name a font family **only** if clearly identifiable (e.g. distinctive geometric sans) or shown in the design; otherwise `sans-serif (similar to modern grotesk — confirm)`.
+- Do **not** fabricate a full H1–H8 px table unless the image shows a type scale.
+
+### Layout & components
+
+- Page structure **top → bottom** (header, hero, sections, footer).
+- Grid patterns (columns, gaps), max content width, alignment.
+- Buttons, cards, inputs: shape (radius), fill vs outline, shadow depth.
+- Images/media: aspect ratios, full-bleed vs contained.
+
+### Spacing
+
+- Section padding rhythm, card gaps, header height — use px estimates where helpful.
+
+### Breakpoints
+
+- If a mobile frame is visible, summarize differences.
+- If desktop only: note “mobile: stack sections, full-width CTAs unless specified elsewhere”.
+
+### Brand mark
+
+- If logo/wordmark visible: describe treatment and color; suggest `assets/logo.svg` only if it is clearly a raster/logo asset, not plain text.
+
+### Honesty rules for Mode B
+
+- Mark inferred values `(estimated — confirm)`.
+- Use `[illegible]` for unreadable text.
+- Do not invent plugin names, routes, or API behavior.
+
+## Output format (strict)
+
+Respond with **one markdown document** for AIditor **Design** only:
+
+```markdown
+# Design brief — <page or brand name if inferable>
+
+> Source: <definitions board | reference mock>. Mode: <A | B>.
+
+## Design tokens — color
+
+<table and/or list>
+
+## Design tokens — typography
+
+<family, weights, hierarchy table — no fake scale if Mode B>
+
+## Layout & components
+
+<structure, grids, buttons, cards, media>
+
+## Spacing & surfaces
+
+<section rhythm, shadows, radius>
+
+## Breakpoints
+
+<desktop / mobile notes>
+
+## Brand mark
+
+<if applicable>
+
+## Reference alignment
+
+- Primary visual reference: user will attach this screenshot in AIditor References
+- Assets likely needed: <list shippable images/icons, not the whole mock>
+
+## Implementation notes for Jay / AIditor agent
+
+- Apply tokens in `.jay-html` styles; prefer CSS variables for colors from Mode A
+- Merge with existing project globals if user noted “match home”
+- Mode B tokens are estimates — refine during implementation
+
+## Open questions
+
+- <ambiguities>
+```
+
+Keep output **under ~800 words** for Mode B, **~600** for Mode A unless the board is large.
+
+## Rules
+
+1. **Design only** — no Content brief, no code files.
+2. **Mode A:** hex from **labels**, not pixel picking when labels exist.
+3. **Mode B:** infer cautiously; label estimates clearly.
+4. **No invented plugins or routes.**
+
+## Attachments
+
+[Image attached by user]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jay-framework/aiditor",
-  "version": "0.17.4",
+  "version": "0.18.0",
   "type": "module",
   "description": "AIditor — visual AI-driven code editor plugin for Jay Framework",
   "main": "dist/index.js",
@@ -25,6 +25,23 @@
     "./list-freezes.jay-action": "./dist/actions/list-freezes.jay-action",
     "./submit-task.jay-action": "./dist/actions/submit-task.jay-action",
     "./read-file.jay-action": "./dist/actions/read-file.jay-action",
+    "./check-add-page-route.jay-action": "./dist/actions/check-add-page-route.jay-action",
+    "./start-add-page-request.jay-action": "./dist/actions/start-add-page-request.jay-action",
+    "./save-add-page-draft.jay-action": "./dist/actions/save-add-page-draft.jay-action",
+    "./upload-add-page-asset.jay-action": "./dist/actions/upload-add-page-asset.jay-action",
+    "./reclassify-add-page-asset.jay-action": "./dist/actions/reclassify-add-page-asset.jay-action",
+    "./submit-add-page.jay-action": "./dist/actions/submit-add-page.jay-action",
+    "./check-page-add-page-brief.jay-action": "./dist/actions/check-page-add-page-brief.jay-action",
+    "./open-add-page-from-brief.jay-action": "./dist/actions/open-add-page-from-brief.jay-action",
+    "./generate-add-page-brief-from-image.jay-action": "./dist/actions/generate-add-page-brief-from-image.jay-action",
+    "./check-plugin-update.jay-action": "./dist/actions/check-plugin-update.jay-action",
+    "./list-jay-plugins.jay-action": "./dist/actions/list-jay-plugins.jay-action",
+    "./list-plugin-contracts.jay-action": "./dist/actions/list-plugin-contracts.jay-action",
+    "./ensure-project-plugin.jay-action": "./dist/actions/ensure-project-plugin.jay-action",
+    "./get-plugin-setup-status.jay-action": "./dist/actions/get-plugin-setup-status.jay-action",
+    "./rerun-plugin-setup.jay-action": "./dist/actions/rerun-plugin-setup.jay-action",
+    "./sync-add-page-plugin-manifest.jay-action": "./dist/actions/sync-add-page-plugin-manifest.jay-action",
+    "./write-plugin-source.jay-action": "./dist/actions/write-plugin-source.jay-action",
     "./dist/pages/aiditor/page.jay-html": "./dist/pages/aiditor/page.jay-html",
     "./dist/pages/aiditor/page.css": "./dist/pages/aiditor/page.css"
   },
@@ -34,7 +51,7 @@
     "validate": "jay-stack-cli validate-plugin",
     "build:client": "vite build",
     "build:server": "vite build --ssr",
-    "build:copy-assets": "mkdir -p dist/actions dist/pages/aiditor && cp lib/*.jay-contract* dist/ && cp lib/actions/*.jay-action* dist/actions/ && cp lib/pages/aiditor/page.jay-html dist/pages/aiditor/ && cp lib/pages/aiditor/page.css dist/pages/aiditor/ && cp lib/pages/aiditor/page.jay-contract* dist/pages/aiditor/",
+    "build:copy-assets": "mkdir -p dist/actions dist/pages/aiditor dist/add-page-agent dist/prompts && cp lib/*.jay-contract* dist/ && cp lib/actions/*.jay-action* dist/actions/ && cp lib/pages/aiditor/page.jay-html dist/pages/aiditor/ && cp lib/pages/aiditor/page.css dist/pages/aiditor/ && cp lib/pages/aiditor/page.jay-contract* dist/pages/aiditor/ && cp add-page-agent/*.md dist/add-page-agent/ && cp ../../docs/add-page-figma-brief-prompt.md ../../docs/add-page-figma-design-definitions-prompt.md ../../docs/add-page-figma-design-from-image-prompt.md dist/prompts/",
     "build:types": "tsup lib/index.ts lib/index.client.ts --dts-only --format esm",
     "build:check-types": "tsc",
     "clean": "rimraf dist",
@@ -42,16 +59,16 @@
   },
   "dependencies": {
     "@anthropic-ai/claude-agent-sdk": "0.2.119",
-    "@jay-framework/fullstack-component": "^0.17.4",
-    "@jay-framework/stack-client-runtime": "^0.17.4",
-    "@jay-framework/stack-server-runtime": "^0.17.4",
+    "@jay-framework/fullstack-component": "^0.18.0",
+    "@jay-framework/stack-client-runtime": "^0.18.0",
+    "@jay-framework/stack-server-runtime": "^0.18.0",
     "busboy": "^1.6.0",
     "html2canvas": "^1.4.1",
     "zod": "^4.3.6"
   },
   "devDependencies": {
-    "@jay-framework/compiler-jay-stack": "^0.17.4",
-    "@jay-framework/jay-cli": "^0.17.4",
+    "@jay-framework/compiler-jay-stack": "^0.18.0",
+    "@jay-framework/jay-cli": "^0.18.0",
     "@types/busboy": "^1",
     "rimraf": "^5.0.5",
     "tsup": "^8.5.1",

package/plugin.yaml

@@ -19,6 +19,40 @@ actions:
     action: submit-task.jay-action
   - name: readFileAction
     action: read-file.jay-action
+  - name: checkAddPageRouteAction
+    action: check-add-page-route.jay-action
+  - name: startAddPageRequestAction
+    action: start-add-page-request.jay-action
+  - name: saveAddPageDraftAction
+    action: save-add-page-draft.jay-action
+  - name: uploadAddPageAssetAction
+    action: upload-add-page-asset.jay-action
+  - name: reclassifyAddPageAssetAction
+    action: reclassify-add-page-asset.jay-action
+  - name: submitAddPageAction
+    action: submit-add-page.jay-action
+  - name: checkPageAddPageBriefAction
+    action: check-page-add-page-brief.jay-action
+  - name: openAddPageFromBriefAction
+    action: open-add-page-from-brief.jay-action
+  - name: generateAddPageBriefFromImageAction
+    action: generate-add-page-brief-from-image.jay-action
+  - name: checkPluginUpdateAction
+    action: check-plugin-update.jay-action
+  - name: listJayPluginsAction
+    action: list-jay-plugins.jay-action
+  - name: listPluginContractsAction
+    action: list-plugin-contracts.jay-action
+  - name: ensureProjectPluginAction
+    action: ensure-project-plugin.jay-action
+  - name: getPluginSetupStatusAction
+    action: get-plugin-setup-status.jay-action
+  - name: rerunPluginSetupAction
+    action: rerun-plugin-setup.jay-action
+  - name: syncAddPagePluginManifestAction
+    action: sync-add-page-plugin-manifest.jay-action
+  - name: writePluginSourceAction
+    action: write-plugin-source.jay-action
 
 routes:
   - path: /aiditor