From 10135b3d363fd2b4afcdd0d561485483e12fd11b Mon Sep 17 00:00:00 2001 From: Martin Dvorak Date: Thu, 24 Sep 2026 10:01:55 +0000 Subject: [PATCH] SMP window fills and centres instead of top-aligning; require opencode.md sync alongside README --- opencode.md | 39 ++++++++++++++++++++++--------------- src/app/components/apps.tsx | 2 +- src/app/skeuo.css | 4 ++++ 3 files changed, 28 insertions(+), 17 deletions(-) diff --git a/opencode.md b/opencode.md index f20a8fb..3af8c41 100644 --- a/opencode.md +++ b/opencode.md @@ -5,22 +5,29 @@ a minute. Read this first, then skim the files it points at. --- -## Keep README.md in sync — do this on EVERY prompt +## Keep README.md AND opencode.md in sync — do this on EVERY prompt -**Before you finish any task, update `README.md` so it still matches the code.** -This is a standing requirement, not a one-off. The README is meant to describe the -project as it is right now, so treat it as part of "done": +**Before you finish any task, update the docs so they still match the code.** +This is a standing requirement, not a one-off, so treat it as part of "done": -- If a change adds/removes/renames a feature, script, route, app, theme, file or - dependency, reflect it in `README.md` (Features, Tech Stack, API Routes, Project - Structure, Scripts, running/deploying sections — whichever apply). -- Re-read `README.md` and the files you touched; fix anything the change made stale. -- Keep the author's voice and existing emoji-section formatting; don't rewrite the - whole thing when a small edit will do. -- If a task genuinely changes nothing user- or contributor-visible, it's fine to - leave the README untouched — use judgement, don't churn it for nothing. +**`README.md`** is the user/contributor-facing doc. If a change adds/removes/renames +a feature, script, route, app, theme, file or dependency, reflect it in `README.md` +(Features, Tech Stack, API Routes, Project Structure, Scripts, running/deploying +sections — whichever apply). -When in doubt, prefer updating it. A stale README is treated as a bug. +**`opencode.md`** (this file) is the cold-boot doc for the next session. Update it in +the same task whenever a change touches anything it describes — architecture, the key +files and their invariants, conventions/gotchas, history, or testing notes. A stale +`opencode.md` is worse than none: it actively misleads the next session. + +For both docs: +- Re-read the doc and the files you touched; fix anything the change made stale. +- Keep the author's voice and existing formatting; don't rewrite the whole thing when + a small edit will do. +- If a task genuinely changes nothing that either doc describes, it's fine to leave + that doc untouched — use judgement, don't churn it for nothing. + +When in doubt, prefer updating. A stale README **or** opencode.md is treated as a bug. --- @@ -244,9 +251,9 @@ list reordering, not free placement. Don't confuse the two. ## After finishing — push to git -First make sure `README.md` is up to date (see "Keep README.md in sync" at the -top), then run **only** these three commands (no extra flags, no rebasing, no -force-push): +First make sure `README.md` **and** `opencode.md` are up to date (see "Keep +README.md AND opencode.md in sync" at the top), then run **only** these three +commands (no extra flags, no rebasing, no force-push): ```bash git add . diff --git a/src/app/components/apps.tsx b/src/app/components/apps.tsx index d198dc7..48755a3 100644 --- a/src/app/components/apps.tsx +++ b/src/app/components/apps.tsx @@ -752,7 +752,7 @@ export const SMP_APP: AppDef = { icon: "🎮", color: "#c0392b", width: 560, - height: 430, + height: 400, content: , }; diff --git a/src/app/skeuo.css b/src/app/skeuo.css index 64fcf36..1a5ff61 100644 --- a/src/app/skeuo.css +++ b/src/app/skeuo.css @@ -625,7 +625,11 @@ a.win-icon { .smp { display: flex; flex-direction: column; + justify-content: center; gap: 14px; + /* Fill the window body so the menu centres instead of leaving a gap under it; + a short window scrolls via .win-body's overflow. */ + min-height: 100%; font-family: "Monocraft", "JetBrains Mono", monospace; color: #e6e6e6; background-color: #313131;