← ClaudeAtlas

maios-project-host-adaptationlisted

Adapt the neutral MAIOS Project Kernel relation to the selected coder or harness without forking its meaning; use during integration, first host activation, a harness change, or when native instructions, skills, tools, state, or reentry conventions must be connected.
GrazianoGuiducci/maios-project-kernel · ★ 0 · AI & Automation · score 70
Install: claude install-skill GrazianoGuiducci/maios-project-kernel
# Adapt MAIOS Project Kernel To The Host Own the translation between the project-owned Kernel and the coder or harness that is present. The coder already knows how its own system works; use that knowledge together with the installed neutral sources instead of importing a second Kernel or treating one adapter table as a complete manual. When the same project must continue through another instance or harness, read [shared-project-continuity.md](references/shared-project-continuity.md). It supplies the method for forming the actual connection, preserving shared knowledge and situated identity, and evolving missing support when it becomes useful. Use `maios-project-coordination` when work or responsibility must return between instances. Merely knowing this possibility does not configure a host. ## Reconstruct The Host Relation Read `AGENTS.md`, `START_HERE.md`, `HOSTS.md`, the selected host projection and the neutral competence sources under `skills/`. Inspect local host help or current owner documentation only when a convention is absent, ambiguous or likely to have changed. Connect the smallest native form that preserves: ```text stable project instruction and Kernel entry -> discovery of pertinent competence knowledge -> current operator, project sources and living state -> host tools and capabilities actually available -> useful situated work and closest-owner learning -> fresh reentry through the changed project field. ``` Paths, invocation names, prompt files, skill