Nexus Commerce

Showing 25 of 33 from the live probe.

• Discover Categories

  Returns the live Discover browse labels with published brand counts, which are the only category values discover_brands accepts. Use it when the merchant asks what categories exist, or to confirm a label before browsing.

• Discover Brand Inspiration

  The Nexus Discover directory of indexed DTC brands: revenue band, positioning, a steal-this hook, and a Discover link for each. Use it for brands to study, brand or PDP inspiration, hero layouts, and category browse (Beauty, Apparel, Beverage, and so on). `category` takes a Discover browse label and `limit` caps the count. Every brand here has real captures behind it, which is what makes the list worth more than a remembered one. It returns brands, not page captures: section-by-section PDP anato

• Brand Lookbook

  Real PDP and hero captures for one indexed Discover brand: page anatomy, hero layout, and a section-by-section teardown. It works on a single named brand, so the brand set itself comes from discover_brands.

• Competitor Benchmark

  Answers 'who are my competitors' and 'who are the real players in my niche' with true peer matches derived from the merchant catalog and web research rather than a generic category list. Returns their derived brand identity, the peer set, and a strategic comparison in Nexus-formatted markdown. Scoped to peer intelligence: storefront health and conversion diagnostics live elsewhere.

• Buy Box Benchmark

  Side-by-side comparison of YOUR product buy box vs. brand-identity-matched peers, with conversion analysis. Captures pixel-accurate screenshots of the real add-to-cart sections (yours + peers) and Claude compares price framing, CTAs, trust signals, and hierarchy. Anchors on your #1 product by default. Use for 'compare my buy box', 'PDP benchmark', 'how does my product page stack up'.

• Scaling Peers

  Brands in your niche scaling ahead of you — matched from products and web research. Use for 'brands scaling past me'. For direct competitors use competitor_benchmark.

• Competitor Page Teardown

  Deep teardown of specific competitor product pages — layout, UX patterns, conversion tactics, and section-by-section notes. Use when the user asks what a competitor does well on PDPs (e.g. 'what does True Classic do on product pages'). Pass competitor domains in `domains`.

• Analyze Store

  Analyze any Shopify store's products, design patterns, and conversion elements

• Create Project

  Create a project on your Nexus board with title, description, priority, due date, and optional target URL. Returns app deep links. When the project is brand work (design, copy, campaign, rebuild), ground the description in nexus_brain facts (products, URLs, voice) before creating.

• List Projects

  List active projects on your Nexus board grouped by kanban column, with status, due dates, comment counts, and deliverable flags.

• Project Insights

  Full project detail: description, status, deliverables, team comments, and playbook-grounded intelligence. Omit project_id for a board-level health summary.

• Comment on Project

  Post a comment on a Nexus project thread. Use list_projects or project_insights to get the project ID.

• Update Project Status

  Move a project on your Nexus board to submitted, in_progress, complete, or cancelled. Use list_projects or project_insights for the project ID.

• Business Overview

  The full picture of your business Nexus works from: connected tools, key store signals, and data freshness from cached business-context (not a live Admin pull on every call). Returns rich markdown with links into the Nexus app. Scoped to operations and stack: brand identity (colors, type, voice, catalog, imagery) is not part of this snapshot.

• Nexus Brain

  Answers questions about this merchant's own brand identity: palette, typography, catalog, pages, and voice, resolved from their live storefront and stored brand system. Use it for "what are our brand colors", "what typeface do we use", "what do we sell". This is a question-answering tool, not a build tool: creative jobs need the compiled rules and packet from resolve_creative_strategy, and asking here for one returns an error instead of a brand dump. It returns facts, not files, and never fetche

• Prepare Brand Execution

  Returns this brand's execution packet: exact hex values, typefaces with downloadable files, button styles, Nexus-hosted product photography, catalog, voice, and the fidelity checklist a delivery is judged against. `intent` scopes the packet to the job (hero, pdp, meta_ad, email, brief, copy); `companion_tool` (for example figma) adds the binding notes for that tool. Facts only, with no compiled rules, no peer cues, and no execution sequence — those come with resolve_creative_strategy, which is t

• Resolve Creative Strategy

  The entry point for any creative job on this brand: homepage hero, PDP, landing page, Meta ad, social, email, or copy, in Figma, Canva, or another design tool. Returns compiled creative RULES for this specific ask, the brand execution packet (hex values, typefaces, buttons, Nexus-hosted product photography, catalog, voice), peer composition cues, and the ordered execution sequence. `ask` is the merchant request in their own words; `intent` narrows the job type; `page_url` names the live page a r

• Deliver Brand Assets

  Places the merchant's real product photography into a design tool. Nexus fetches the bytes and uploads them, so the design session never needs network access to the merchant CDN. Pass the upload URLs the design tool minted (in Figma, `upload_assets` with count = number of images) alongside the packet `assets[].id` values for the photos you want. This is the supported path to brand imagery when a CDN fetch is blocked, and it is what makes generated or placeholder art unnecessary. It uploads image

• Remember Figma Plan

  Stores the Figma planKey/team that worked for this brand so later builds default to it instead of asking again. Takes the values from a successful create_new_file.

• Rebuild Hero

  Homepage hero rebuild or redesign: a thin wrapper around resolve_creative_strategy with the hero intent already set. Returns the same compiled RULES, brand packet, peer cues, and photography gate, scoped to the hero. `page_url` is the live page to react to and defaults to the storefront; `companion_tool` names where the build happens. Scoped to heroes only — other creative jobs belong in resolve_creative_strategy.

• Brand Fidelity Check

  Grades a finished design or copy deliverable against this brand’s execution packet and returns pass/fail per rule with remediation. Report what actually shipped: the asset URLs placed, hex values, typefaces, token values, and copy. Rules cover real product and logo assets instead of generated art, packet hex present, packet typefaces used, no template placeholders, and no invented prices. It grades one candidate per call, so a tool that returns several options (Canva variants, image sets) needs

• Extract Brand Tokens

  Export the connected store's Shopify theme tokens (colors, fonts, spacing, buttons) for use in Figma, Canva, or other design tools. `format: figma` returns structured JSON ready for design-tool variables. This reads the theme settings file, so it reports what the theme declares rather than the resolved brand system a build should bind to, and it returns no Liquid or theme code.

• Brand code index

  Returns a storefront as code: platform and framework detection, CSS custom properties, spacing and radius scales, per-component selectors, class names and markup skeletons. Use this when writing or reviewing front-end code against a brand, when you need the real class convention rather than a description of it, or when comparing the merchant's implementation to a competitor's. Pass `brand` for any public domain, or omit it for the connected merchant. Returns JSON alongside a readable summary.

• Peer code patterns

  Reports how competitors structurally build a given section and how many of them do each thing, then expresses the recommendation in this storefront's own class convention and design tokens. Use this when deciding how to build or restructure a section: "how do competitors do their buy box", "what are we missing on our PDP", "should this be an accordion". Returns counted patterns and ready-to-use class names, not screenshots. Complements buy_box_benchmark, which compares visually.

• Brand Ontology

  Structured brand ontology from Nexus extraction and analysis: entities, relationships, and metric trends across the connected stack. Served from a cached snapshot, so it answers in chat latency rather than a live Admin round trip.