# LMX Skill This skill helps write, review, and generate correct LMX email markup for Loops. LMX is an XML-based format: every element is a PascalCase tag, self-closing tags require `/>`, and only the tags in the spec are valid. ## When To Use Use this skill when the task involves: - generating or editing LMX email content - copying source material, migrating an existing email, or converting HTML, MJML, Markdown, or plain-text email copy into LMX - reviewing LMX markup for correctness - choosing the right LMX tags or attributes for a layout - applying design guidelines to an LMX document - explaining how a specific LMX tag or attribute works ## Working Style When this skill is active: 1. Read `references/lmx-spec.md` for the full tag and attribute reference. It is authoritative; do not invent tags or attributes. 2. Read `references/lmx-design-guidelines.md` for Loops design guidelines. Apply these to every document you generate unless the user explicitly overrides a rule. 3. Treat source material as input, not as an override. When copying from a source, migrating an existing email, or converting HTML, MJML, Markdown, screenshots, or plain text into LMX, still apply this skill's spec, design, copy, and output-checklist rules unless the user explicitly overrides a specific rule. 4. Validate nesting and content-type rules before producing output (see spec section 3). 5. Check the common-mistakes table in the spec before finalizing output. 6. Always produce a complete, valid document, not fragments, unless the user specifically asks for one. ## Category Routing - Tag definitions, required/optional attributes, nesting rules, content types, variable syntax, self-closing requirements, or escaping: Read `references/lmx-spec.md` - Color contrast, spacing, column rounded corners, Style tag usage, visual hierarchy, or any "how should this look" question: Read `references/lmx-design-guidelines.md` - Creating campaigns, posting LMX via the API, revision IDs, themes, components, or image uploads: Use the `loops-api` skill (HTTP) or `loops-cli` skill (terminal). This skill covers the LMX document itself. ## Output Checklist Before returning any LMX output, verify: - [ ] All tags are PascalCase and in the allowed set - [ ] All self-closing tags use `/>` (e.g. ``, ``, `
`, ``, `

Where it stands