01 / GET STARTED
One home. Your own project.
Give your coding agent a framework to work with. It helps you choose components, prepare configuration and inspect a deployment plan for your Home Assistant setup.
Open the framework with your agent.
Clone the catalog with its component tags and use the documented revision. This is the shared framework; your home project will live in a separate folder.
git clone https://github.com/zerostorypoints/domosenso.git
cd domosenso
git checkout 817f8de4eebce9563b385294376e6b751c01ef9f
uv sync
claudeIn Claude Code, run /onboard-home. In Codex, start codex instead and ask it to use the onboard-home skill. You can begin with this prompt:
PASTE INTO YOUR CODING AGENT
Use the onboard-home skill to help me configure my Home Assistant setup. Ask about my host, devices and goals. Create a separate home project and start with backups. Stop at the deployment plan so I can review it before any live changes.
The conversation happens in your agent. There is no AI chat or connection to your installation on this website.
Work from the devices you have.
The skill asks about your host and priorities. With the access you provide, it reads your Home Assistant devices and discovered integrations, then compares them with the catalog’s requirements.
You get a proposal: components that fit, hardware that is missing and setup steps you need to complete. You choose which components belong in your project.
Create your Home Assistant token yourself and store it in a file outside every repository, with restrictive file permissions. Give the agent the file path; never paste the token into a chat or issue.
Start with a backup plan.
The agent creates a separate home repository and starts with the backup component. It helps fill in the inputs, render configuration and prepare a deployment plan. Keep your home repository private.
domosenso add [email protected]
domosenso render
domosenso status
domosenso deploy production --planThese commands illustrate the steps the agent takes. They are shorthand for uv run --project <catalog checkout> domosenso …, run from your home folder after initialization and input configuration.
You decide when the plan becomes a change.
Onboarding stops at the deployment plan. Review file changes, integration requirements and the restart before authorizing any live writes. When you proceed, take a baseline snapshot and verify the result; check again after the first scheduled backup.
Your configuration stays in your project. Shared components have pinned versions; your local extensions remain yours to maintain.
Read the full guide