AddThisFeature

Search Synonyms and Aliases

Find the right thing even when users call it by a different name.

moderate Search & Discovery

What it adds

A managed set of synonyms, aliases, and common misspellings applied at match time so alternate wording still finds the record.

What your agent is told to do

5
  1. 1

    Build a synonym set the app can edit, covering the three real cases: industry jargon versus plain language, product names that changed, and misspellings your logs show people actually type.

  2. 2

    Expand the query at match time, not the stored documents, so a synonym change takes effect immediately without a reindex.

  3. 3

    Scope sets by workspace, language, and object type. A word that means one thing in one tenant's vocabulary means nothing in another's.

  4. 4

    Rank exact matches above synonym matches so the literal term the user typed still wins.

  5. 5

    Do NOT expand aggressively. Every added term widens the result set, and a search that returns everything is the same as a search that returns nothing.

Edge cases it handles

6
  • Circular and chained rules must be resolved or rejected at save time, or one expansion cascades into the whole dictionary.
  • One-way aliases and two-way synonyms are different. An old product name should map to the new one, not the reverse.
  • Multi-word synonyms must match as a phrase, not as loose independent tokens.
  • When a result matched only via a synonym, say so — otherwise a hit with none of the typed words looks like a bug.
  • Short synonyms collide with unrelated words. Require a minimum length or an explicit exact-term rule.
  • Someone must own the list. An unmaintained synonym set decays into wrong results nobody can explain.

Definition of done

8
  • Synonyms, one-way aliases, and misspellings are stored in an editable set.
  • Expansion happens at query time and takes effect without a reindex.
  • Sets are scoped by workspace, language, and object type.
  • Exact matches rank above synonym-only matches.
  • Circular rules are detected and refused when saved.
  • Synonym-driven results are labelled as such in the UI.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.