clickhouse-architecture-advisor
MUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs. Complements clickhouse-best-practices with decision frameworks and explicit provenance labels.
What this skill does
# ClickHouse Architecture Advisor This skill adds workload-aware architecture decisioning on top of `clickhouse-best-practices`. > **Official docs remain the source of truth.** > This skill must always prefer official ClickHouse documentation when available. ## Required behavior Before producing recommendations: 1. Identify the workload shape - observability - security / SIEM - product analytics - IoT / telemetry - market data / financial services - mixed OLAP with point-lookups 2. Read the relevant decision rule files in `rules/` 3. Use `mappings/doc_links.yaml` to attach official documentation 4. Classify every recommendation as: - `official` - `derived` - `field` 5. Never present field guidance as official guidance 6. If a recommendation is uncertain, say so explicitly ## Provenance rules ### `official` Use this when the recommendation is directly backed by official docs. ### `derived` Use this when the recommendation is not stated verbatim in docs but follows logically from documented ClickHouse behavior. ### `field` Use this only for experience-based guidance that may be situational. When using `field`, include: - a disclaimer that the advice is heuristic - a relevant official doc if one partially applies - the reason the advice depends on workload context ## Read these rule files by scenario ### Real-time ingestion design 1. `rules/decision-ingestion-strategy.md` 2. `rules/decision-real-time-preaggregation.md` 3. Relevant best-practices insert rules ### Time-series and retention design 1. `rules/decision-partitioning-timeseries.md` 2. Relevant best-practices schema partition rules ### Enrichment and dimension lookups 1. `rules/decision-join-enrichment.md` 2. Relevant best-practices query join rules ### Mutable state / late-arriving events 1. `rules/decision-late-arriving-upserts.md` 2. Relevant best-practices mutation avoidance rules ## Output format Structure responses like this: ```markdown ## Workload Summary - workload: - latency target: - data shape: - primary query patterns: - operational constraints: ## Key Decisions - ... - ... ## Recommendations ### <Recommendation title> **What** ... **Why** ... **How** ... **Category** official | derived | field **Confidence** high | medium | heuristic **Source** - doc link(s) **Validation** - concrete SQL, metric, or smoke test ``` ## Architecture-specific guidance Prefer decision frameworks over generic advice. Good responses should: - explain tradeoffs - identify the likely operating bottleneck - separate immediate actions from structural redesign - provide target architecture patterns, not just isolated settings ## Full reference See `AGENTS.md` for the compiled version and `examples/` for sample outputs.
Related in Data & Analytics
clawarr-suite
IncludedComprehensive management for self-hosted media stacks (Sonarr, Radarr, Lidarr, Readarr, Prowlarr, Bazarr, Overseerr, Plex, Tautulli, SABnzbd, Recyclarr, Unpackerr, Notifiarr, Maintainerr, Kometa, FlareSolverr). Deep library exploration, analytics, dashboard generation, content management, request handling, subtitle management, indexer control, download monitoring, quality profile sync, library cleanup automation, notification routing, collection/overlay management, and media tracker integration (Trakt, Letterboxd, Simkl).
querying-soql
IncludedSOQL query generation, optimization, and analysis with 100-point scoring. Use this skill when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan analysis, and performance or safety improvements for Salesforce queries. TRIGGER when: user writes, optimizes, or debugs SOQL/SOSL queries, touches .soql files, or asks about relationship queries, aggregates, or query performance. DO NOT TRIGGER when: bulk data operations (use handling-sf-data), Apex DML logic (use generating-apex), or report/dashboard queries.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
habit-flow
IncludedAI-powered atomic habit tracker with natural language logging, streak tracking, smart reminders, and coaching. Use for creating habits, logging completions naturally ("I meditated today"), viewing progress, and getting personalized coaching.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
visualizing-data
IncludedBuilds dashboards, reports, and data-driven interfaces requiring charts, graphs, or visual analytics. Provides systematic framework for selecting appropriate visualizations based on data characteristics and analytical purpose. Includes 24+ visualization types organized by purpose (trends, comparisons, distributions, relationships, flows, hierarchies, geospatial), accessibility patterns (WCAG 2.1 AA compliance), colorblind-safe palettes, and performance optimization strategies. Use when creating visualizations, choosing chart types, displaying data graphically, or designing data interfaces.