<EXTREMELY-IMPORTANT> This skill mutates durable project memory across multiple workspace members. Non-negotiable rules: 1. Discover the real workspace shape before writing any member `CLAUDE.md`. 2. Document the actual exported or reachable surface, not raw visibility markers alone. 3. Keep each member file self-contained enough for Claude's lazy-loading model. 4. Preserve root-level project rules and locked architectural decisions unless discovery proves them stale. 5. Do not run this skill proactively; it is explicit-user-only maintenance. </EXTREMELY-IMPORTANT>

• whether the repo is a Cargo workspace or a package monorepo
• whether the user wants a full refresh or a scoped member refresh
• which members exist and which already have

  CLAUDE.md

  files
• which root-level memory files and architectural rules already exist and should be preserved

• workspace detection order
• member inventory expectations
• discovery rules for exported surface, wiring, and dependency mapping

• the workspace shape cannot be identified
• the target member set is too ambiguous to update safely

references/workspace-discovery.md

• actual exported or reachable surface
• key source files
• wiring files such as crate roots, package entry points, manifests, barrels, startup hooks, registries, routers, or feature flags
• inter-member dependencies
• tests, benchmarks, or runtime entry points
• real consumer usage patterns when available

• do not equate raw

  pub

  or raw

  export

  counts with the real public surface
• verify what consumers can actually reach first
• prefer actual imports, re-exports, and runtime registration points over guesses
• preserve existing member docs when they are still correct; extend or tighten them instead of regenerating blindly

references/workspace-discovery.md

• purpose
• public or exported surface
• key files
• dependencies
• wiring and entry points
• usage pattern
• architecture notes
• testing guidance

• references/output-contract.md

  for required sections, size targets, and verification rules

• references/package-template.md

  for library or package members

• references/app-template.md

  for apps, binaries, or entrypoint-heavy members

• use real workspace examples, not placeholders
• keep tables and bullets preferred over repetitive prose
• make each member file self-contained for Claude's lazy-loading behavior
• document hidden wiring points if a future change would need them to make behavior reachable

CLAUDE.md

CLAUDE.md

• keep project-wide rules, locked decisions, testing policy, and workspace layout
• remove member-specific API tables or file listings from root
• ensure the root points clearly to member-local docs rather than duplicating them

• preserve root-level architectural constraints and steering decisions
• do not erase useful human-authored global rules
• move member detail down instead of letting the root become a second copy of every member file

references/output-contract.md

• every in-scope member has a

  CLAUDE.md

• member docs describe the real reachable surface, not just raw visibility markers
• wiring and entry points are documented where relevant
• root no longer duplicates member-local details heavily
• line budgets remain sane
• the refreshed docs would let an implementation agent work in a touched member without searching blindly

• improve coverage
• restore missing sections
• tighten duplicated content
• correct stale reachability or wiring claims

references/output-contract.md

• detected workspace shape
• members refreshed
• files created or updated
• coverage or inventory highlights
• budget status
• intentionally deferred or out-of-scope members

1. detected workspace shape and scope
2. members refreshed
3. files created or updated
4. coverage and self-containment summary
5. budget and verification result
6. deferred or intentionally skipped members