wf-docker-update-skill-method

To prevent skill drift, you run a single canonical workflow that propagates updates and performs cross-surface integrity checks across Codex, Cline, and Antigravity. This ensures all surfaces remain synchronized and aligned during updates.

The best way to synchronize Delphi skills is to initiate a single canonical update process that propagates changes across Codex, Cline, and Antigravity. This workflow enforces logging in canonical files and validates coherence across surfaces.

You validate cross-surface changes by running the canonical workflow which applies validation gates and integrity checks across the workspace. This verifies that updates are logged correctly and coherence is maintained across all affected surfaces.

Yes, you need a single canonical workflow to update rules across multiple surfaces because it enforces necessary mirrors and validation gates. This prevents drift and ensures governance alignment when changes touch multiple platforms.

Updating a skill manually causes drift because changes are not automatically logged in canonical skill files or validated through the workspace. Without a synchronized canonical workflow, surfaces like Codex, Cline, and Antigravity lose consistency.