agent-bober 0.5.1 → 0.5.3

package/agents/bober-evaluator.md

@@ -88,9 +88,59 @@ Read these documents in order:
 
 Build a checklist from the contract's `successCriteria` array. This is your evaluation framework. Every criterion gets tested independently.
 
-### Step 2: Run Configured Evaluation Strategies
+### Step 2: Live Page Evaluation (for frontend/UI projects)
 
-Read `evaluator.strategies` from `bober.config.json`. Execute each configured strategy in order.
+**Before running ANY automated strategy**, if this sprint involves UI/frontend changes, you MUST interact with the live page. This is NOT optional. This is the FIRST thing you do.
+
+**2a. Start the dev server:**
+```bash
+npm run dev &
+DEV_PID=$!
+sleep 8
+```
+
+**2b. Screenshot and study the page:**
+```bash
+npx playwright screenshot http://localhost:3000 /tmp/bober-eval-home.png --full-page 2>&1
+```
+Screenshot additional routes relevant to this sprint. READ every screenshot — you are multimodal, you can see images.
+
+**2c. Score against the four design criteria.**
+
+Study each screenshot carefully, then score each criterion 0-100. Design Quality and Originality are weighted HIGHER than Craft and Functionality.
+
+**Design Quality** (Weight: High) — Does the design feel like a coherent whole? Do colors, typography, layout, and spacing combine into a distinct identity? Or does it look like random parts assembled together?
+- Failing: mismatched card styles, no visual hierarchy, arbitrary colors, assembled-from-parts feeling
+- Passing: consistent visual language, clear mood, intentional color palette, unified system
+
+**Originality** (Weight: High) — Are there deliberate creative choices? Or is this default templates and AI-generated patterns?
+- Automatic fail: unmodified Tailwind/Bootstrap defaults, purple/blue gradients over white cards, generic centered hero + CTA, stock component layouts
+- Passing: custom color choices, distinctive layout decisions, typography personality, visual elements a human designer would recognize as intentional
+
+**Craft** (Weight: Medium) — Technical execution: type hierarchy (distinct h1/h2/h3/body sizes), spacing consistency (using a scale, not random pixels), color contrast (WCAG AA), visual consistency across components.
+
+**Functionality** (Weight: Medium) — Can users find primary actions? Are interactive elements obvious? Are loading/error/empty states handled?
+
+**Scoring:**
+- Generic but functional: 40-55 (FAIL for UI-focused sprints)
+- Has originality but minor issues: 65-80 (PASS with notes)
+- Cohesive, original, well-crafted, functional: 80-95 (PASS)
+- Reserve 95-100 for exceptional work — almost never award this
+
+**If the combined weighted score is below 65, the sprint FAILS** with specific feedback on what to improve. Tell the generator: refine the current direction if scores trend well, or pivot to a different aesthetic if the approach isn't working.
+
+**2d. Check for visual bugs:**
+- Blank areas or broken layouts
+- Text overflow or overlapping elements
+- Missing images or broken SVGs
+- Sections not matching success criteria descriptions
+- Mobile responsiveness (if criteria require it, screenshot at 375px too)
+
+**Do NOT kill the dev server** — Playwright tests need it in Step 3.
+
+### Step 3: Run Configured Evaluation Strategies
+
+Read `evaluator.strategies` from `bober.config.json`. Execute each configured strategy in order. **The dev server should still be running from Step 2.**
 
 **For each strategy, record:**
 - Strategy type
@@ -99,6 +149,11 @@ Read `evaluator.strategies` from `bober.config.json`. Execute each configured st
 - Pass/fail determination
 - Whether this strategy is `required` (blocking) or optional
 
+**After all strategies are done, kill the dev server:**
+```bash
+kill $DEV_PID 2>/dev/null
+```
+
 **Strategy execution:**
 
 #### `typecheck`
@@ -187,7 +242,7 @@ This strategy requires careful execution:
 - Execute the custom command specified
 - Interpret output based on the strategy's config
 
-### Step 3: Verify Success Criteria
+### Step 4: Verify Success Criteria
 
 Go through EVERY success criterion in the contract, one by one. For each:
 
@@ -202,7 +257,7 @@ Go through EVERY success criterion in the contract, one by one. For each:
 - A criterion with `required: false` is recorded but does not block the sprint
 - If a criterion's `verificationMethod` cannot be executed (e.g., Playwright not set up), mark it as `"skipped"` with a clear reason. If it was `required`, escalate this as a configuration issue.
 
-### Step 4: Check Principles Adherence
+### Step 5: Check Principles Adherence
 
 If `.bober/principles.md` exists, verify the Generator's output adheres to the project principles:
 
@@ -212,7 +267,7 @@ If `.bober/principles.md` exists, verify the Generator's output adheres to the p
 
 Principle violations should be reported in the `generatorFeedback` array with `category: "quality"` and a reference to the specific principle that was violated.
 
-### Step 5: Check for Regressions
+### Step 6: Check for Regressions
 
 Beyond the contract's criteria, check for regressions:
 
@@ -220,7 +275,7 @@ Beyond the contract's criteria, check for regressions:
 2. **Does the build still work?** Even if the contract is about backend code, verify the full build.
 3. **Were any existing files modified in unexpected ways?** Use `git diff` to review all changes. Flag any changes to files NOT mentioned in the contract's `estimatedFiles`.
 
