Scenario 11: Start from a catalog baseline instead of building from scratch
Use this when you want a fast starting point and only need to tailor it for your repo afterward.
Frequency: Common · Status: Shipped
Use this when you want a fast starting point and only need to tailor it for your repo afterward.
Typical commands:
harnesstap init --main codex --aliases claude-code,cursor
harnesstap layer list --search foundation --remote-only
harnesstap layer apply engineering-foundationThis is often the fastest path for a new repo: apply a public catalog baseline, then scan or extend it with project-specific resources later.
Bare names such as engineering-foundation resolve against the harnesstap-cloud
public catalog (and any connected orgs or libraries). Use layer pull when you
want the bundle cached locally before going offline.
Scenario 10: Export or import a layer as a portable bundle
Use this when you want to move a harness setup between machines, bootstrap a new repo quickly, or share a team baseline.
Scenario 12: Drive HarnessTap from scripts or other agents
Use this when another automation layer needs structured output instead of human text.