Customization

Keep installed skills unchanged. Use TOML overrides for persona, menus, templates, activation steps, and review lenses. Ask e11-customize to create or audit the override you need.

Skill override layers

Order	File	Owner
1	<skill-directory>/customize.toml	Toolkit defaults. Generated in your editor directory.
2	.foundry/custom/<skill>.toml	Team settings. Commit this file.
3	.foundry/custom/<skill>.user.toml	Personal settings. Keep this file ignored.

Later scalars replace earlier values. Plain arrays append. Tables with an id or code replace matching entries and append new entries. Overrides do not delete entries. Use a supported empty value or false field to disable behavior.

Add a team instruction

Save this example as .foundry/custom/e11-agent-dev.toml.

[agent]
persistent_facts = ["Use the project test commands before presenting a delivery."]

node .foundry/scripts/resolve-customization.mjs --skill .claude/skills/e11-agent-dev --key agent

Review the merged result before committing. Edit only fields present in the shipped customization surface.

Central configuration

Central settings resolve in this order: .foundry/config.toml, .foundry/config.user.toml, .foundry/custom/config.toml, then .foundry/custom/config.user.toml. Init generates the first two. Put team changes in the third and personal changes in the fourth.

node .foundry/scripts/resolve-config.mjs --project-root . --key core --key modules.foundry

Central settings hold language, project paths, and the agent roster. For a project outside the E11 platform, set e11_platform = false under [modules.foundry] in your team override. Individual platform gates also have per-skill settings.

Add a review lens

Review ships seven lenses in e11-review/customize.toml. Add a [[workflow.lenses]] entry with its id, applicable artifact type, condition, and method file. Reuse an existing id to replace a lens. Inspect the shipped surface for supported path and ordering fields.

Review lens settings