shapelang

This skill should be used only when explicitly asked to create or refresh a whole-repository authored Shape model from a fixed repository baseline. Survey architecture-significant subsystems, treat generated AST as read-only navigation, verify claims in source, and author validated model batches. Do not use it for incremental edits, pending-change review, or preflight planning.

This skill should be used before editing code to map a concrete planned change onto an existing Shape model, identify constraints, obligations, source anchors, coverage, and bindings, and optionally simulate a conservative temporary contract change. Do not use it for post-change review, whole-repository modeling, or source-to-model drift.

This skill should be used to review a concrete code diff for real reachable bugs, combining complete local review with focused authored-Shape investigation. Do not use it for pure model drift, authored contract-diff risk, style preferences, or speculative architecture concerns.

This skill should be used to compare a base and candidate authored Shape contract for semantic loosening that may remain checker-valid. Review `.shape` and vendored-pack changes only. Do not use it for application-code bugs, source-to-model drift, or whole-repository modeling.

This skill should be used for incremental Shape language work: authoring or repairing `.shape` files, explaining syntax or diagnostics, formatting, validation, teaching, source-to-model drift review, and CLI/editor operation. Do not use it for whole-repository modeling (`shape-index`), pre-implementation planning (`shape-contract-preflight`), authored contract-diff risk (`shape-contract-guard`), or code-change bug review (`shape-review`).