You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/framework/prompts/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ is written in TypeScript any more, so prompting can change without touching the
6
6
| file | what it is |
7
7
|---|---|
8
8
|`system_prompt.md`| The built-in system prompt (#326). Rom's doc. |
9
-
|`build_prompt.md` / `extend_prompt.md`/ `scaffold_prompt.md`| The prompts a build session opens with (#1347): greenfield, existing codebase (#185), and the scaffold retry (#182). `${{ tf.prompt }}` is the user's intent. |
9
+
|`extend_prompt.md`| The prompt a build session opens with (#1347): deliver the intent within the existing codebase (#185). `${{ tf.prompt }}` is the user's intent. |
10
10
|`protocols/await.md`| How to emit an awaited choice so the turn-boundary gate can detect it (#337/#339). |
11
11
|`protocols/signal.md`| How to emit `setSessionName()` / `setReadyForMerge()` (#326). |
12
12
|`presets/*.md`| One file per preset button: research (#331), readability (#360), maintainability (#361), security_audit (#461), ux (#472). |
Copy file name to clipboardExpand all lines: packages/framework/prompts/SPEC.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Every prompt The Framework sends an agent lives here as markdown. Nothing agent-
13
13
-**The data-branch protocol** - where the framework's own data lives and how to read and write it without putting it on a code branch.
14
14
-**The protocols** - how an agent signals: awaited choices, session name and ready for merge, plus the sections added only when it has a browser, when it runs hands-off, and when nothing can answer its questions.
15
15
-**The presets** - one file per launcher button and per routine prompt.
16
-
-**The build-opening prompts** - the three framings a build agent can open with: the greenfield build, the existing-codebase variant, and the scaffold retry for a build that produced nothing.
16
+
-**The build-opening prompt** - the one framing a build agent opens with: deliver the work within the existing codebase.
17
17
-**The on-before-mergeable prompt** - the optional extra turn a finished agent gets, queueing quality follow-ups and folding what it learned into the knowledge base.
18
18
-**Prompts are reviewed before they land** - a prompt change goes through review like any other change.
19
19
@@ -47,7 +47,7 @@ See `## User story`.
47
47
-**The triage scope rule** — the one-paragraph rule appended to both triage presets, that a triage only queues work and never implements it.
48
48
-**The protocols** — how an agent signals to The Framework, and what this particular agent can do.
49
49
-**The presets** — one file per preset: the launcher's buttons and the daemon's routine prompts.
50
-
-**The build-opening prompts** — the greenfield build, the existing-codebase variant chosen when the workspace already holds source, and the scaffold retry sent when a build's opening turn left the workspace empty.
50
+
-**The build-opening prompt** — the existing-codebase framing every build agent opens with: a project is a repo that already exists.
51
51
-**The on-before-mergeable prompt** — the extra turn an agent gets when it signals ready for merge, if the user turned that on.
Copy file name to clipboardExpand all lines: packages/framework/src/steps.SPEC.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,8 @@
1
-
The prompts a build agent opens with, and the one check that decides between them: whether the workspace already holds an app.
1
+
The opening prompt of a build agent, filled withthe user's intent.
2
2
3
-
## Business logic — TL;DR
3
+
## Business logic
4
4
5
-
-**Three build-opening prompts, filled with the user's intent** - the greenfield build prompt, the existing-codebase prompt (chosen when the workspace already holds source at build time), and the scaffold retry (sent when a build's opening turn left the workspace empty). Each prompt's text is authored as markdown in the prompts directory like every other agent-facing prompt; what happens here is only the choice between them and filling in the intent.
6
-
-**Workspace-emptiness check** - a workspace counts as empty when it holds no source file the agent could have produced: lockfiles, dotfiles, and dependency/output directories (node_modules, .git, dist, build caches) do not count. Best-effort and cheap — it stops at the first real file, treats an unreadable or missing directory as empty, and never throws.
5
+
A build agent's opening prompt is the existing-codebase framing — a project is a repo that already exists, so there is exactly one framing. Its text is authored as markdown in the prompts directory like every other agent-facing prompt; what happens here is only filling in the intent. The old greenfield and scaffold-retry framings (build an app in an empty folder) were removed: no product path leads a build agent into an empty workspace any more.
0 commit comments