Scenario 6: Add plugin constraints to a layer
Use this when your environment depends on Claude plugins and you want the layer to describe not just files, but also expected plugin versions.
Frequency: Rare · Status: Shipped
Use this when your environment depends on Claude plugins and you want the layer to describe not just files, but also expected plugin versions.
Typical commands:
harnesstap layer edit my-setup --add formatter@team-marketplace --type plugin_pin --version "^2.1.0"
harnesstap layer edit my-setup --remove formatter@team-marketplace --type plugin_pin
harnesstap layer show my-setupThis is especially useful for team-wide setups where the harness environment should stay compatible across machines. See Scenario 16 for enforcing the constraints in CI.
Scenario 5: Build a reusable layer from imported resources
Use this when you want to turn a working repository setup into a named, reusable harness baseline.
Scenario 7: Preview and apply a layer to one or more target harnesses
Use this when you are ready to materialize a known-good setup into a project. The dry-run preview is itself a frequent check before a real write.