Motion Menu

Audit an EXISTING page (yours or a client's — any AI builder, any stack) for the default-AI "section grammar" tell: numbered steps, a centered hero with two buttons, 3-up icon cards, a testimonial/FAQ/CTA-band skeleton repeating unchanged. Deterministic, no LLM — every finding cites the exact matched HTML. Returns an ai_shaped_score (0-100), per-section tells with evidence, page-level tells (skeleton order, uniform scaffolding, default type/motion), and prescriptions: real Motion Menu patterns to replace each flagged section, drawn from the same graph recommend_patterns/validate_combination use, plus the exact next tool calls to fetch and validate them. FREE, no key required.

Design a complete page from intent. Returns an act map — 5–7 acts in page order, each with a purpose, recommended patterns (by slug), and a density rating (loud/quiet). Follows the one-page protocol: density wave pacing, one GL spectacle, 12–18 viewport-heights. Feed the result straight to compose_page or get_pattern to retrieve the code. Returns metadata only — no pattern bodies.

Check whether patterns you already built with have changed. Pass the library version you last built against (from `version` in a previous check_updates or /p/manifest.json) and get back exactly which slugs were added, changed or removed — so you re-pull three patterns instead of all of them. Call with no arguments to read the current version and library counts. Record the version you get back alongside the code you generate.

Compose a complete standalone working page from Motion Menu patterns — OR, given a `brief` instead of `sections`, get back a structured COMPOSITION PLAN (pattern picks with reasons, no HTML) reasoned over the pattern graph: role fit, pairs_with affinity, clashes checked across the whole plan, max_per_page/placement enforced by construction (one spectacle max, heavy never early, footer terminal). A plan can never contain a violation validate_combination would also reject — same rule engine, checked before each pick. Give explicit `sections` (pattern numbers in page order) and a theme instead to get back one self-contained HTML document with the scroll spine, shared runtime, page-level chrome, and all pattern code already themed. Both modes require the compose entitlement (Lifetime plan) and design_digest_version: 1 so the anti-generic quality contract is explicit. Per-section "swap" (sections mode only) replaces literal text strings (find→replace) to put real copy in.

Get the machine-readable Motion Menu quality contract. Call before build_page or compose_page. It defines anti-generic composition rules, motion lifecycle, responsive requirements, truth constraints, and release verification gates.

Get the Motion Menu build kit: the design laws, the one-page act protocol, stack pins, known gotchas, and the full pattern index. Call this FIRST before building a page.

Get one pattern by number, including its complete transplantable HTML, CSS and JS. Pass framework to get a ready-to-use component wrapper (react .tsx, vue .vue, svelte .svelte, or vanilla .ts). Pass theme (e.g. "daf", "wb", "blmedia" — see list_themes) to receive the bundle ALREADY re-skinned: themed :root tokens prepended and every known JS/GLSL color literal rewritten. No color work needed on your side.

Get one theme: token values, font stacks, ready-to-paste :root CSS block, and the literal→color substitution map for theming code by hand (exact strings: hex, 0x numbers, "r,g,b" triplets, GLSL vec3). Build/tune themes at /theme.html.

List Motion Menu patterns. Every row is "number slug <role> [tags] · title". ROLE is where the pattern goes on a page (hero, nav, pricing, background, product, form…) — filter by it when you are building a page rather than hunting an effect. The SLUG is the permanent identity — prefer it. Filter by tag (e.g. "scroll", "webgl", "seam", "commerce"), by collection slug (e.g. "seams-handoffs"), by free-text query, or by legacy section letter. Call with no arguments to see the whole catalogue and its tag vocabulary.

List available Motion Menu themes (name, mode, label) for get_pattern/get_theme.

Intent-aware pattern recommendations. Describe what you are building — industry, style, mood, technical needs — and get scored results with reasons and compatibility suggestions. Returns metadata only (number, slug, title, role, score, reason, compatible_with). Call get_pattern to retrieve the actual code for any recommendation.

Check whether a set of patterns work well together. Pass the slugs (or numbers) of patterns you plan to combine on a page and get a compatibility report: overall score, per-pair analysis, style/industry coherence, intensity balance, page-flow coverage, and warnings (duplicate roles, missing positions, too many heavy patterns). Call BEFORE compose_page to catch mismatches early.

Re-audit a page you just rewrote from audit_page's prescriptions and get a pass/fail verdict: fresh ai_shaped_score, the delta from the prior audit (pass baseline_score or the whole prior audit_page result as `baseline`), and any tells STILL present, each with a concrete fix instruction. FREE, no key required.