The design/pages/execute prompt
The whole text of config/agent-prompts/design/pages/execute.md, as an agent is handed it.
Bundled agent prompts — one row of 30, exported from
config/agent-prompts
· every prompt
· the resolution order
What this prompt is
| id | design/pages/execute | the key every tier, every pattern step and every override spells it by |
| kind | stage instruction | whether any bundled pattern hands it to an agent step |
| role | build | the harness role the agent reading it runs under |
| stage | execute | the stage of a run it is handed at |
| bundled at | config/agent-prompts/design/pages/execute.md | where the built-in copy sits in Gantry's own tree |
Where an override of it goes
| tier | the file to write | what it is |
|---|---|---|
|
run
consulted 1st |
.gantry/<plan>/prompts/design/pages/execute.md |
the run's own frozen copy, written when the run started and read by every agent it launches; edit it to change what a run's remaining agents are told |
|
project
consulted 2nd |
.gantry/<plan>/design/pages/execute.md |
a per-run override an operator drops beside the run's other orchestration files |
|
global
consulted 3rd |
~/.config/gantry/agent-prompts/design/pages/execute.md |
the materialized global mirror; it overrides the built-in once its bytes differ from the built-in's |
|
built-in
consulted 4th |
config/agent-prompts/design/pages/execute.md |
the default compiled into the binary |
The text
Build exactly one real page from the design brief named by the ticket below. The deliverable is the
reachable page itself: route, controller/action, view or partials, stylesheet in the project's own
layers, and a minimal render test.
Read the brief end to end, then read the design system, reference pages, and data contract it names.
Design the page from the brief's purpose and functions; do not copy an existing page with nouns swapped.
Handle every required state on mobile and desktop, use the project's tokens and components, and keep the
result native to this codebase.
Stay within the ticket. If the brief or required systems are missing or impossible to satisfy, write
`{{BLOCKED_PATH}}` with `value = "blocked"` and explain the blocker in your final response.
{{SPRINT}}