dress
Use when adopting loom on a repo, or re-tuning an existing loom configuration.
- License 许可
- MIT
- 所属仓库
- ZPerrin/loom
- 最近更新
- 2026-09-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- dress
- description
- Use when adopting loom on a repo, or re-tuning an existing loom configuration.
03 SKILL.md 正文
Dress
Install or retune loom for a repo. dress decides the repo-local control surfaces: .loom/loom.toml, optional .loom/skills/<skill>.md overrides, managed docs, and .loom/scripts/ hooks. The plugin supplies the runtime (doc-scan, doc-slicer, doc-linter, doc-stamp, skill-hook); dress configures what that runtime sees.
dress handles three repo states:
- Blank/new: little structure exists; propose the smallest useful loom surface.
- Undressed existing: code/docs exist but
.loom/loom.tomldoes not; map existing material before seeding anything. - Dressed:
.loom/loom.tomlexists; read current config and overrides, then propose retuning instead of reinstalling.
Dress Control Surfaces
These are the surfaces dress reads or writes directly; the full key map is the reference project, which Propose loads whole.
| Surface | Dress uses it for |
|---|---|
.loom/loom.toml |
read existing config; propose or write the repo control plane |
.loom/skills/<skill>.md |
read existing repo opinion; propose only when a skill needs repo-specific guidance |
.loom/scripts/* |
detect or scaffold approved deterministic hook scripts |
| managed Markdown/frontmatter | adopt, seed, move, exclude, or stamp docs in the managed set |
Workflow Graph
flowchart TD
survey["Survey - explore the repo, write nothing"] --> propose["Propose - reconcile to the minimum surface"]
propose --> confirm{"Confirm - approval boundary"}
confirm -->|revise| propose
confirm -->|approved| write["Write - materialize the approved set"]
write --> check["Self-check - run checks, report drift"]
check -->|"needs an unconfirmed edit"| propose
Workflow
The gate first: a loom gate: dress receipt in your context says whether the repo opinion was read and which hook ran, with that opinion and that hook's output beneath it. Without one for this invocation, do the same by hand: read .loom/skills/dress.md if it exists and run bash "${CLAUDE_PLUGIN_ROOT}/scripts/skill-hook" dress; exit 3 is no hook. A receipt from an earlier invocation does not count, and a hook tolerates a repeat.
1. Survey - explore the repo, write nothing
Determine whether this repo is blank, undressed, or already dressed, then gather only the facts needed to propose the surface.
- Check
.loom/: whether.loom/loom.tomlexists, which.loom/skills/<skill>.mdoverrides exist, and whether hook scripts already exist under.loom/scripts/. - Run
bash "${CLAUDE_PLUGIN_ROOT}/scripts/doc-scan"to see what loom currently sees: the managed docs and the frontmatter-less candidates. - Run
bash "${CLAUDE_PLUGIN_ROOT}/scripts/doc-slicer"to see the current startup slice. - Inspect only enough repo shape to explain the proposal: modules, build/test signals, existing docs worth mapping, and obvious gaps.
2. Propose - reconcile to the minimum surface
Review the reference project as calibration for the minimum loom surface, then turn the survey into an adoption diff: current state -> needed loom surface -> proposed changes. Still write nothing.
cat "${CLAUDE_PLUGIN_ROOT}/references/reference-project.md"
- Control plane. Always propose
.loom/loom.toml; say whether it is new or a retune, and whether an existing one is valid. - Managed set. For existing Markdown, say adopt, leave unmanaged, exclude, move, or seed.
AGENTS.mdis the default agent-facingreadme; seed only durable content, and seedCLAUDE.mdas the one-line@AGENTS.mdimport, excluded from discovery, since Claude Code reads only the former. - Startup slice. Propose
context.slice_headersandcontext.inject_fieldsfrom headings that exist or docs you propose to create. - Overrides. Propose
.loom/skills/<skill>.mdonly for repo opinion that changes a skill's DEFAULT behavior. - Hooks/scripts. Propose scripts only for deterministic behavior.
- Gaps. Name what loom needs but the repo does not yet know. Do not fill unknowns with invented prose.
3. Confirm - approval boundary
Do not write until the operator approves the exact adoption diff. If the operator changes scope, revise the proposal first. Approval covers the docs, config, overrides, scripts, moves, excludes, and staged files for this pass.
4. Write - materialize the approved set
Write one coherent pass from the approved diff.
- Always write or update
.loom/loom.toml. - Adopt, move, seed, or exclude only the approved docs.
- Preserve operator voice when mapping existing prose.
- Stamp managed docs with
bash "${CLAUDE_PLUGIN_ROOT}/scripts/doc-stamp" <file> kind=... status=... updated=<today>. - Stage only approved files changed by dress.
5. Self-check - run checks, report drift
Run bash "${CLAUDE_PLUGIN_ROOT}/scripts/doc-linter". Fix findings caused by the approved dress work. Report unrelated drift separately. If the fix requires an unapproved change, return to Propose.
Output
Report what changed, what was staged, what gaps remain, and the self-check result.
04 同仓库更多 Skills
weft
Use when a loom-managed documentation set needs an editorial pass to prune, condense, reroute, and realign durable project docs with the code and the editorial ethos.
weave
Use when wrapping up a loom work session, especially when durable docs, close-out checks, merge handoff, or branch cleanup need attention.
warp
Use when opening a unit of work in a loom managed repo, especially when orientation, branch/worktree setup, ticket context, or kickoff guidance may be needed.
spec
Use when the user asks to spec a capability, write its requirements, or capture what the code does before changing it. Produces a repo spec of what the code does or a work spec of what one unit of work will make true, under the loom spec grammar.
refine-spec
Use when the user asks whether a spec is still accurate, suspects spec drift, wants a capability's behavior captured before or after a change, or names code that has no spec. Reconciles one capability's loom spec against its tests and code and reports drift by requirement id.