homenet
homenet — home network administration
| Field | Value |
|---|---|
| Version | 0.1.0 |
| Requires template | >=2.6.0 |
| Tools | claude-code |
| Licence | MIT |
| Contains code | yes |
Contents
Section titled “Contents”Rules, roles and skills for running a home network or homelab from a project on the template: LAN and WLAN, router
and network controller, hypervisor, Raspberry Pi and other servers, DNS filter, devices, firewall and Home Assistant.
The package carries no network data (no addresses, host names or credentials); the setup records them in the project
under docs/project/homenet/. It builds on R-safe-approval and .act/rules/topics/live-systems.md and repeats
neither.
- Rules:
R-homenet-access(a rights table per system and way; a dated entry there is the standing approval for a named action class),R-homenet-never(the hard core no standing approval covers),R-homenet-ssh,R-homenet-rename,R-homenet-names,R-homenet-exports,R-homenet-handoff; an extension ofR-safe-approvalthat points to the rights table. - Roles:
homenet-reader(reads only, never scans, cross-checks every write over its own way) andhomenet-writer(backs up first, never deletes, a write is done only after the reader’s cross-check). - Skills:
homenet-inventory(first inventory and doc audit against the live state) andhomenet-add-device. - Topic:
homenet-mcp(MCP servers and APIs for Home Assistant, network controller, hypervisor, monitoring and NAS, with read and write kept apart). - Code:
install.pyonly reports which tools are there (ssh, Python, interpreter traps on Windows); it opens no connection and writes nothing. The check modulehomenet_no_scanrefuses port scanners (nmap,masscan,zmapand similar,nc -zover more than one port) in shell calls of Claude Code.
Settings
Section titled “Settings”The install asks these questions once; the answers are kept in docs/ai/config.md.
homenet-home-assistant: Is Home Assistant part of this network (yes or no)?
In this package
Section titled “In this package”Names as the package folders carry them. pre-template loads before the template’s own files: a skill, role or topic with a template name replaces the template’s. Rules and coding sets are only extended: a template rule id or coding set name in pre-template is refused. post-template loads after the template’s files and extends a unit of the same name.
R-homenet-access(post-template)R-homenet-exports(post-template)R-homenet-handoff(post-template)R-homenet-names(post-template)R-homenet-never(post-template)R-homenet-rename(post-template)R-homenet-ssh(post-template)R-safe-approval(post-template)
Skills
Section titled “Skills”homenet-add-device(post-template)homenet-inventory(post-template)
homenet-reader(post-template)homenet-writer(post-template)
Checks
Section titled “Checks”homenet_no_scan(post-template)
Topics
Section titled “Topics”homenet-mcp(post-template)
install.md: yesinstall.py: yes
Install
Section titled “Install”In a project on the template:
python .act/scripts/packages.py fetch homenetthen, in the assistant:
/act-packages add homenet