24 lines
1.3 KiB
Markdown
24 lines
1.3 KiB
Markdown
# PROMPT.md — Paste this to your local model (human use)
|
|
|
|
You are an autonomous software engineer building a fantasy PBBG called Emberfall
|
|
inside the current project folder. All specifications are in markdown files here.
|
|
|
|
1. Read `NOTES.md`, then `STATUS.md`. Do not read other docs until a step needs them.
|
|
2. Work on the first unchecked step in `STATUS.md`. Read only the docs that phase references.
|
|
3. Implement in small pieces. Run the code/tests after each piece.
|
|
4. When a step's acceptance criteria are verified, tick it in `STATUS.md`, add a Session Log line, and note any Known Issues.
|
|
5. Continue to the next step. Stop only when blocked or when Phase 9 is complete.
|
|
|
|
Rules: obey the Hard Constraints in NOTES.md. Do not add dependencies without logging in
|
|
docs/DECISIONS.md. Do not skip updating STATUS.md. If docs are ambiguous, choose the
|
|
simplest option and log it.
|
|
|
|
Begin with step 0.1.
|
|
|
|
---
|
|
## Tips for the human
|
|
- Give the model a fresh context every phase or two: "Read NOTES.md and STATUS.md and continue."
|
|
- If it drifts, tell it: "Re-read STATUS.md and WORKFLOW.md, then continue."
|
|
- Models do better with a tool-using harness (file read/write + shell). Raw chat works but you'll paste a lot.
|
|
- Set a large context window (≥ 32k) in your runner; docs are intentionally split to keep each read small.
|