MaterializeInc

Trigger: "commit", "prepare commit", "create PR", "push", "open pull request", or mentions committing, pre-commit checks, pull requests in Materialize. Also "ship it", "ready to merge". For code review use mz-pr-review.

Trigger: adding or changing a feature flag, dyncfg, or system parameter default, reviewing a PR that adds one, LaunchDarkly flag setup, or bin/lint-test-flags failures in Materialize.

Run the Console scalability suite against a replayed captured workload and measure what Console load costs mz_catalog_server: a replay-only baseline, the Playwright suite, the k6 ramp, and an optional sweep of N headless viewers fitted to CPU per viewer.…

Local code review of current branch vs Materialize standards. Trigger: "review my code", "review my changes", "check my diff", "does this look ok", "what do you think of this PR", "code review", or look over changes before merging. Also PR number + wants…

Trigger: adding, removing, or updating a Rust dependency, changing crate features, touching Cargo.toml or Cargo.lock, "cargo update", "add a crate", "bump a dependency", or a new dependency license in Materialize.

Review a Console (`console/`) PR or diff the way Console reviewers do: run the change to verify claims, check it against the patterns and helpers the app already has, and post findings as one GitHub review. Trigger: "review this console PR", "review my…

Verify a release candidate on the Grafana dashboards and sign off in #release. Trigger: "verify the release", "sign off on the release", "release verification", "check the canary", "does this release look healthy", a pasted grafana.dev.materialize.com…

Add/modify/debug Materialize perf benchmark scenarios. Three frameworks: Feature Benchmark (single-op micro), Scalability Test (SQL throughput under concurrency), Parallel Benchmark (sustained latency via scenarios.py). Trigger: "benchmark", "feature…

Materialize documentation for SQL syntax, data ingestion, concepts, and best practices. Use when users ask about Materialize queries, sources, sinks, views, or clusters.

Reduce the memory footprint and cost of Materialize compute clusters: find where arrangement memory sits, pick and size the right optimization lever (index strategy, GROUP SIZE hint tuning, view slimming, subquery decorrelation), adjudicate proposed index or…

Use when a Materialize object is behind wall-clock time — high lag in mz_wallclock_global_lag, a stale or lagging materialized view, index, or sink, a freshness alert, results that keep showing old data, or a dataflow whose output cannot keep up with its…

Trigger: "demo data", "synthetic data", "live operational data", "generate fake data", "create a demo", "load generator alternative", or wants realistic continuously-updating data in Materialize for a demo. Also "I need streaming data to show off X" or "build…

Terraform modules for deploying self-managed Materialize on AWS (EKS), Azure (AKS), and GCP (GKE). Covers networking, Kubernetes clusters, managed PostgreSQL, object storage, the Materialize operator, and Materialize instance configuration. Use this skill…

Analyze a Materialize environment via the MCP Developer endpoint, and/or configure an MCP client (Claude Code, Cursor, VS Code, Zed, Continue, Windsurf, Claude Desktop) to connect to the materialize-developer server. For analysis: check environment health,…

Using the dbt-materialize adapter to manage Materialize streaming pipelines with dbt. Covers materializations (source, source_table, view, materialized_view, sink, table, seed), profile configuration, index creation, blue/green deployments (deploy_init,…

Using the Materialize Terraform provider to manage Materialize resources declaratively. Covers clusters, sources (Kafka, Postgres, MySQL, SQL Server), sinks (Kafka, Iceberg), connections, materialized views, indexes, tables, roles, grants, secrets, network…

This skill should be used when developing Helm charts under `charts/*` — templates, `values.yaml`, subchart wrapping, profile overlays, helm-docs annotations, and helm-unittest tests. Covers more than just templates.

Use this skill when building, modifying, reviewing, or pushing Grafana dashboards under `packages/dashboards/` (Materialize observability dashboards generated from Rust against the vendored Grafana schemas). Also use it when writing the panel descriptions and…

This skill should be used when standing up the monitoring stack against a real or local cluster, or when diagnosing one that is not healthy — pods that will not start, storage that will not attach, config changes that appear to do nothing, or a teardown that…

This skill should be used when writing or editing Markdown prose in this repository, including any page under `docs/content/`, any `SKILL.md`, and `README.md` files. Covers the Google developer documentation style guide the repository follows, the house…

This skill should be used when adding, changing, reviewing or vetting an alerting rule or a recording rule: an `alerts:` or `rules:` entry under `packages/queries/`, its severity, capabilities (`requires`) or default-set membership (`enabledByDefault`), the…

Use this skill when working with Materialize's alloy log-processing or metric-processing pipelines — anything under `packages/alloy-pipelines/`. Triggers include: building, modifying, reviewing, or rendering pipelines; working with the embedded JSONSchemas…

This skill should be used when changing the Terraform modules under `terraform/`, the E2E test tiers under `test/e2e/`, or the CI that gates them — and when a chart change has consequences for either. Covers how the module and the chart are coupled, what each…

This skill should be used when reviewing a pull request or diff. Catches renames and removals on the customer-facing surface that owe a deprecation cycle, and says what is not a breakage.

Contributing to the Materialize Terraform provider codebase. Covers the project layout (pkg/materialize, pkg/resources, pkg/datasources, pkg/provider), the builder pattern for SQL generation, adding new resources and data sources end to end, the acceptance…

Bump the mz-deploy Homebrew formula (Formula/mz-deploy.rb) to a new release version — updates the version field and recomputes every platform's sha256 checksum from the published tarballs. Use this whenever the user wants to release, bump, update, or upgrade…