Extensions

An extension adds skills, subagents and knowledge for a specialty. Like the workspace, it has no installer. To add one, copy its top-level folders (.claude/, .agents/, .codex/, .gemini/, .familiar/) into the project root, and merge them with the folders that are already there. An extension never overwrites core files. Start a new session, and its skills appear.

This release includes no extensions. To write your own, start from familiar-template (“Use this template”). It follows .familiar/core/extension-contract.md. Each extension’s own _about.md says what it adds.

Adding several at once

For example, you want the fleet hub, the hooks package and two extensions of your own:

1. The hub does not go into a project. Unzip it as its own folder beside your projects. Its INSTALL-HUB.md covers the rest.

2. The hooks: copy the .familiar/ folder from the hooks zip onto the project. Then run /ili-system-settings hooks and turn on the hooks you want. Copying alone turns nothing on.

3. Each extension: copy its top-level folders onto the project root, one after the other. The order does not matter.

4. Start a new session.

   → verify: /ili lists each extension’s skills, and /ili-system-settings hooks shows the hooks as installed.