ember-claude-skills

Scaffold a Glimmer component (template + backing class + integration test) following Octane conventions and Polaris-friendly patterns.

Scaffold an Ember route (route file + template + optional controller for query params) and an application test that visits the URL.

Scaffold an Ember service with TypeScript types, Registry augmentation, and a unit test.

Run the Ember test suite (QUnit), triage any failures, and (when asked) author additional tests for missing coverage.

Specialist agent for migrating Ember 2.x apps to 3.28 LTS — and from there onward through the LTS chain to the latest. Drives the LTS-by-LTS sequence, runs ember-cli-update with codemods, manages the deprecation workflow, audits addons, and keeps the test suite green at every hop. Use when planning, scoping, or executing a 2.x → modern Ember migration.

Specialist agent for finishing Octane adoption within Ember 3.x and driving the 3.28 → 4.12 LTS jump. Operates in two phases — (1) finalize Octane on 3.28, (2) hop through the 4.x LTS chain. Hands off to ember-4-migrator at 4.12. Use when in any 3.x state, mid-Octane or otherwise, and the goal is to reach a clean 4.12 LTS.

Specialist agent for the Ember 4.12 → latest 5.x LTS jump and (optionally) Glint + .gjs/.gts adoption along the way. Operates in two phases — (1) finalize 4.x prerequisites (Embroider, official TS, addon hygiene), (2) hop the 5.x LTS chain. Hands off to the modern Ember skills (architect agent + Polaris migration) once on the latest 5.x LTS. Use when in any 4.x state and the goal is to reach the modern Ember destination.

Senior Ember architect. Use for designing new Ember features, choosing where state lives (component vs service vs route model vs Ember Data), picking addons from the ecosystem, planning Octane→Polaris migrations, or reviewing the structure of an Ember PR before code is written. Pulls heavily from the ember-octane-fundamentals, ember-services-and-state, ember-data, ember-ecosystem-addons, and ember-polaris-migration skills.

Test engineer specialized in Ember — designs and writes QUnit suites using @ember/test-helpers, ember-test-selectors, ember-cli-page-object, ember-cli-mirage, and ember-a11y-testing. Use when authoring or auditing tests, fixing flaky settled-state issues, reviewing test coverage on a PR, or scaffolding a Mirage scenario for a new feature.

The canonical Ember 2.x mental model — Ember.Object.extend, Ember.computed, classic components, the actions hash, mixins, observers, run loop, two-way binding. Use when reading or maintaining 2.x code, decoding deprecation messages, or explaining how a 2.x pattern maps to modern Ember.

Practical advice for teams that must stay on Ember 2.x for now — pinning, security hygiene, what to backport, what to leave alone, when to declare upgrade-impossible-without-rewrite. Use when triaging a frozen 2.x codebase, when justifying upgrade budget, or when scoping the smallest viable maintenance footprint.

The Ember 2.x test API — moduleFor, moduleForComponent, moduleForModel, moduleForAcceptance, the global async helpers (visit, click, fillIn), wait(), and the bridge to the modern setupTest/setupRenderingTest API introduced in 3.x. Use when reading or fixing 2.x tests, or when planning the conversion to the modern qunit-based API.

The 2.18 LTS → 3.28 LTS migration path — the LTS-by-LTS sequence, ember-cli-update, the deprecation workflow, jQuery removal, the test API conversion, and the addon survival list. Use when planning, scoping, or executing a 2.x upgrade. Hands off to the ember-3-migrator agent once you reach 3.28.

Reading and maintaining Ember 3.x apps where classic and Octane patterns coexist — half the components are Ember.Component.extend, the other half are @glimmer/component, and tests run on both APIs. Use when triaging "why does this file look different from that file," when reviewing a partial-migration PR, or when planning the order of further conversion.