KB-599B

UI Preview Master Homepage Governance Index — 06 Prompt Templates

3 min read Revision 1
ui-previewmaster-homereportprompt-templates2026-05-30

Prompt Templates (Cowork / Agent operations)

Copy-paste templates for routine workspace operations. All keep the no-mutation, no-overwrite, no-self-approval rules.

1. Add a new UI surface to the master list

Add a new UI surface to the UI Preview master manifest.
- id: <kebab-id>   group: <core-mow-mot|moit-mout|governance-ops|registry-managers>
- surface_name: <name>   description: <one line>
- status: idea   approval_status: none
- owner_agent: <claude-design|claude-code>   next_action: <step>
- dependencies: [<ids>]
Append the row to _master/v1/manifest.json (do not touch other rows), redeploy manifest.json,
verify HTTP 200, then report the new total. No PG/Directus/Qdrant. No fake approvals.

2. Deploy a new version of an existing preview

Deploy <project>/<surface> vN to /ui-preview/<project>/<surface>/vN/.
Gate 0 first (host=contabo, route works). Do NOT overwrite the previous version.
Deploy via tar over ssh contabo. Verify vN HTTP 200. Then update the surface review-log and
set the manifest row's current_version=vN, preview_url, checklist.preview_deployed=true,
status=preview_deployed. Redeploy manifest.json. No DB mutation.

3. Update status / checklist after GPT review

GPT reviewed <surface>. Set checklist.gpt_reviewed=true and status=needs_review (or
design_polish if review requests visual changes). Record the review notes in the surface
review-log under a dated entry. Redeploy manifest.json. Do not set user_approved (human only).

4. Mark a surface user-approved

User approved <surface> on <date>. Record the approval verbatim in the surface review-log,
set checklist.user_approved=true, approval_status=user_approved, status=approved in the
manifest row, and redeploy manifest.json. Only do this with an explicit human approval message;
never self-approve.

5. Create a Claude Design brief for a selected surface

Create a Claude Design brief for <surface> at knowledge/dev/ui/<surface>/design-brief.md.
Base it on its spec (knowledge/dev/ui/<surface>/spec.md) and the relevant handoff/Phase1 KB
docs. Cover: intent, layout, components, visual tokens (#639922/#ef9f27/#e24b4a), states,
and what is design vs engineering. Then set the manifest row's design_brief_path and redeploy
manifest.json. Document-only; no DB mutation.
Back to Knowledge Hub knowledge/dev/reports/architecture/ui-preview-master-homepage-governance-index-2026-05-30/06-prompt-templates.md