Skip to main content
Reference

What the StoreFront Agent Toolchain can do

Overview​

Each page in this section covers one area of a StoreFront: what the agent can do there, example requests you can give it, the uc-storefront commands involved, what is out of scope, and what needs your approval. The commands are listed so you can recognize what your agent proposes; you do not need to run them yourself.

AreaWhat the agent can work on
Pages and themesPage layouts and content, new and copied pages, templates, menus, theme colors and fonts, site settings, catalog search facets
Checkout and My AccountThe layout and styling of checkout and the customer account pages
ItemsItem attributes, title, description, SEO, images, prices, pre-order, variations and related items
UpsellsUpsell paths and offers, and each offer's page
CommunicationsCampaigns, flows, segments, lists, emails, SMS steps and postcards
Analytics and trackingWarehouse queries, screen recordings, render logs, and tracking and privacy settings
LanguagesStorefront languages, translations and built-in messages
Redirects and 404s301 redirects, missed paths, and the 404 page
ExperimentsA/B tests on a page or between pages
Blog postsBlog posts, their images and SEO
Files and assetsImages, video, fonts, PDFs, CSS and JSON files, and file history
SurveysSurveyJS survey files and the survey element

Commands every area shares​

Every area uses the same small set of commands to read and write StoreFront content:

CommandWhat it does
sf storefronts, sf themesList your storefronts and a storefront's themes
sf pull, sf pushRead a page body or theme container into a local file with a baseline, and write it back with a guarded push
sf containers pull, push, versions, revertThe same for item, upsell, email and postcard containers, which are stored as records
cjson tree, cjson update, cjson add, apply --plan, cjson validateInspect and edit a local CJSON file, then validate it
element search, element explain, schema showLook up an element and the settings it accepts in the packaged catalog
sf idsReserve real widget IDs from UltraCart before adding widgets
sf preview start, stage, open, endShow staged changes on the real storefront without saving them
sf renderRender one widget against a theme, without writing
sf snapshot take, sf snapshot diff, sf reportRecord a storefront's layout at handoff, compare it later, and make a PDF of it

Run uc-storefront --help or uc-storefront sf --help for the full command list of the version you have installed. The help is the authority when it differs from these pages.

Outside the toolchain​

Some UltraCart work is done in the admin, not through the CLI. In the current beta that includes activating a theme, creating or deleting standalone items, inventory, shipping, tax and wholesale pricing tiers, orders and customers, coupons, payment settings, creating a storefront and changing its domains, and starting or sending a campaign. Each area page lists its own limits. The agent skill tells your agent to say so up front when a request needs one of these, rather than work around it.

Was this page helpful?