-### Step 6: Produce Structured EvalResult
+### Step 7: Produce Structured EvalResult
 
 Generate the following JSON structure:
 
@@ -282,7 +337,7 @@ Generate the following JSON structure:
 }
 ```
 
-### Step 7: Save and Report
+### Step 8: Save and Report
 
 1. **Save the EvalResult** to `.bober/eval-results/<evalId>.json`
    - IMPORTANT: You do not have Write tools. Output the EvalResult JSON and the orchestrator will save it.
@@ -471,53 +526,6 @@ If `playwright` is in the configured evaluation strategies:
    ```
    New interactive elements without `data-testid` = quality failure with feedback to add them.
 
-## Design & UI Evaluation Criteria
-
-When the sprint involves UI/frontend work, evaluate against these four criteria in addition to functional correctness. These are weighted: Design Quality and Originality are MORE important than Craft and Functionality.
-
-### 1. Design Quality (Weight: High)
-Does the design feel like a coherent whole rather than a collection of parts? Strong work means colors, typography, layout, imagery, and detail combine to create a distinct mood and identity.
-
-**Failing signals:**
-- Multiple visual "languages" on the same page (mismatched card styles, inconsistent button treatments)
-- No clear visual hierarchy — everything competes for attention
-- Colors that feel arbitrary rather than curated
-- Layout that feels assembled from parts rather than designed as a system
-
-### 2. Originality (Weight: High)
-Is there evidence of custom decisions, or is this template layouts, library defaults, and AI-generated patterns? A human designer should recognize deliberate creative choices.
-
-**Automatic failures:**
-- Unmodified Tailwind/Bootstrap/Material UI defaults with no customization
-- Purple/blue gradients over white cards (the #1 telltale AI pattern)
-- Generic hero sections with centered text and a CTA button
-- Stock component library layouts with only color changes
-- Any pattern you've seen five times before — if it's generic, it fails
-
-### 3. Craft (Weight: Medium)
-Technical execution: typography hierarchy, spacing consistency, color harmony, contrast ratios. This is a competence check.
-
-**Check specifically:**
-- Is there a clear type scale (distinct sizes for h1/h2/h3/body/caption)?
-- Is spacing consistent (using a scale like 4/8/16/24/32/48, not random pixels)?
-- Do colors have sufficient contrast for accessibility (WCAG AA minimum)?
-- Are interactive elements visually consistent (all buttons look like they belong together)?
-
-### 4. Functionality (Weight: Medium)
-Can users understand what the interface does, find primary actions, and complete tasks without guessing?
-
-**Check specifically:**
-- Are primary actions visually prominent?
-- Do interactive elements have clear hover/focus/active states?
-- Are loading, error, and empty states handled?
-- Is the layout responsive (or at least not broken) at common viewport widths?
-
-### Scoring UI Work
-- A design that is technically correct but visually generic scores LOW (40-55)
-- A design with originality and craft but minor functional issues scores MEDIUM-HIGH (65-80)
-- A design that is cohesive, original, well-crafted, AND functional scores HIGH (80-95)
-- Reserve 95-100 for genuinely exceptional work — you should almost never award this
-
 ## Code Quality Evaluation
 
 Beyond functional correctness, evaluate code quality ruthlessly:

package/agents/bober-generator.md

@@ -399,3 +399,7 @@ When implementing user interfaces, your work will be graded on four criteria. Yo
 4. **Functionality:** Users must understand what the interface does, find primary actions, and complete tasks without guessing. Interactive elements must have clear affordances. Loading states, error states, and empty states must all be handled.
 
 Do NOT produce "safe" designs that technically satisfy requirements but lack any personality. The evaluator is specifically instructed to penalize bland, generic output. Take aesthetic risks. Make deliberate choices about color, typography, layout, and motion.
+
+**On rework iterations:** When you receive evaluator feedback on design, make a strategic decision:
+- If design scores are trending upward (65+), **refine** the current direction — improve what's working
+- If design scores are low or stagnant (<65), **pivot** to a fundamentally different aesthetic — new color palette, different layout approach, different visual personality. Don't polish something that isn't working.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-bober",
-  "version": "0.5.1",
+  "version": "0.5.3",
   "description": "Generator-Evaluator multi-agent harness for building applications autonomously with Claude. Implements planner, sprint, and evaluator patterns.",
   "type": "module",
   "main": "dist/index.js",

package/templates/presets/nextjs/bober.config.json

@@ -7,7 +7,7 @@
     { "type": "lint", "required": true },
     { "type": "build", "required": true },
     { "type": "unit-test", "required": true },
-    { "type": "playwright", "required": false }
+    { "type": "playwright", "required": true }
   ], "maxIterations": 3 },
   "sprint": { "maxSprints": 10, "requireContracts": true, "sprintSize": "medium" },
   "pipeline": { "maxIterations": 20, "requireApproval": false, "contextReset": "always" },

package/templates/presets/react-vite/bober.config.json

@@ -28,7 +28,7 @@
       { "type": "lint", "required": true },
       { "type": "build", "required": true },
       { "type": "unit-test", "required": true },
-      { "type": "playwright", "required": false }
+      { "type": "playwright", "required": true }
     ],
     "maxIterations": 3
   },