Doris Best Practices

---
name: doris-best-practices
description: >
  Apache Doris table design and cluster sizing best practices.
  MUST USE when writing, reviewing, or optimizing Doris CREATE TABLE statements,
  partition/bucket strategies, data models, or cluster configurations.
  ALSO MUST USE whenever the doris-architecture-advisor skill produces DDL — apply
  the Pre-Flight Checklist to every CREATE TABLE before output.
  Also triggers on any workload design involving: IoT, analytics, dashboard, CDC,
  time-series, log analysis, real-time warehouse, point query, data platform, or
  any scenario where table design decisions are being made.
  Also triggers on replacing or migrating from legacy analytics/search/serving
  stacks such as Impala, Kudu, Elasticsearch/ES, Greenplum, Presto, HBase,
  Hive, Hadoop, Redis, or Lambda-style multi-engine data platforms, even when
  Apache Doris is not named explicitly.
  Also use when user provides an Apache Doris connection string or asks to get started.
  Also triggers on slow query investigation, query profiling, runtime performance
  diagnosis, tablet skew analysis, and table health checks — any scenario where
  runtime evidence (profile output, tablet distribution) informs optimization.
  Cluster lifecycle, billing, and networking are managed-service operations, out of
  scope here — use your platform's cluster-management console for those.
license: Apache-2.0
metadata:
  author: tomz-alt
  version: "0.1.0"