goose-graphics

9 steps · start to finish.

1. 1
   Step 1

   Environment Setup

   ▶

   Create the output directory, verify Node.js and Python are available, and install any missing runtime helpers.

   mkdir -p /app/results /app/results/work
   command -v node >/dev/null || { echo "ERROR: node is required"; exit 1; }
   command -v npx >/dev/null || { echo "ERROR: npx is required"; exit 1; }
   python - <<'PY'
   import json, pathlib
   pathlib.Path('/app/results/validation_report.json').write_text(json.dumps({
     "setup": "started"
   }, indent=2))
   PY
   

2. 2
   Step 2

   Resolve Inputs

   ▶

   Read the requested visual brief and normalize optional parameters. If `brief` is missing, ask one focused question before continuing. Default `output_dir` to `/app/results`, default `format` to a single PNG render, and leave `style` unset until discovery if the operator did not p

3. 3
   Step 3

   Discover Style And Format

   ▶

   Use the Gooseworks catalog to list or search published styles and formats. Prefer the most specific style whose description matches the brief, then fetch the slim `DESIGN.md` spec for the chosen style and any selected format.

4. 4
   Step 4

   Prepare References

   ▶

   If image references are provided, copy them into `/app/results/work/references` and extract any reusable style notes before generating HTML. Keep references optional; a text-only brief is valid.

5. 5
   Step 5

   Generate HTML

   ▶

   Generate a self-contained HTML file at `/app/results/work/goose-graphics.html`. The HTML must implement the selected visual style, include all required assets inline or by stable local paths, and be sized for the target format.

6. 6
   Step 6

   Screenshot Render

   ▶

   Render the HTML with Playwright or an equivalent browser screenshot tool and write the final PNG to `/app/results/goose-graphics.png`. Capture browser console errors in `/app/results/browser_console.json` when the renderer supports it.

7. 7
   Step 7

   Validate Outputs

   ▶

   Check that the generated PNG and HTML exist, are non-empty, and that the PNG has plausible dimensions. Record the validation result in `/app/results/validation_report.json`.

8. 8
   Step 8

   Iterate on Errors (max 3 rounds)

   ▶

   If validation fails or the render is visibly incomplete, perform up to max 3 rounds of targeted fixes. Each round should change only the HTML, referenced assets, or renderer settings needed to satisfy the validation finding, then re-run the screenshot and validation steps.

9. 9
   Step 9

   Final Checklist

   ▶

   Run the final verification script and write `/app/results/summary.md`.