Skip to content
- All project should have access to the
homeassistant-repl@rhizomatics skill and the ha-repl tool
- Major projects will have their own
ha-repl plugin
- An up-to-date long lived access token will be maintained at user level for
ha-repl access
- Real-world beta test environments (home Home Assistant install, boat SignalK server) are described
privately in
hq-private/reference/test_environments.md.
- Local secrets for diagnostics and agent accounts live in
~/Projects/.hq.env/<service>.env, outside
every repo; never copy them into a checkout. Load at run time, never print.
- Agents use dedicated, least-privilege accounts on local services (OpenObserve, SignalK, Home Assistant,
routers), not the maintainer’s logins.
- Browser automation: Claude in Chrome (MCP extension) for UI checks against real instances, using a
Chrome profile logged in with agent accounts only; headless Playwright for preview environments,
docs sites and screenshots.
- What exists, hosts, accounts and sandbox needs:
hq-private/reference/diagnostics.md. Project:
projects/agent-diagnostics.md.
- All production projects
- Share the same set of admin workflows from the
.github project
- Have a
ci build that’s triggered on push to main or PR
- Have package publish workflows that require a clean (tests, lints, cyber checks) build, unless manually forced
archify used to generate architectural diagramshome-assistant-best-practices- rhizomatics/agent-plugins marketplace
- homeassistant-repl@rhizomatics
- New skill based on
hq defined standards and practices
