Install and initialise

Before you begin

Use macOS or Linux with Git, Node.js 24.15.0 or later, and npm. Windows does not support engine execution. Your account needs access to the Engineering11 package and a token with package read access. Configure and authenticate the AI runtime your project uses before starting paid work.

Install the CLI

Add these registry settings to your user npm configuration. Provide your package token through the NPM_TOKEN environment variable.

@engineering11:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=${NPM_TOKEN}

npm install -g @engineering11/e11-foundry@2.0.0
e11 --version

The version command prints 2.0.0. This guide uses e11 throughout. Doctor checks PATH because installed skills call e11 board.

Make the checkout ready

cd your-repository
e11 init

On a terminal, choose your project name, editor, and output folder. The default publication root is foundry. For unattended setup, supply the editor codes and accept the defaults.

e11 init --yes --ide claude-code,codex,opencode

Init reports the project file, workspace, Toolkit, configuration, price list, profiles, ignore rules, skills, registry, and preferences. wrote means a step changed files or records. kept means the existing result already matches. refused names a problem. skipped means a dependency or option prevented the step.

Run init again after cloning a repository or restoring editor skills. Matching inputs stay in place. Review the price list and inferred acceptance commands before committing.

Check your checkout

e11 doctor

Doctor writes no files. An ok row passes. A warn row needs review, such as a price difference. A fix row names a required correction. Follow each correction and run doctor again.

The walkthrough includes captured terminal output.

Commit what your team shares

git add .foundry/project.toml .foundry/pricing.json .foundry/profiles.toml .gitignore
git commit -m "chore: configure Foundry"

Commit your initiative documents under the publication root. Commit team overrides under .foundry/custom/ when you add them. Keep generated configuration, Toolkit files, scripts, editor skill directories, and local workspace pointers out of Git. Init manages the ignore rules.

Files a checkout carries explains each file and its owner.