Menu
Capture durable repository-specific context into Membase.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Pre-release drill for the Membase plugin — package every artifact locally, install each client (claude, codex, cursor, openclaw, hermes) through its real channel, verify auth, then prove skills AND hooks actually work end-to-end. Use before tagging a release, e.g. "/release-drill" or "/release-drill codex" for one client.
Connect an AI client (claude, cursor, codex, hermes, openclaw) to Membase from this repo — first-time local install, config wiring, and a verification smoke test. Use when the user asks to install, set up, connect, or test a Membase connector locally, e.g. "/membase-connect claude" or "cursor 연동해줘".
Flush pending local captures to Membase cloud, then sweep and consolidate fragmented or duplicated memories — without deleting originals without confirmation.
Store a session-state summary in Membase, tagged so a future session (this client or another) can recall exactly where things were left off.
Correct, avoid, or delete unsafe or stale Membase context.
Use Membase memory and wiki when prior user/project context may improve the answer.
| name | membase-project-context |
| description | Capture durable repository-specific context into Membase. |
When entering or summarizing a repo, inspect stable project files such as README, AGENTS/CLAUDE instructions, package manifests, test/build commands, and deployment docs.
Store concise durable context:
Do not store raw source files, secrets, .env values, or long logs.
