mariadb-agents-schema-reviewer

name	mariadb-agents-schema-reviewer
description	Use when reviewing a proposed MariaDB schema before it ships, auditing an existing schema for engine / indexing / naming / normalization problems, or validating a migration DDL. Prevents the common mistake of shipping a schema with MyISAM tables, UUID-text PKs, missing tenant indexes, utf8 charset, or composite indexes in the wrong column order. Covers a deterministic schema-review checklist : storage-engine choice, primary-key type, indexing strategy and column-order, charset / collation, normalization fitness, multi-tenant pattern detection, naming-convention adherence, with severity grading and cross-references to mariadb-core-storage-engines, mariadb-syntax-indexing, mariadb-impl-schema-design. Keywords: schema review, schema audit, review my schema, is this schema correct, schema checklist, design review, storage engine audit, index audit, primary key audit, normalization check, multi-tenant check, naming convention, DDL review, before I ship this schema, ENGINE=InnoDB, MyISAM, BIGINT AUTO_INCREMENT, UUID primary key, utf8mb4, ROW_FORMAT=DYNAMIC, composite index column order, leftmost-prefix, how do I review a schema, what is wrong with my schema, is my table design good, getting started with schema review
license	MIT
compatibility	Designed for Claude Code. Requires MariaDB 10.6-LTS, 10.11-LTS, 11.x, 12.x.
metadata	{"author":"OpenAEC-Foundation","version":"1.0"}

mariadb-agents-schema-reviewer

A deterministic procedure for reviewing a MariaDB schema (CREATE TABLE DDL, migration script, or existing schema dump) before it ships. This is an ORCHESTRATION skill : it does not teach syntax, it applies a fixed 10-dimension checklist and produces a graded findings report. Every check cites the canonical skill that explains the underlying rule.

Quick Reference

• Run ALL 10 review dimensions in order. Never skip a dimension because the schema "looks fine".
• Grade every finding with one of three severities : BLOCKER, WARNING, SUGGESTION.
• BLOCKER : the schema must not ship. Examples : MyISAM on a transactional table, a table with no PRIMARY KEY, FLOAT used for a money column.
• WARNING : the schema works but carries a known cost or footgun. Examples : CHAR(36) UUID-text PK on InnoDB, utf8 (utf8mb3) charset on text columns, a multi-tenant table with no leftmost tenant_id index.
• SUGGESTION : a stylistic or maintainability improvement. Examples : inconsistent naming case, oversized VARCHAR, TEXT where VARCHAR fits.
• Every finding cites the canonical skill that explains the rule. NEVER report a problem without a skill-ref.
• Output a single findings table : dimension, severity, location, problem, fix, skill-ref. Close with a verdict line.
• A clean schema still gets a report : the table has zero rows and the verdict is PASS.

The 10 Review Dimensions

#	Dimension	What it checks	Canonical skill
1	Storage engine	InnoDB for transactional tables ; flag MyISAM	mariadb-core-storage-engines
2	Primary key	every table has a PK ; flag UUID-text PK	mariadb-impl-schema-design
3	Indexing	composite column-order, redundant indexes, FK indexes	mariadb-syntax-indexing
4	Charset / collation	utf8mb4 on text columns ; flag utf8 / latin1	mariadb-errors-encoding-and-collation
5	Normalization	repeating groups, unjustified denormalization	mariadb-impl-schema-design
6	Multi-tenant	detect tenant_id ; flag missing leftmost tenant index