mysql-engineering

# MySQL Engineering Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178. Use this parent skill as the active MySQL engineering entrypoint. It keeps routing narrow while preserving the older MySQL child skills as reference modules. <!-- dual-compat-start --> ## Use When - Designing MySQL-backed features, schemas, migrations, indexes, keys, and query paths. - Reviewing MySQL SQL correctness, transaction behaviour, locking assumptions, or data modelling choices. - Implementing stored routines, generated columns, JSON usage, or application data-access conventions. ## Do Not Use When - The task is unrelated to this parent skill or is better handled by a narrower active parent named in the workflow. - The request only needs a trivial answer and no reference module needs to be loaded. ## Required Inputs - Gather the concrete system, repository, environment, constraints, and deliverable before loading references. - Identify which absorbed reference file is needed; do not load every migrated reference by default. ## Workflow 1. Start with `database-design-engineering` for model, integrity, tenancy, migration, and access-pattern framing. 2. Load only the needed reference: - `references/mysql-best-practices.md` for MySQL defaults, constraints, engine choices, and safe conventions. - `references/mysql-data-modeling.md` for schema and relationship design. - `references/mysql-advanced-sql.md` for advanced query and SQL patterns. 3. Pair with `mys...