prolog-migrate-projectlisted

# Legacy Prolog Project Migration Skill Use this skill whenever migrating an existing or legacy Prolog project (e.g. built with early prompts, ad-hoc scripts, or vendor-specific AGY/Gemini/Claude configs) over to the **Prolog Agent Toolkit** standards and conventions. --- ## Phase 1: Safe Git Isolation (Branch & Worktree First) > [!IMPORTANT] > **Safety First**: NEVER perform structural refactoring or delete legacy files directly in your primary working directory or on the `main`/`master` branch without a clean backup. Before editing code or deleting files: 1. **Check Git Status**: ```bash git status ``` 2. **Create a Dedicated Git Worktree & Branch** (Recommended): If using Git, isolate the migration work in a separate worktree so your existing working codebase remains untouched until verification is complete: ```bash # Create a new branch 'migrate/prolog-agent-toolkit' in a parallel worktree directory git worktree add -b migrate/prolog-agent-toolkit ../<project-name>-migrate main cd ../<project-name>-migrate ``` 3. **Alternative Feature Branch** (If worktrees are unavailable): ```bash git checkout -b migrate/prolog-agent-toolkit ``` --- ## Phase 2: Purging Subsumed Vendor & Harness Configurations The toolkit enforces **100% vendor neutrality** (see [AGENTS.md](../../AGENTS.md)). Ad-hoc prompt scripts, IDE-specific configs, and harness-specific settings are fully subsumed by the open-standard `.agents/` architecture. Identify and