harbor-spec

Use before running risky commands, deleting or moving files, modifying secrets, changing migrations, installing dependencies, modifying CI/CD, changing production configuration, modifying .harbor/*.yaml, writing generated skills, or any operation with runtime safety risk under Harbor-spec.

Use when reviewing code, diffs, PRs, implementation correctness, semantic drift, missing tests, runtime safety risks, generated context drift, or contract consistency under Harbor-spec.

Use when refreshing Harbor generated context under .harbor/views/**, including project structure, L2 README, Module Capsule, stale checks, doctor checks, or finish --sync-context after code, contract, schema, CLI, JSON, test, DDT, or module boundary changes.

Use when adding or modifying APIs, schemas, public functions, parser/export/writeback behavior, workflow nodes, CLI behavior, JSON output, file write behavior, or any change with possible Contract Impact under Harbor-spec.

Use when updating tests, DDT bindings, l3_version, contract versions, Diary Drafts, changelogs, release notes, or important architectural decisions under Harbor-spec.

Use when inspecting Harbor workspace layout, planning workspace cleanup, validating .harbor/ canonical workspace health, reviewing managed files, running workspace inspect, or previewing read-only workspace migration plans with migrate --dry-run.

Use when debugging, reviewing, or refactoring the harbor/core module. It routes the agent to the module capsule instead of loading the whole repository.