adapt-to-project

To adapt an installed skill pack, you guide post-install adaptation by substituting placeholders, merging companion files, and restructuring layouts to align with repository conventions. This resolves partial merges and ensures consistent project architecture.

Discovery-driven restructuring is a post-install adaptation process that analyzes repository and user scopes to consolidate layouts and reconcile companion files. It ensures installed packs integrate cleanly without leaving inconsistent structural artifacts behind.

Resolving placeholder markers and dirty-state issues requires consuming install markers and escalating dirty-state checks during post-install adaptation. This generates idempotent pending-state files to safely track and clean up incomplete work.

Yes, post-install adaptation handles both repository and user scopes through scope-aware file writes. It enforces safety checks that preserve per-scope path jails, ensuring modifications remain correctly isolated during companion-file reconciliation.

Layout consolidation is constrained by safety checks that preserve per-scope path jails, preventing writes outside authorized boundaries. It relies on marker consumption and dirty-state escalation, meaning unresolved pending states can block adaptation steps.

You need post-install adaptation for file merging when a session-start hook signals pending changes or when a newly installed pack leaves partial merges. It reconciles companion files and substitutes placeholders to match existing local conventions.