
from galyarder-framework12
Compatibility skill that maps legacy `e2e-runner` calls to current runtime capabilities, routing requests to modern plugins or agents.
This compatibility skill restores the historical e2e-runner capability so older prompts, docs, and integrations still resolve correctly. It does not implement new execution logic itself; instead it routes legacy invocations to the appropriate current runtime agent, plugin, or narrower modern skill. Typical uses include migrating old automation flows, preserving backward compatibility for integrations, and providing a stable name for orchestrations that reference e2e-runner.
Use this skill when a prompt, template, or integration explicitly references e2e-runner and the runtime has since renamed or refactored that capability. It is primarily a routing/compatibility layer: prefer the modern, specialized skill for new work, and use this only to resolve legacy references or during migration.
The skill is framework-agnostic but references common agent runtimes and integrations (Claude Code, Codex/Copilot-style skills, Cursor, Gemini). It functions as a pointer to the modern runtime implementation rather than as a standalone executor.
Compatibility stub that routes legacy e2e-runner calls to modern runtime equivalents. The SKILL.md is 90% unrelated framework protocol manifesto and 10% actual skill content — just 3 sentences saying 'route to the current capability.' No scripts, no concrete routing logic, no examples. Essentially a signpost with no directions.
The bulk of the SKILL.md is a framework governance manifesto (TDD mandates, operational modes, security hygiene rules) that has nothing to do with e2e-runner compatibility. The actual skill content is just 3 sentences at the bottom. This looks like a framework that injects its global rules into every skill file, inflating size and diluting relevance.
Playwright Test Reviewer
Automated Playwright test auditor: finds anti-patterns, scores files, and generates concrete fixes and patch suggestions to improve stability and coverage.
Verification Before Completion
Require and verify concrete evidence (command outputs, test results, build exit codes) before claiming work is complete or creating PRs.
Requesting Code Review
Dispatch a focused code-review subagent and follow a strict review contract to catch critical issues before merging or continuing development.
Remotion Engineer (compatibility)
Compatibility/adapter skill that maps legacy `remotion-engineer` capability names to the modern runtime and enforces the framework’s operational protocols.
Requesting Code Review
Dispatches a focused code-review subagent and provides a template-driven process to request reviews before merges, feature completion, or risky changes.
Remotion Engineer (compatibility)
Compatibility skill that maps legacy `remotion-engineer` references to current runtime practices and enforces the framework's operational protocols for agentic
Galyarder Release Coordination
Coordinated release workflow for the Galyarder Framework: verification gates, canary validation, smoke tests, stable promotion, changelog drafting, and follow-u