Scaffold C++20 screencast project with Meson, agent workflow, and phase plan

2026-08-28 21:54:32 +02:00
commit 742611b841
25 changed files with 1322 additions and 0 deletions
@@ -0,0 +1,51 @@
+---
+name: agent-memory
+description: |
+  Persistent handoff memory for multi-session agent work on the screen_cast
+  project. Read this skill at the start of every new agent conversation so the
+  current thread can bootstrap context from the repository rather than from chat
+  history.
+disable-model-invocation: false
+---
+
+## Always read at the start of a new conversation
+
+1. `AGENTS.md` — mandatory project workflow.
+2. This skill (`agent-memory/SKILL.md`).
+3. `.agents/MEMORY.md` — current handoff log.
+4. Any domain-specific `RUNBOOK.md` relevant to the task (e.g.
+   `docs/RUNBOOK.md`).
+5. All other skills applicable to the task (see `AGENTS.md` skill selection).
+
+## Purpose
+
+Zed agent threads do not share conversation history. This project therefore
+keeps the shared state in the repository itself:
+
+- `.agents/MEMORY.md` — rolling handoff log: current focus, completed work,
+  open blockers, decisions, files that matter.
+- `<domain>/RUNBOOK.md` — operational memory for recurring workflows
+  (build/CI, capture validation, networking smoke tests).
+
+Both files are ordinary markdown under git, so their history is preserved.
+
+## After significant work
+
+Update `.agents/MEMORY.md`:
+
+- **Current focus**: one-line summary of what the thread was working on.
+- **Completed**: concrete outcomes, file paths, commits.
+- **Open issues / blockers**: anything unresolved at the end of the thread.
+- **Decisions & conventions**: choices that future threads must respect.
+- **Files that matter right now**: paths the next thread should read first.
+
+Update domain `RUNBOOK.md` when the task reveals a reusable observation:
+
+- non-obvious build or dependency workarounds;
+- validation steps that caught errors;
+- commands or snippets that should be reused.
+
+## When starting a new thread
+
+Paste a brief handoff if helpful, but **do not rely on it**. Always verify the
+actual current state from the memory files, git log, and the relevant code.