role-fullstack:search-implementation
/role-fullstack:search-implementation
Implement search features using Meilisearch, Typesense, Algolia, ElasticSearch, OpenSearch, or PostgreSQL full-text search. Covers indexing strategy with incremental sync via CDC or application hooks, autocomplete/typeahead with debounce, faceted search UI with URL-encoded filter state, relevance tuning (field boosts, typo tolerance, synonyms), and common pitfalls. Use when adding product search, content discovery, autocomplete, or faceted filtering to an application.
- Author
- rnavarych ↗
- Repository
- alpha-engineer ↗
- Licence
- MIT
- Last repository change
- 24.07.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Implement search features using Meilisearch, Typesense, Algolia, ElasticSearch, OpenSearch, or PostgreSQL full-text search. Covers indexing strategy with incremental sync via CDC or application hooks, autocomplete/typeahead with debounce, faceted search UI with URL-encoded filter state, relevance tuning (field boosts, typo tolerance, synonyms), and common pitfalls. Use when adding product search, content discovery, autocomplete, or faceted filtering to an application.
Original author description
Implement search features using Meilisearch, Typesense, Algolia, ElasticSearch, OpenSearch, or PostgreSQL full-text search. Covers indexing strategy with incremental sync via CDC or application hooks, autocomplete/typeahead with debounce, faceted search UI with URL-encoded filter state, relevance tuning (field boosts, typo tolerance, synonyms), and common pitfalls. Use when adding product search, content discovery, autocomplete, or faceted filtering to an application.
How it works
- When to use
- Core principles
- Reference Files
SKILL.md preview
--- name: role-fullstack:search-implementation description: Implement search features using Meilisearch, Typesense, Algolia, ElasticSearch, OpenSearch, or PostgreSQL full-text search. Covers indexing strategy with incremental sync via CDC or application hooks, autocomplete/typeahead with debounce, faceted search UI with URL-encoded filter state, relevance tuning (field boosts, typo tolerance, synonyms), and common pitfalls. Use when adding product search, content discovery, autocomplete, or faceted filtering to an application. allowed-tools: Read, Grep, Glob, Bash --- # Search Implementation ## When to use - Adding full-text search to a product catalog or content site - Building autocomplete or typeahead input - Implementing faceted filtering with sidebar checkboxes and result counts - Syncing a database with a search index (initial bulk load + incremental updates) - Tuning relevance ranking after users complain results are wrong - Choosing between self-hosted (Meilisearch, Typesense) and managed (Algolia) ## Core principles 1. **Engine matches scale and budget** — pg_trgm for small datasets with no extra infra; Meilisearch/Typesense for fast typo-tolerant search on a budget; Algolia when managed SaaS and rich UI components justify the cost 2. **Denormalize for search** — flatten related data into the search document at index time; joins at query time kill latency 3. **Incremental sync, not full re-index** — hook into Prisma middleware, DB triggers, or a CDC pipeline; bulk re-indexing on every change is the first thing that breaks under load 4. **Debounce is not optional** — 200-300ms debounce on autocomplete input; without it you hit rate limits and burn the user's battery 5. **Encode filters in the URL** — active facets belong in `useSearchParams`; shareable and bookmarkable search state is a product feature, not a nice-to-have ## Reference Files - `references/engine-selection-indexing.md` — engine comparison table with latency and hosting characteristics, four-step indexing strategy, incremental sync options (CDC, hooks, job queue), Meilisearch settings and search code example - `references/ui-patterns-relevance.md` — debounced useSearch hook with TanStack Query, keepPreviousData pattern, faceted search UI with URL sync, relevance tuning controls (field boosts, typo tolerance, synonyms, stop words, custom ranking), common pitfalls
Files in this package (3)
- SKILL.md 2 KB
- references/engine-selection-indexing.md 2 KB
- references/ui-patterns-relevance.md 2 KB
Versions
The database has no other skills named role-fullstack:search-implementation.
Database snapshot: 13.11.2026 · package version 35d4342a5810 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 80role-database:search-engines
Deep operational guide for 10 search engines. Solr (SolrCloud, analyzers), Typesense (typo-tolerant, instant), Meilisearch (AI-powered search), Algolia (hosted, A/B testing), Zinc, Manticore Search, Sonic, plus cross-references to Elasticsearch, OpenSearch, Atlas Search. Use… - 100typesense
Typesense is an open-source, typo-tolerant search engine for instant search: sub-50ms queries, filters, facets, geo search and synonyms, self-hosted or in Typesense Cloud. Use when a user wants to run Typesense with Docker, define a collection schema, index documents, search… - 100meilisearch-instant-search
Use this skill when deploying typo-tolerant, instant search endpoints with faceted filtering using Meilisearch. - 100search-design
Use when the user is designing search: Elasticsearch or Typesense indexes, mappings, analyzers, relevance tuning, autocomplete, faceting, full-text search, or syncing search from the source of truth. - 100instantsearch
Build production-quality search experiences (autocomplete, search results pages, faceted search) using InstantSearch. Use when user asks to add search, autocomplete, search-as-you-type, faceted filtering, or a search results page to a React, Vue, or vanilla JS application, or… - 90distributed-search
This skill should be used when the user designs a "search system", needs "full-text search", asks about an "inverted index", "Elasticsearch / OpenSearch", "relevance ranking" (TF-IDF/BM25), "search autocomplete / typeahead", an "indexing pipeline", or "faceted search". It gives…