What this project has already learned the hard way, and where any new such fact belongs. Two jobs. (1) Routing: this project keeps NO per-project Claude memories — read this before writing anything down, and pick a durable home from the list here. (2) An index, by area, of non-obvious facts worth knowing before you guess: debugging rigs and measurements that lie, iOS/WebKit and the tethered iPhone, the Windows app, production and deployment, and general codebase traps. Use before setting up a browser- or server-driven debugging session, when a bug reproduces only on iPhone, in Safari or in the Windows app, before changing deployment configuration or reading store/crash data, when something behaves unexpectedly and you are about to guess why, and whenever you are tempted to record a fact for later.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This project — and every ActualChat-* clone or sibling (C1, C2, Marketing, …) — keeps no
per-project Claude memories. Those memory/ directories stay empty. A fact learned here
belongs somewhere durable: checked in, visible to every clone, and readable by Alex.
Ask Alex where it should go, and offer the destinations:
| Destination | For |
|---|---|
areas/*.md here | A project quirk — a couple of sentences, full write-up in references/<area>/ |
docs/CODING_STYLE.md | Anything about how code in this repo should be written |
docs/** | How a subsystem actually behaves (live-video/, live-audio/, ui/, …) |
The owning .claude/commands/*.md or skill | When the fact is really "how to use this tool correctly" |
AGENTS-Source.md | A rule every agent must have in context in every session (then run ai update-md) |
| A GitHub issue | Open follow-up work — not a memory |
~/.claude/CLAUDE.md | Only if it is about Alex or his machine, not about this project |
| Nowhere | A one-off finding about a bug that is already fixed |
Why: Claude memories are per-project-directory and do not cross the Docker (-proj-…) and
Windows (D--Projects-…) views of the same repo, so anything written there is duplicated,
invisible from the other side, and lost to everyone else. Everything above is in git.
Before adding an entry, check it is still true. Several memories migrated here in September 2026 named symbols that no longer existed. An entry that describes code is worth only as much as its last verification.
| Area | What it covers |
|---|---|
| Debugging | Servers and builds, the browser rigs, measurements that lie, calling a running server |
| iOS / WebKit | Driving and profiling the tethered iPhone, channels that lie, Safari, builds and signing |
| Windows | Diagnosing the WinUI/WebView2 app, native stack sampling, echo cancellation |
| Infrastructure | Deployment and Flux, reaching the clusters, the external consoles |
| General | Performance traps and build-tool traps in the codebase itself |
Each area file is a short index; the long write-up for an entry lives in
references/<area>/<name>.md.
Related skills with their own depth: /server-loop, /debug-ui, /virtual-list-debug,
/gcloud-dev-logs, /gcloud-prod-logs, /soniox-sweep, and the user-level /macmini.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Delete the `-bak` backup branches that `/prepare-merge` leaves behind, local and on origin, once the work they back up has merged. Use when the user says "remove my bak branches", "clean up bak branches", "delete the backups", or "/clean-bak-branches".
日本語の概要は準備中です。原文の説明を表示しています。
Use when work on a branch is finished and the next step is a pull request — "create a PR", "open a PR", "push and PR this", "/create-pr" — when a draft PR should be marked ready for review — "mark the PR ready", "undraft it", "it's ready for review" — or right after either has happened and the team has not been told about it yet.
日本語の概要は準備中です。原文の説明を表示しています。
Search Google Cloud (GKE) server logs of the DEV environment (dev.voxt.ai). Use when troubleshooting anything that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check GCP logs", "check server logs on dev", or gives a dev.voxt.ai timeline from a client console log.
日本語の概要は準備中です。原文の説明を表示しています。
Search Google Cloud (GKE) server logs of the PROD environment. Use when troubleshooting a production incident that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check PROD logs", "check production server logs", or gives a production timeline from a client console log.
日本語の概要は準備中です。原文の説明を表示しています。
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).
日本語の概要は準備中です。原文の説明を表示しています。
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations.
日本語の概要は準備中です。原文の説明を表示しています。