elevate

Elevate — orchestrator

0. Preflight — identical to craft (see ${CLAUDE_PLUGIN_ROOT}/skills/craft/SKILL.md §0).

1. Read the project

Stack (confirm Next.js — if not, report that v0.1 only supports the fixed stack and stop); sections; existing animations (GSAP? Lenis? CSS?); existing DESIGN.md/PRODUCT.md or brand source (same resolution as craft §1). Detect the mode: Preserve (modernize without breaking identity) or Overhaul (new visuals, preserve content). State it in the gap-analysis.

2. Gap-analysis

Score the current page against the Awwwards anatomy checklist (${CLAUDE_PLUGIN_ROOT}/skills/direction/references/awwwards-rubric.md) + run impeccable's audit + its detector once over the target: node <impeccable-base>/scripts/detect.mjs --json <target> (base dir resolved in preflight). Consume its findings instead of re-deriving them; anything it already reports is a fix item, not a new observation. Output: what it has / what is missing / what is wrong (with file:line refs). Also score the copy: hero tests, arc coherence, banned language, micro-copy (see ${CLAUDE_PLUGIN_ROOT}/skills/direction/references/copywriting.md). Copy rewrites are a modernization lever — place them with typography (highest lift, lowest risk).

3. Elevation plan → GATE

Prioritized items (impact vs effort), each: what changes, which recipe applies, expected checklist deltas. ═══ STOP: human picks items ═══ Overhaul mode only: offer the comp round with the plan — three rendered compositions of the new first viewport (~3 credits, priced with get_cost), so the human approves a composition instead of a description. Follow ${CLAUDE_PLUGIN_ROOT}/skills/direction/references/comps.md; elevate never invokes direction, so run it here. Preserve mode does not comp: the incumbent composition is the reference, and rendering alternatives invites a redesign nobody asked for.

4. Apply approved items using ${CLAUDE_PLUGIN_ROOT}/skills/build-recipes (same rules).

Apply modernization levers in this order (highest lift / lowest risk first): typography refresh + copy rewrites (headline/CTA/banned language — same tier: highest lift, lowest risk) → spacing & rhythm → color recalibration → motion layer → hero and key-section recomposition → full block replacement (last resort). Never silently change slugs, nav labels, form field names, or legal copy. Token changes land in DESIGN.md's YAML frontmatter (normative) and, when they touch motion/shadows/breakpoints, in .impeccable/design.json — see the "On approval" section of ${CLAUDE_PLUGIN_ROOT}/skills/direction/SKILL.md. Never silently overwrite a DESIGN.md written by impeccable. If the approved items require new assets, the same credit ceiling rule applies — propose the ceiling with the elevation plan and stop before exceeding it. If any of them is a VIDEO asset, price the tier menu with get_cost and present it with the elevation plan exactly as Pass-1 item 9 of ${CLAUDE_PLUGIN_ROOT}/skills/direction/SKILL.md prescribes; elevate never invokes direction, so the menu has to be run here or the tier gets picked by an agent instead of the human. (Lever order distilled from taste-skill, MIT.)