Brainerce

Skills

• brainerce-analytics

  Answer how much, how many, what is best and what is the trend for a Brainerce store, using the right reporting tool instead of counting rows by hand. Use when the merchant asks about revenue, sales, total orders, average order value, best or worst sellers, how this month compares to last, whether a sale worked, how many customers, or what people think of a product. Turns a plain question into the correct statistics call and answers with a number plus what it means. Also owns retention, coupon performance, stock velocity, traffic and connection health. For store owners, not developers. Not for the morning check-in (brainerce-daily-summary), acting on one order (brainerce-order-handling) or a health sweep (brainerce-store-health). Keywords: revenue, sales, how much, how many, total, average order value, AOV, best sellers, trend, compare, month over month, growth, conversion, retention, repeat customers, stock velocity, traffic, ratings, reviews, report, analytics.

• brainerce-checkout-flows

  Get the non-negotiable Brainerce sequences right: checkout, registration and email verification, login, password reset, cart persistence, inventory reservation and order confirmation. Use when a developer is building or debugging any of those, or asks why is my order not appearing, the payment succeeded but nothing happened, my reservation expired, the cart empties on refresh, or what order do these calls go in. These flows are fixed regardless of framework, and improvising one produces orders that never complete and stock that never releases. For developers. Do not choose this for the signature of a single method, use brainerce-sdk. Do not choose this to plan a whole storefront, use brainerce-storefront-build. Do not choose this for a merchant asking where a specific customer order is, use brainerce-order-handling. Keywords: checkout, payment, order confirmation, handlePaymentSuccess, waitForOrder, reservation, cart persistence, login, email verification, reset password, OAuth callback.

• brainerce-content-and-navigation

  The words on a Brainerce storefront that are not product copy: static pages, FAQs, footers, the header and its navigation links, announcement bars, the blog, and the SEO around them. Use when the merchant asks where do I write my About page, how do I add a shipping policy, can I add a banner at the top, or how do I get found on Google. Says which pieces exist, where each is configured, and which a storefront must read before anything shows up. Also owns the contact form. Content, blog and contact-form tools are OAuth-only and absent from the ChatGPT app, and navigation has no tool at all, so it gives exact dashboard routes rather than pretending. For store owners and for developers wiring content in. Do not choose this for products, categories or tags, use brainerce-store-architecture. Do not choose this for product specs, use brainerce-custom-fields. Keywords: pages, about page, policy page, terms, FAQ, footer, header, navigation, menu, announcement bar, blog, contact form, SEO, meta description, sitemap.

• brainerce-custom-fields

  Work with Brainerce custom fields, also called metafields: the structured extra data a product carries beyond its built-in fields. Use when the merchant says add a spec to my products, where do I put materials or care instructions, I need a size guide link on every item, let customers type an engraving, or make this filterable on my shop. Covers the definition versus value split, which of the fifteen types to pick, and the two flags that decide whether a field is buyer-facing or filterable. Writes values only over an OAuth connection; on an API key the metafield tools refuse outright. Creating a definition is a dashboard step either way, and this skill says so rather than pretending. For store owners, and for developers reading fields on a storefront. Do not choose this to decide whether a property should be a custom field at all, that is brainerce-store-architecture. Keywords: custom fields, metafields, specs, materials, care instructions, engraving, storefront filter, product attributes.

• brainerce-daily-summary

  Give a Brainerce store owner one short morning briefing: what sold, what came in overnight, what needs attention today. Use when the merchant says how is the store doing, what happened yesterday, catch me up, morning report, daily summary, any orders overnight, or what do I need to deal with today. Assembles sales figures, order counts and low-stock warnings into a single readable answer instead of three separate tool dumps. For store owners, not developers. Do not choose this for one specific metric or a trend question such as which product sells best or how does this month compare to last, use brainerce-analytics. Do not choose this for a full audit of drafts, expired promotions and stuck orders, use brainerce-store-health. Do not choose this to act on a particular order, use brainerce-order-handling. Keywords: daily summary, morning report, briefing, catch me up, overnight, how is the store doing, today, yesterday, standup, dashboard.

• brainerce-email-campaigns

  Send a marketing email to a Brainerce store's customers safely: pick the audience, write or reuse the email, check who it reaches, then send or schedule it. Use when the merchant says email my customers, send a newsletter, announce the sale by email, email my VIP buyers, save this as a template, schedule an email for Friday, who would get this email, or make a customer segment. Covers saved customer segments, campaign templates, drafting, the recipient count check and the send itself. A send reaches real people and cannot be recalled, so this skill puts the count check and the merchant's yes before it. For store owners, not developers. Do not choose this for the signup welcome coupon or for a promotion itself (brainerce-launch-a-sale), for a fundraising drive (a donation campaign), or for transactional order emails. Keywords: email campaign, newsletter, email blast, segment, audience, template, schedule send, mailing list, send email to customers.

