search-analytics-design

What problem does it solve?

This Skill prevents teams from building unjustified search or analytics engines by defining when they are necessary and how to make them safe, permission-correct, fresh enough, and operationally reliable.

Core Features & Use Cases

• Engine selection with clear decision boundaries: Use purpose-built search/analytics only when full-text relevance, complex faceting, OLAP aggregation, or event analytics cannot be served by the source database.
• Derived-view and source-of-truth contract: Enforces that search/analytics are derived views with explicit write-path ordering so the engine never becomes an unauthorized source of truth.
• Permission, freshness, and reindex governance: Requires permission enforcement in every query, product-approved freshness SLOs, blue-green/zero-downtime reindexing, drift detection, and GDPR Right to Erasure handling for indexed personal data.
• Use Case: Designing an Elasticsearch/OpenSearch/ClickHouse/Druid/Pinot plan for a multi-tenant product where users must see permission-filtered, fresh enough results with a safe reindex and measurable drift controls.

Quick Start

Use the search-analytics-design skill to produce a complete search or analytics design that includes justification, source-of-truth contract, indexed field plan, ingestion and freshness SLO, permission enforcement, zero-downtime reindex strategy, drift detection, GDPR erasure handling, fallback behavior, and observability metrics.