← ClaudeAtlas

wavemaker-conventionslisted

Conventions and rules for migrating legacy web apps (JSP/servlet, PHP, .NET, or any server-rendered app) to WaveMaker AI (React/low-code), AND for hand-authoring any WaveMaker project files outside WaveMaker Studio. Use this skill whenever the task involves migrating a legacy app to WaveMaker; creating or editing WaveMaker pages/partials by hand (`.html` wm-markup, `.variables.json`, `.js`, `.css`); writing WaveMaker LiveVariables, LiveForms, LiveTables, ServiceVariables, or navigation actions; authoring custom `@ExposeToClient` Java services; building design-token themes or component variants (`design-tokens/overrides/**`); or configuring WaveMaker security (intercept-urls, roles query, auth providers). Trigger it even when the user just says "WaveMaker", "wm-", "LiveVariable", "design tokens", "shopbit", or names a WaveMaker file — hand-authored WaveMaker markup has many non-obvious rules that are easy to get wrong.
wm-ps/legacy-to-wavemaker-claude-plugin · ★ 0 · Web & Frontend · score 57
Install: claude install-skill wm-ps/legacy-to-wavemaker-claude-plugin
# WaveMaker Migration & Hand-Authoring Conventions WaveMaker AI apps are normally built in WaveMaker Studio (a visual designer that generates the files). When migrating a legacy app or editing a WaveMaker project **by hand**, the generated file formats have many non-obvious rules — get one wrong and Studio rejects the file or the page renders blank. This skill captures the rules validated against real WaveMaker Studio output. ## Step 0 — Connect Studio ⇄ local sync FIRST (do this before authoring) You cannot preview a WaveMaker app without Studio, so hand-authored files must be verified there. The fastest loop is WaveMaker's **`wavemaker-workspace` Maven plugin** (IDE sync, beta): edit locally, push, the user refreshes Studio, reports back, repeat — no zip/re-import each round. Full detail and the dedicated `/wavemaker-sync` command are in [`references/ide-sync.md`](references/ide-sync.md). **At the very start of any WaveMaker task, ask the user whether Studio⇄local sync is connected. If not, give them these one-time steps and let them run them — then you drive the ongoing sync.** Prerequisites: Git, Maven, and a JDK installed; the project exported/opened once in Studio. One-time setup (**the user runs this — it authenticates**): 1. In an active Studio session, get a token from `https://<your-studio-host>/studio/services/auth/token` (enterprise instances differ from `wavemakeronline.com` — use your own host). Token auth is preferred over username/password so no pa