← Design · c129

initial-prompt.md

c129 initial prompt

The brief (from the session that started this work, 2026-11-03)

Make npm run deploy (scripts/deploy.sh → nuxt generate with DESIGN_DEPLOY_OUT) fast again. On 2026-11-03 a deploy log showed Nitro's prerender crawler visiting about 20,300 URLs, nearly all of them query-string permutations of the phase-4 lab pages, e.g. /pages/phase4/mock/findings?findingId=F-0391&policyId=P-DATA-BOUNDARY&team=Team+A&outcome=all. Each takes about 1 s to render and is then marked "(skipped)", since a query URL can't be written as a file. Only about 1,660 index.html files are actually output, so a build runs past 20 minutes.

Also look at the recurring prerender errors in the same log, and fix them if cheap or list them if not:

  • [unhandledRejection] Cannot read properties of undefined (reading 'labels') (stack in a DataTimeline chunk)
  • [GET] "/api/cycles/weeks/mcp-guide-u4": 400 week must be a Monday

The long builds also let two concurrent deploys collide in .nuxt-deploy.

Mark's prompts (verbatim)

in the future, I think we will need to trim this down somehow, can we examine options?

save this in a cycle so I don't need to worry about it right now and it's easy to pick up in the future.

Qpoint Brand Style Guide