Packs

A pack is how a team shares what its agents should know and how they should work. Memory, workflows and agent definitions are one concept: a pack is a folder in the open Agent Skills format (a SKILL.md, plus any reference files) with a pack.json that describes it.

Kinds

Kind	What it is	Example
knowledge	Reference material for agents: conventions, how a system works, lessons learned	ue5-cpp-conventions, your project’s style notes
workflow	A repeatable process, which may bundle its own subagent definitions	critic-loop, make-asset
agent	A Claude Code subagent file with Weld settings, runnable in a session or in the background	merge-resolver, commit-summarizer

pack.json records the name, kind, version, description, author, agent and session provenance, and a trust label. Knowledge packs are given to agents as reference material, not as instructions.

Three tiers

• Personal, in ~/.claude/: yours alone, never synced.
• Project, in the game repo under .claude/skills/ and .claude/agents/: git syncs, versions and reviews them, and Claude Code loads them natively. There’s no separate registry and nothing to reload.
• Weld built-ins, in the Weld Claude Code plugin: weld-coordination, make-asset, critic-loop, weld-build and weld-doctor.

Publishing is just a merge

An agent (or a person) that learns something worth keeping writes or updates a pack in the repo, and it goes through the merge queue like any other change. After it merges, every session on the team has it.

Projects made with weld game new start with a few packs: project knowledge, Unreal C++ conventions, a game-debug pack describing the game’s weld.* console commands and headless smoke tests, and a critic rubric for the chosen art style (.claude/skills/rubric-<style>/).

What Weld adds to git

• Provenance and usage: who or which agent session wrote a pack, and how often it’s used.
• A cross-project library on the hub: publish a pack once, then copy it into another game.
• Validation of pack.json, SKILL.md, agent files and links.

weld pack list                       # packs in this repo, plus the hub library
weld pack validate .claude/skills/rubric-art
weld pack publish .claude/skills/rubric-art
weld pack add rubric-art             # copy a library pack into this repo's .claude/

Agent packs

An agent definition is a Claude Code subagent file in .claude/agents/ with extra Weld frontmatter: its trigger (an event, a schedule or manual), inputs and tool permissions, model and budget cap, which node role runs it, and what it produces. One file serves both Claude sessions and Weld’s background runner.

Repo agents are code that runs on your machine, so they need your approval first:

weld agents list                     # built-in agents and the repo's .claude/agents/*.md
weld agents validate .claude/agents/level-reviewer.md
weld agents approve level-reviewer   # pins the file's sha256; any change needs approval again
weld agents run level-reviewer --prompt "Review the arena layout" --dry-run

Background agents run with claude -p under the node owner’s account, for the owner’s own work only, with per-run budget and time limits.