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.
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
- Start with
database-design-engineering for model, integrity, tenancy, migration, and access-pattern framing.
- 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.
- Pair with
mysql-operations for administration, performance, backup, restore, or incident work.
Quality Standards
- Make storage engine, character set, collation, key, and transaction assumptions explicit.
- Prefer integrity in schema constraints and transactional boundaries before application-only enforcement.
- Include migration safety notes for locks, long-running changes, rollback, and data verification.
Anti-Patterns
- Treating absorbed reference files as active skills or separate routing entrypoints.
- Loading every migrated child reference instead of the one that matches the task.
- Producing generic advice without constraints, evidence, or next verification steps.
Outputs
- MySQL schema, SQL, migration, or review output with loaded references and validation evidence.
References
- Load only the references/.md files named in the workflow when their depth is required.
Inputs
| Input |
Required |
Purpose |
| MySQL version and schema |
yes |
Select valid features |
| Query shapes and cardinalities |
yes |
Design indexes |
| Migration and availability constraints |
yes |
Plan safe change |
Capability contract
Review SQL and propose DDL by default. Execute migrations, routines, or data changes only with authorised credentials, environment scope, backup evidence, and rollback.
Degraded mode
If EXPLAIN plans or production statistics are unavailable, provide read-only hypotheses and validation SQL; do not claim a query is tuned.
Decision rules
| Condition |
Action |
| Scan is selective and frequent |
Evaluate a covering index |
| DDL may lock a hot table |
Use an online or staged migration |
| Constraint encodes business truth |
Enforce it in the database |
Domain Anti-Patterns
- Using SELECT star in stable contracts. Fix: name columns.
- Building SQL by interpolation. Fix: bind parameters.
- Adding indexes without write-cost review. Fix: measure both paths.
- Using zero dates as missing values. Fix: use nullable semantics.
- Changing a hot table without lock analysis. Fix: test the DDL plan.
1---2name: mysql-engineering3description: Use when designing, implementing, or reviewing MySQL application schemas, SQL, indexes, constraints, stored routines, and production query patterns. Load absorbed MySQL best-practice, data-modeling, and advanced-SQL reference files as needed.4---56# MySQL Engineering7Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.89Use this parent skill as the active MySQL engineering entrypoint. It keeps routing narrow while preserving the older MySQL child skills as reference modules.1011<!-- dual-compat-start -->12## Use When1314- Designing MySQL-backed features, schemas, migrations, indexes, keys, and query paths.15- Reviewing MySQL SQL correctness, transaction behaviour, locking assumptions, or data modelling choices.16- Implementing stored routines, generated columns, JSON usage, or application data-access conventions.1718## Do Not Use When1920- The task is unrelated to this parent skill or is better handled by a narrower active parent named in the workflow.21- The request only needs a trivial answer and no reference module needs to be loaded.2223## Required Inputs2425- Gather the concrete system, repository, environment, constraints, and deliverable before loading references.26- Identify which absorbed reference file is needed; do not load every migrated reference by default.27## Workflow28291. Start with `database-design-engineering` for model, integrity, tenancy, migration, and access-pattern framing.302. Load only the needed reference:31 - `references/mysql-best-practices.md` for MySQL defaults, constraints, engine choices, and safe conventions.32 - `references/mysql-data-modeling.md` for schema and relationship design.33 - `references/mysql-advanced-sql.md` for advanced query and SQL patterns.343. Pair with `mysql-operations` for administration, performance, backup, restore, or incident work.3536## Quality Standards3738- Make storage engine, character set, collation, key, and transaction assumptions explicit.39- Prefer integrity in schema constraints and transactional boundaries before application-only enforcement.40- Include migration safety notes for locks, long-running changes, rollback, and data verification.4142## Anti-Patterns4344- Treating absorbed reference files as active skills or separate routing entrypoints.45- Loading every migrated child reference instead of the one that matches the task.46- Producing generic advice without constraints, evidence, or next verification steps.47## Outputs4849- MySQL schema, SQL, migration, or review output with loaded references and validation evidence.5051## References5253- Load only the references/<old-skill>.md files named in the workflow when their depth is required.54<!-- dual-compat-end -->5556## Inputs57| Input | Required | Purpose |58|---|---|---|59| MySQL version and schema | yes | Select valid features |60| Query shapes and cardinalities | yes | Design indexes |61| Migration and availability constraints | yes | Plan safe change |6263## Capability contract64Review SQL and propose DDL by default. Execute migrations, routines, or data changes only with authorised credentials, environment scope, backup evidence, and rollback.6566## Degraded mode67If EXPLAIN plans or production statistics are unavailable, provide read-only hypotheses and validation SQL; do not claim a query is tuned.6869## Decision rules70| Condition | Action |71|---|---|72| Scan is selective and frequent | Evaluate a covering index |73| DDL may lock a hot table | Use an online or staged migration |74| Constraint encodes business truth | Enforce it in the database |7576## Domain Anti-Patterns77- Using SELECT star in stable contracts. Fix: name columns.78- Building SQL by interpolation. Fix: bind parameters.79- Adding indexes without write-cost review. Fix: measure both paths.80- Using zero dates as missing values. Fix: use nullable semantics.81- Changing a hot table without lock analysis. Fix: test the DDL plan.
peterbamuhigire