メニュー
To develop the user interface of the application, you need to know how to start, stop, restart the app and where to find it.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Describes the current local development setup, for when we want to perform development tasks on the actual Rhizome app
How to talk to the deployed plurama apps (treina, …) from the shell with the plurama-cli command — a curl-like client that carries baked-in prod credentials. Use whenever a task means reading or writing live plurama app data over HTTP, when `plurama-cli` is missing or unauthorized, or when a new app must be added to it.
Tracker's HTTP API — authenticate as a machine user, read tasks/meets/journals/today-board, ingest mail messages, write through the recording-mode gate via curl
How to run, test and develop the natural-language Telegram bot that queries tracker. The bot is NOT in tracker — it lives in the plurama umbrella app (plurama/src/plurama/app/agent). Covers the agent architecture, the secrets/config it needs, the locked-box egress-proxy gotcha, seeding a testable conversation, and driving it from the host as if you were Telegram.
Rhizome's local REST API — search, read, and create contexts/items via curl
Sandbox a Docker container so only an explicit allowlist of outside hosts is reachable. Use when running an untrusted/AI agent container and you want a hard egress cutoff with optional inbound port forwarding.
| name | develop-tracker-ui |
| description | To develop the user interface of the application, you need to know how to start, stop, restart the app and where to find it. |
Start the application with make start. Stop it with make stop.
Doing so starts and stops both the frontend and the backend.
The app will state the port its running on at startup like this: "Starting server on port ".
Logs are under logs/tracker.log.
Check config.edn for actual configuration, when there is need.
Testing is done with make test and make e2e.
