All products

Design Algolia search records with AI

Decide what a result represents before indexing a catalogue. Specify stable identifiers, visible fields and the relationship between variants and stock.

Design Algolia search records with AI before turning every stock row into a result card. For a lamp sold in two finishes, a shopper might expect two photographs but only one product page. If the brass version is unavailable, the filter and the displayed card still need to agree.

The algolia-data-modeling skill uses examples to compare a record per product, per variant or per group. It also asks where each field comes from and how it changes. The resulting design gives the people building the index and the interface a shared description of one result.

What it does

  • Choose when a variant deserves its own result
  • Pick an identifier that survives a title edit
  • Separate card details from internal fields used for ranking
  • Describe how stock and price changes reach the record
  • Check colour filters against real combinations available to buy

Install and use

  1. Install the skill in a compatible agent and supply representative, shareable catalogue records. Planning needs samples. Inspecting or changing a live index needs separate authorised tooling.
  2. Ask, “Design records for these lamps. Compare one card per finish with one card per product, including a case where brass sells out.”
  3. Walk through a rename, a stock change and a new variant. Check that the card, filter and destination page still refer to the same item.

FAQ

Source

Made by Algolia. Original skill: algolia-data-modeling, published on GitHub under the MIT licence.

View on GitHub