Let UI Prototype start from a Notebook tab, filling its request box on Start fresh

AI Assisted
This commit is contained in:
jparkerweb committed 2026-11-12 10:35:29 -08:00
1 parent fde92ef4d2
commit c6265795ea
9 files changed
+38 -12

No files matched your search

+3 -2
View File
@@ -57,8 +57,9 @@ Read `./AGENTS.md` when it exists: its stack, its style files and its convention
### Step 1: Start
1. Run `sweep --project .` silently.
2. **The kind.** From the request: a **screen**, a **flow** (several screens of one journey, shown side by side, not linked) or a **terminal** screen. Ask only when it cannot be told.
3. **What can be carried over.** Read source files only: stylesheets, theme and config files (a Tailwind or theme config, CSS custom properties, design files), and component files. For each of the five items (colors, fonts, spacing, components, layout) note what you found and where (`src/styles/theme.css`: accent #0f766e, gray #64748b), or "none found". Note the app's own font files when it ships some (at most 4, 2 MB together). A project with no screens yet skips the checklist: say you found no existing look and start fresh.
2. **The request.** When nothing yet says what to prototype (no argument, no host handing it over), ask for it first, in one question (console: the request card in `notes/ui-prototype.md`). Images sent with the answer are Step 2's images.
3. **The kind.** From the request: a **screen**, a **flow** (several screens of one journey, shown side by side, not linked) or a **terminal** screen. Ask only when it cannot be told.
4. **What can be carried over.** Read source files only: stylesheets, theme and config files (a Tailwind or theme config, CSS custom properties, design files), and component files. For each of the five items (colors, fonts, spacing, components, layout) note what you found and where (`src/styles/theme.css`: accent #0f766e, gray #64748b), or "none found". Note the app's own font files when it ships some (at most 4, 2 MB together). A project with no screens yet skips the checklist: say you found no existing look and start fresh.
### Step 2: The starting screen
+1 -1
View File
@@ -114,7 +114,7 @@ const isFile = (p) => {
// The workflows a tab can be sent to from the dashboard, and the spec a Revise
// plan send names.
export const SENT_WORKFLOWS = ["pathfinder", "plan", "quick-task", "revise-plan", "diagnose"];
export const SENT_WORKFLOWS = ["pathfinder", "plan", "quick-task", "revise-plan", "diagnose", "ui-prototype"];
const SENT_SPEC_RE = /^specs\/[A-Za-z0-9._-]+$/;
// A tab's `sent` record as stored, or null when it does not hold up.
+8
View File
@@ -1,5 +1,13 @@
# UI Prototype
## The request
Nothing yet says what to prototype: before Step 1, one `--wait` card (a Notebook tab fills it):
```jsonc
{"title":"UI prototype","items":[{"id":"request","kind":"text","title":"What to prototype","fill":"note","body":"The screen or flow, and what it is for."}]}
```
## Starting card
One `--wait` batch after Step 1. A card cannot open with its boxes ticked, so the carry-over card's preset ticks every found item in one press, and a Skip on it keeps everything found (all ticked is the default); leave the card out for a project with no screens:
+8 -6
View File
@@ -710,15 +710,17 @@ export function cardAvailability(entry, scan, sel, lookup = stateFor) {
}
// The cards whose confirm pane offers "Start with a note from your Notebook"
// on Start fresh: the three that open on an idea box.
const NOTE_FRESH_CARDS = new Set(["plan2code-0-pathfinder", "plan2code-1-plan", "plan2code-quick-task"]);
// on Start fresh: the three that open on an idea box, and UI Prototype, whose
// request box it fills.
const NOTE_FRESH_CARDS = new Set(["plan2code-0-pathfinder", "plan2code-1-plan", "plan2code-quick-task", "plan2code-ui-prototype"]);
/**
* Whether a lit card's confirm pane offers the Notebook switch: Pathfinder,
* Plan and Quick Task on Start fresh (no spec picked), Diagnose whenever it is
* lit (it launches untargeted, so a picked spec does not matter), and Revise
* plan on a picked spec with no plan change brief waiting (a waiting brief is
* what that revision is about). Never on a grayed card, never on any other card.
* Plan, Quick Task and UI Prototype on Start fresh (no spec picked), Diagnose
* whenever it is lit (it launches untargeted, so a picked spec does not
* matter), and Revise plan on a picked spec with no plan change brief waiting
* (a waiting brief is what that revision is about). Never on a grayed card,
* never on any other card.
*/
export function noteSwitchShows(entry, scan, sel) {
if (!entry || !cardAvailability(entry, scan, sel).on) return false;
+4 -3
View File
@@ -1564,9 +1564,10 @@
</li>
<li>
A lit card's confirm pane can offer <strong>Start with a note from
your Notebook</strong>. On the dashboard, Pathfinder, Plan and Quick
Task offer it on Start fresh, and Revise plan on a picked spec with
no plan change waiting. A tab you started a workflow with wears a
your Notebook</strong>. On the dashboard, Pathfinder, Plan, Quick
Task and UI Prototype offer it on Start fresh, Diagnose whenever
it is lit, and Revise plan on a picked spec with no plan change
waiting. A tab you started a workflow with wears a
small <strong>sent</strong> badge.
</li>
<li>