ワンクリックで
rhizome-readme
Principles for structuring the Rhizome README
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Principles for structuring the Rhizome README
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | rhizome-readme |
| description | Principles for structuring the Rhizome README |
The first principle is that onboarding is as easy and simple as possible, and as unintrusive as possible. When a user has Docker, this should be thusly the best fit.
All ports should be configurable at all times, to avoid annoyance on developers side.
Next, working alternatingly - not at the same time, but deciding on a case by case basis depending on the task at hand - between working inside or outside of a container, should be seemlessly possible.
Tests with Playwright (can be headless) from the host system, and controlling another CMUX surface.
Assume
Make sure
make clean)docker/token existsSteps
make box.make test should workmake e2e should workmake startnpm imake test should workmake e2e should workmake startmake stopmake yoloclaude (bypass permissions mode is ok inside the container)/status)/mcp should list playwright as connectedmake clean on hostmake box WITH_VEC=1make onboardmake startmake backfill-embeddings