What problem does it solve?
This skill provides workload-aware architecture decisioning for ClickHouse, translating best practices into workload-specific system designs and embedding explicit provenance labels to distinguish official, derived, and field guidance.
Core Features & Use Cases
- Workload classification and scenario mapping to guidance tailored for real-time ingestion, time-series, and mutable-state workloads.
- Decision frameworks that translate official documentation and core ClickHouse behavior into architecture patterns (e.g., raw vs pre-aggregated paths, partitioning, and enrichment strategies).
- Explicit provenance labeling for each recommendation (official, derived, field) with clear sources and validation steps.
- Output contracts that structure guidance into workload summaries, key decisions, target architectures, example patterns, and validation tests.
- Read and reference rule files under rules/ and link documentation via mappings/doc_links.yaml to attach official docs.
- Non-reliance on field guidance as official and explicit disclaimers when uncertain.
- Supports multiple workload scenarios and provides actionable architecture patterns, not low-level tuning.
Quick Start
Provide architecture guidance for a representative ClickHouse workload by applying the decision frameworks and citing provenance sources.
