القائمة
Use the local deterministic infra layer in `tools/infra/` when setting up or extending harness, testbed, or local server environment workflows. Read the infra README first, then wire the setup into `Makefile` where appropriate.
| name | infra-use |
| description | Use the local deterministic infra layer in `tools/infra/` when setting up or extending harness, testbed, or local server environment workflows. Read the infra README first, then wire the setup into `Makefile` where appropriate. |
Use this skill when the task involves local infrastructure setup, harness environments, deterministic testbeds, or server-side runtime helpers.
This skill is specifically for the TeamClaw repo-local infra layer:
tools/infra/Before making infra or harness changes:
tools/infra/tools/infra/README.mdDo not invent a parallel setup path outside the repo if the infra layer should own it.
Use this skill for requests like:
tools/infra/README.md.tools/infra/.tools/infra/Makefilemake bootstrapmake runmake resetFor harness or testbed setup:
make bootstrapmake run depend on the required bootstrap stateThe target shape should stay simple for operators:
make bootstrap
make run
make reset
tools/infra/README.md remains aligned with the actual setup pathMakefile stays the main operator entrypoint for local environment setupMakefiletools/infra/README.mdbootstrap, run, or reset are enoughTechnical guide for creating a new TeamClaw agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new local coding agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Use a file-only git working branch for agent changes. Start from the current main branch contents without carrying prior branch history, create a fresh branch named from the agent or a uuid, then make the code update there.
Hire an Engineer in TeamClaw. Use this when an Architect or Manager needs to add implementation capacity, choose the right engineer role fit, check headcount, and then execute the hire through the standard TeamClaw agent creation flow.
Use the local agent workspace memory model. Store durable hot memory in the agent `memory/` folder, use `notes/` for daily records and task-local notes, and keep both folders updated as work progresses.
Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.
Generate the stable TeamClaw release changelog at releases/v{version}.md by reading commits, changesets, and merged PR context since the last stable tag.