@dfosco/storyboard 0.9.4 → 0.9.5

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@dfosco/storyboard",
-    "version": "0.9.4",
+    "version": "0.9.5",
     "type": "module",
     "license": "MIT",
     "description": "Storyboard prototyping framework — core engine, React integration, and canvas",

package/scaffold/AGENTS.md

@@ -161,40 +161,6 @@ The `storyboard` CLI (`sb` alias) wraps dev tooling. The standard `npm run dev`
 
 For the full canvas CLI reference (positioning, batch ops, collision detection), invoke the **canvas** skill.
 
-### Dev URLs
-
-With Caddy proxy running (set up via `npm run setup`):
-- Main: `http://storyboard.localhost/storyboard/`
-- Worktree `fix-bug`: `http://storyboard.localhost/fix-bug/storyboard/`
-
-Without proxy (fallback with port numbers):
-- Main: `http://localhost:1234/storyboard/`
-- Worktree: `http://localhost:<port>/storyboard/`
-
-### Dev URL session state
-
-Whenever Copilot starts a dev server (e.g. `npm run dev`), save the URL as `devURL` in the SQL session database. Read the proxy URL from the dev server's startup output (`[storyboard] proxy URL: <url>`):
-
-```sql
-INSERT OR REPLACE INTO session_state (key, value) VALUES ('devURL', 'http://storyboard.localhost/storyboard/');
-```
-
-If the proxy is not running, fall back to the direct URL from the output (`[storyboard] direct URL: <url>`).
-
-This `devURL` is used as the default target by the **agent-browser** skill when the user says "inspect the browser", "check the page", etc. — no URL argument needed.
-
-**How `devURL` gets set:**
-- **Automatically** — when Copilot runs `npm run dev` (or directly `storyboard dev`), persist the proxy URL (or direct URL if no proxy) to `devURL`.
-- **From user input** — if the user says "the dev server is at http://localhost:3000", save that as `devURL`.
-- **Implicitly from inspection** — if no `devURL` is set and the user says "inspect http://storyboard.localhost/storyboard/", that URL becomes the `devURL` for the rest of the session.
-
-**How `devURL` gets read:**
-- Before opening a browser with `agent-browser`, always check for a saved `devURL`:
-  ```sql
-  SELECT value FROM session_state WHERE key = 'devURL';
-  ```
-- If set, use it as the default URL. If not set, ask the user or fall back to `http://storyboard.localhost/storyboard/`.
-
 ---
 
 ## Architecture
@@ -232,14 +198,9 @@ The fix was a one-line compaction (4MB → 9KB). Everything the user reported
 
 ## Key Conventions to follow at all times
 
-- Use **Primer React** components from `@primer/react` for all UI elements
 - Use **semantic HTML tags** whenever they are appropriate in between Primer React components
-- Use **Primer Octicons** from `@primer/octicons-react` for icons
-  - **Before importing any icon, verify it exists in `.agents/data/primer-octicons.json`** (the authoritative export list, generated from the installed package). Agents frequently invent icon names like `ScissorsIcon` that do not exist and break the page at runtime. If the icon you want is not in that list, pick the closest available name from the list — never guess.
-  - Regenerate the list after bumping `@primer/octicons-react`: `node scripts/gen-octicons-list.mjs`
 - Use the **canvas widget type registry** at `.agents/data/widget-types.json` as the authoritative list of valid canvas widget `type` strings, their props, default sizes, and when-to-use guidance. Never invent widget types. In particular: when showing multiple variants of a single story file, use ONE `component-set` widget — not N `story` widgets. Regenerate after changing the widget registry: `node scripts/gen-widget-types.mjs`.
 - Use **CSS Modules** (`*.module.css`) for component-specific styles
-  - If you find any `sx` styled-components styling, migrate them to CSS Modules
 - **Components must live in their own directory:** `src/components/Name/Name.jsx`, `Name.module.css`, `name.story.jsx`. Never place component files flat in `src/components/`.
 - **Always use the `create` skill** when creating new components or stories — don't manually create files.
 - **Every piece of data consumed in a page must gracefully handle `null` or `undefined` without crashing.** Since flow data, records, and overrides can all be partial, incomplete, or missing, components must never assume a field exists. Use optional chaining, fallback values, or conditional rendering for every data access.
@@ -252,14 +213,6 @@ The fix was a one-line compaction (4MB → 9KB). Everything the user reported
 
 ---
 
-## Key anti-patterns to avoid
-
-- **DO NOT EVER USE** `<Box>` components
-- **DO NOT EVER USE** `sx` styled-components
-- **DO NOT USE `useState` in pages or components.** All state management must happen through storyboard hooks (`useFlowData`, `useOverride`, `useObject`, `useRecord`, etc.). Storyboard state lives in the URL hash — not in React component state.
-
----
-
 ## Storyboard Data System
 
 The storyboard data system separates UI prototype data from components using JSON files discovered by a Vite plugin at dev/build time.
@@ -347,38 +300,6 @@ Access with `useRecord('posts')` in a `pages/posts/[id].jsx` dynamic route page.
 
 ---
 
-### External Prototypes
-
-An **external prototype** links to a prototype hosted at an external URL. It appears in the viewfinder alongside regular prototypes but opens in a new tab instead of navigating within the app.
-
-To create one, add a folder inside `src/prototypes/` with only a `.prototype.json` file containing a `url` field:
-
-```json
-// my-external-app.prototype.json
-{
-  "meta": {
-    "title": "External App",
-    "description": "Hosted on another domain",
-    "author": ["dfosco"]
-  },
-  "url": "https://example.com/prototype"
-}
-```
-
-No `index.jsx` or flow files are needed — the folder only contains the `.prototype.json`.
-
-**Behavior:**
-- Shows up in the viewfinder with an "external" badge
-- Clicking opens the URL in a new tab (`target="_blank"`)
-- Can live inside `.folder/` directories for grouping
-- Supports all standard metadata (`title`, `description`, `author`, `icon`, `tags`, `team`)
-
-**Creating via Workshop UI:** Use the "New prototype" workshop action and check the "External prototype" checkbox, then provide the URL.
-
-**Creating via Agent:** Create the folder and `.prototype.json` file directly — no special commands needed.
-
----
-
 ### Template Variables
 
 Data files support **build-time template variables** using `${variableName}` syntax within JSON string values. Variables are resolved by the Vite data plugin based on the file's location — no runtime overhead.