design-search-index-infra

Design Elasticsearch mappings, HNSW parameters, and hybrid RRF ranking strategies.

9|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill design-search-index-infra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-search-index-infra
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/design-search-index-infra
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill design-search-index-infra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of designing and tuning search backends, preventing common pitfalls like poor relevance, slow query performance, and downtime during index updates.

Core Features & Use Cases

  • Search Infrastructure Design: Define robust mappings, analyzers, and vector index parameters for Elasticsearch or OpenSearch.
  • Relevance & Performance Tuning: Implement hybrid search (BM25 + Vector) using RRF, optimize shard topology, and manage zero-downtime reindexing.
  • Use Case: When scaling a search cluster to millions of documents, use this skill to configure HNSW parameters for optimal recall-latency trade-offs and establish an alias-based reindexing strategy to ensure continuous availability.

Quick Start

Use the design-search-index-infra skill to generate an immutable mapping configuration for a new product catalog index that supports both keyword and semantic search.

Frequently Asked Questions about design-search-index-infra

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Elasticsearch mappings for both keyword and semantic search?

Configure Elasticsearch mappings by defining robust analyzers for full-text BM25 retrieval alongside dedicated vector index parameters for semantic search. This approach ensures high-recall retrieval and efficient memory utilization across millions of documents.

What's the best way to tune HNSW vector parameters for optimal search recall-latency trade-offs?

Tune HNSW vector parameters by adjusting index configurations to balance graph connectivity and search radius, achieving an optimal recall-latency trade-off. This ensures efficient memory utilization during high-performance vector search operations.

How does hybrid search using RRF ranking work in OpenSearch?

Hybrid search using Reciprocal Rank Fusion (RRF) in OpenSearch combines BM25 full-text relevance scores with vector search similarity scores. This ranking strategy merges independent result sets to deliver high-recall retrieval without requiring manual score normalization.

How do I perform zero-downtime reindexing in Elasticsearch?

Perform zero-downtime reindexing in Elasticsearch by establishing an atomic alias-based reindexing strategy. This index lifecycle management technique routes queries through aliases, allowing background index rebuilding without interrupting continuous search availability.

Can I use this approach to scale a search cluster to millions of documents?

Yes, this search infrastructure design applies directly when scaling a search cluster to millions of documents. It optimizes shard topology and HNSW vector parameters to maintain high-recall retrieval and efficient memory utilization at massive scale.

Why does my vector search experience slow query performance and poor relevance?

Slow query performance and poor relevance in vector search often stem from unoptimized HNSW parameters and inadequate shard topology. Designing proper vector index parameters and hybrid RRF ranking strategies resolves these backend architecture pitfalls.