Aurelia migration

Skill Expert-Vision-Software/aurelia-expert/skills/aurelia-migration

Aurelia v2 MVVM SPA expertise skill package — 5 router-routed skills (foundation, runtime, largespa, migration) for AI coding agents.

Install

npx -y skills add Expert-Vision-Software/aurelia-expert --skill aurelia-migration

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when lifting Aurelia v1 code to v2, debugging v2 errors, or citing canonical Aurelia docs. Use when migrating from Aurelia 1, replacing PLATFORM.moduleName, switching configureRouter to @route, swapping .delegate for .trigger, fixing AUR0xxx error codes, optimizing performance with .to-view / batch(), or producing DeepWiki deep-links. Leading word — lift.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.6 KB, as published. Nobody here has run it

Aurelia Migration & Reference

Lift v1 code to v2 — the migration is the focal work, but this skill also serves as the post-migration reference for debugging, performance, and ground-truth citations.

When you lift v1 → v2, you replace removed APIs in place, never rewrite-then-drop-in. The three sub-areas the skill unlocks after the lift:

Concern	Reach for	Anchor
Removed/renamed v1 API → v2 replacement	reference/v1-removals.md	The lift table
AUR0xxx error code or behavior bug	reference/debugging.md	"How Do I…"
Slow list, re-render churn, batch DOM	reference/performance.md	`.to-view` mandate
Citing canonical doc / DeepWiki URL	reference/deepwiki-protocol.md	Link format

The lift step

A v1 → v2 lift is mechanical: eight APIs changed. Run the table in reference/v1-removals.md once per file. The most common lift mistake is .delegate on a custom event — it throws AUR0713 at compile time. See that file for the full table + one-line fix per row.

v1 contamination guardrail

When lifting legacy code, the FORBIDDEN patterns in reference/v1-removals.md throw runtime errors or silently break in v2. Never carry these patterns forward. Prefer rewriting over @aurelia/compat-v1 — the shim is for incremental legacy increments, not a destination.

Project precedence (overrides anything here)

When migrating in a project whose instructions file declares these rules, they are authoritative and override any generic Aurelia advice elsewhere in the skill package:

.trigger only for custom events, never .delegate (throws AUR0713 at compile time).
kebab-case element names only — every old PascalCase or camelCase element name from v1 is invalid in v2; rename at the lift step.
import type / export type for interfaces — split runtime (DI tokens, classes) from type-only; v1 files commonly merged them.
.style property binding is v2-only; v1 inline style="...${value}%" produces a 0-value prod-build bug that the dev build hides.

What this skill defers

Authoring new Aurelia 2 code from scratch (conventions, feature-first layout, DI patterns, Model/DTO flow) → aurelia-authoring skill in this package.
Vite 8 / Babel decorator pipeline → aurelia-tooling skill.
Testing setup → aurelia-ecosystem skill (see its reference/testing.md).

"How Do I…" routing

If the question is "what was that v1 thing called in v2?" — start at reference/v1-removals.md. If the question is "why does my prod build do X but dev doesn't?" — start at reference/debugging.md. If the question is "my list lags on scroll" — start at reference/performance.md. If the question is "what's the canonical URL for this claim?" — start at reference/deepwiki-protocol.md.