• brainerce-integration-verify

  Audit a Brainerce storefront against the mandatory-feature checklist and the critical rules, and report what is missing, present but unreachable, or wrong. Use when a developer says is my integration complete, check my Brainerce build, did I miss anything, review this before launch, why is this feature not working, or before shipping a storefront to a real store owner. Walks the actual code rather than trusting that a file exists, with particular attention to the features that are almost always skipped. For developers. Do not choose this to build something new, use brainerce-storefront-build. Do not choose this for one method's signature, use brainerce-sdk. Do not choose this for the correct order of a checkout or login sequence while writing it, use brainerce-checkout-flows. Do not choose this for a merchant auditing their shop's products and promotions, that is brainerce-store-health. Keywords: verify, audit, checklist, did I miss anything, pre-launch, mandatory features, critical rules, ready to ship.

• brainerce-launch-a-sale

  Set up a sale, promotion or discount on a Brainerce store and confirm it is actually live. Use when the merchant says take 20% off, run a sale, create a discount code, set up a voucher, or schedule a Black Friday deal. The core of this skill is the choice between an automatic discount that applies by itself in the cart and a coupon code the shopper has to type, because getting that wrong is the mistake merchants notice. Also covers loyalty points, earning rules, badges and paid plans, and gift cards: a gift card is stored value the customer spends, not a discount, never a coupon. For store owners, not developers. Do not choose this to review a past promotion, use brainerce-analytics, or to hunt for expired ones, use brainerce-store-health. Do not choose this to set up shipping zones or what shipping costs, use brainerce-store-architecture. Keywords: sale, discount, promo code, coupon, voucher, BOGO, free shipping offer, Black Friday, loyalty, points, earning rules, membership, gift card.

• brainerce-order-handling

  Work a single Brainerce order from question to action: look it up, understand its state, then fulfil, move its status or cancel it. Use when the merchant says where is order 1042, this customer is asking about their order, mark this as shipped, add tracking, or cancel this one. Includes when NOT to touch an order, and the pay-before-fulfill gate that blocks shipping an unpaid order. Also owns manual orders, status labels, shipping labels and the contact-form inbox; those, plus refunds and returns, are on the full connector and not the ChatGPT app, so check the tool list. For store owners, not developers. Do not choose this for counts and totals across many orders, use brainerce-analytics or brainerce-daily-summary. Do not choose this to sweep for stuck orders across the whole store, use brainerce-store-health. Keywords: order, fulfil, ship, tracking number, cancel order, order status, where is my order, refund, return, mark as paid, manual order, status label, shipping label, inquiry, order custom fields.

• brainerce-product-onboarding

  Add a product to a Brainerce store properly, from creating it through to category, tags, stock and publishing. Use when the merchant says add a product, list this item, put this in the shop, set up my new range, copy an existing product, or fix the stock count on something. Also covers duplicating a product, publishing the whole catalog to a storefront, stock corrections and stock history. For store owners, not developers. A price or description edit on a set-up product needs no sequence. Not for reviews (brainerce-analytics), finding drafts (brainerce-store-health) or variant versus custom field (brainerce-store-architecture). Keywords: add product, new product, create product, stock count, inventory, restock, categorise, tags, publish, publish all, duplicate product, bulk import, CSV import, product images, alt text, stock history, sale price dates.

• brainerce-sdk

  Look up the real shape of the Brainerce storefront SDK: method names, arguments, return types and the TypeScript definitions behind them. Use when a developer asks what does this SDK method take, what comes back from it, what is the type of a product or an order, how do I fetch products with variants, which method loads a category, or is there a method for this at all. This is the reference, so reach for it whenever you are about to write a Brainerce call and are not certain of its exact signature. For developers. Do not choose this for the ordered sequence a checkout or login has to follow, use brainerce-checkout-flows. Do not choose this to plan or scaffold a whole storefront, use brainerce-storefront-build. Do not choose this for admin or dashboard operations such as creating a product as a merchant, those are merchant skills. Keywords: SDK, method, signature, arguments, return type, TypeScript types, interface, BrainerceClient, getProducts, types, API reference, does this method exist.

• brainerce-store-architecture

  Decide how a Brainerce catalog should be structured, and audit an existing one: what becomes a variant, what becomes a custom field, what becomes a category, what becomes a tag. Use when the merchant asks how should I organise my shop, should this be a variant or an option, categories or tags, or I have too many variants to manage. Also owns store settings (currency, language, going live), shipping zones, rates, labels, sales-channel publishing, subscriptions, apps, email domains, webhooks and backups. Free shipping as a standing rate lives here; as a promotion it does not. For store owners and developers deciding a data model. Do not choose this to add one product, that is brainerce-product-onboarding. Do not choose this for custom fields in depth, use brainerce-custom-fields. Do not choose this for pages or menus, use brainerce-content-and-navigation. Keywords: catalog structure, variant explosion, categories vs tags, shipping zones, sales channels, go live, currency, subscriptions, email domain, webhooks.