legacy-bridge

Translate legacy @load patterns into Load: skills/* format with deprecation warnings.

17|1|Updated Jun 8, 2025
One-click install
npx skills add https://github.com/williamzujkowski/standards --skill legacy-bridge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legacy-bridge
Source: https://github.com/williamzujkowski/standards/tree/main/skills/legacy-bridge
Command: npx skills add https://github.com/williamzujkowski/standards --skill legacy-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill provides a crucial backward compatibility layer, allowing existing systems using @load patterns to seamlessly transition to the new Skills-based architecture without immediate breaking changes. It automates the translation process, saving significant refactoring time and reducing migration risks.

Core Features & Use Cases

  • Automated Pattern Translation: Converts old @load product:* and @load CS:* patterns into the new Load: skills/* format.
  • Wildcard Expansion: Automatically expands generic patterns (e.g., SEC:*) into specific skill sets.
  • Zero-Downtime Migration: Enables a gradual, controlled migration over a 6-month transition period, ensuring continuous operation.
  • Use Case: You have a large codebase with many @load product:api directives. Use this skill to automatically translate these into the equivalent Load: [coding-standards, testing, security, devops] skill calls, preparing your system for the new architecture.

Quick Start

Translate the legacy pattern '@load product:api + CS:python' to the new skills format.

Frequently Asked Questions about legacy-bridge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate legacy @load patterns to the new Skills format?

Legacy-bridge automatically translates old @load product:* and @load CS:* patterns into the new Load: skills/* format. The Skill expands generic patterns and maps them to corresponding skill paths, enabling your codebase to transition without rewriting directives manually.

Can I use legacy @load directives during a migration period without breaking changes?

Yes. Legacy-bridge provides zero-downtime migration by translating legacy patterns while emitting deprecation warnings. You can run both old and new formats simultaneously over a six-month transition period, ensuring continuous operation across CI/CD and production.

What legacy patterns does the Skill support translating?

Legacy-bridge translates @load product:* patterns (e.g., product:api, product:security) and @load CS:* patterns (e.g., CS:python) into equivalent skill loads. Wildcard expansion automatically converts generic patterns into specific skill sets matching the new architecture.

Does legacy-bridge work with my existing CI/CD and production environments?

Yes. Legacy-bridge is designed for compatibility across CI/CD and production environments. It integrates with legacy-mappings.yaml and maintains mapping fidelity to skills/* paths, ensuring pattern translation works throughout your deployment pipeline.

How does legacy-bridge handle backward compatibility during system refactoring?

The Skill preserves zero breaking changes by translating legacy patterns without removing old directives immediately. Deprecation notices inform teams of pending changes while the system accepts both formats, reducing refactoring risk across large codebases.

What's the best way to automate the conversion of legacy @load directives at scale?

Legacy-bridge automates pattern translation accuracy across your entire codebase, mapping old directives to new skill paths automatically. This eliminates manual refactoring work and reduces migration time, especially for large systems with many @load statements.