mysql-engineering
/mysql-engineering
Pomaga projektować, wdrażać, administrować, strojić, archiwizować, monitorować i naprawiać schematy oraz produkcyjne systemy MySQL.
- Autor
- peterbamuhigire ↗
- Repozytorium
- chwezi-dev-engine ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 24.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 22
- Skrypty
- 0
- Komentarze HTML
- 2
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 24.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.
Co robi i kiedy
Pomaga projektować, wdrażać, administrować, strojić, archiwizować, monitorować i naprawiać schematy oraz produkcyjne systemy MySQL.
Oryginalny opis (EN)
Use when designing, implementing, administering, tuning, backing up, restoring, monitoring, or troubleshooting MySQL schemas and production systems; use database-reliability for datastore-independent SLO and recovery policy.
Jak działa
- Use When
- Do Not Use When
- Required Inputs
- Workflow
- Quality Standards
- Anti-Patterns
- Outputs
- References
- Evidence Produced
- Inputs
Podgląd SKILL.md
--- name: mysql-engineering description: Use when designing, implementing, administering, tuning, backing up, restoring, monitoring, or troubleshooting MySQL schemas and production systems; use database-reliability for datastore-independent SLO and recovery policy. metadata: portable: true compatible_with: - claude-code - codex --- # 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. Administration, performance, backup, restore, and incident work also route here (the retired `mysql-operations` skill is an inactive alias of this skill). ## 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 the retained [MySQL operations workflow](../mysql-operations/ALIAS.md) for backup, restore, replication, production tuning, monitoring, and incidents. - Load only the references/<old-skill>.md files named in the workflow when their depth is required. ## Evidence Produced | Category | Artifact | Format | Example | | --- | --- | --- | --- | | Data safety | MySQL schema and operations evidence pack | DDL, query plans, and runbook | constraints, migration, backup/restore, performance capture, and rollback | <!-- dual-compat-end --> ## 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.
Pliki w paczce (22)
- SKILL.md 4 KB
- references/mysql-advanced-sql.md 6 KB
- references/mysql-best-practices.md 6 KB
- references/mysql-data-modeling.md 14 KB
- references/mysql-advanced-sql/references/skill-deep-dive.md 12 KB
- references/mysql-best-practices/examples/saas-schema.sql 9 KB
- references/mysql-best-practices/references/advanced-sql-patterns.md 15 KB
- references/mysql-best-practices/references/backup-recovery.md 16 KB
- references/mysql-best-practices/references/benchmarking-tools.md 9 KB
- references/mysql-best-practices/references/database-security-hardening.md 15 KB
- references/mysql-best-practices/references/high-availability.md 16 KB
- references/mysql-best-practices/references/indexing-deep-dive.md 13 KB
- references/mysql-best-practices/references/mysql8-features.md 9 KB
- references/mysql-best-practices/references/partitioning.sql 9 KB
- references/mysql-best-practices/references/query-performance.md 15 KB
- references/mysql-best-practices/references/security-hardening.md 15 KB
- references/mysql-best-practices/references/server-tuning-mycnf.md 20 KB
- references/mysql-best-practices/references/skill-deep-dive.md 16 KB
- references/mysql-best-practices/references/stored-procedures.sql 7 KB
- references/mysql-best-practices/references/transaction-locking.md 14 KB
- references/mysql-best-practices/references/triggers.sql 7 KB
- references/mysql-data-modeling/references/growth-analytics-schema.md 5 KB
Wersje
W bazie nie ma innych skilli o nazwie mysql-engineering.
Migawka bazy z 13.11.2026 · wersja paczki e8f21af13ddf (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100postgresql-engineering
Wspiera projektowanie, wdrażanie, administrację, strojenie, kopie zapasowe, odtwarzanie, monitoring i diagnozę schematów oraz produkcyjnych systemów PostgreSQL. - 100database-reliability
Pomaga definiować SLO baz danych, budżety błędów, weryfikację kopii zapasowych, politykę pojemności, reagowanie na incydenty, game days oraz dyżury dla MySQL i PostgreSQL. - 100linux-postgresql
Pomaga instalować, zabezpieczać, stroić, archiwizować i odtwarzać PostgreSQL na Debianie, Ubuntu i RHEL, w tym pg_hba.conf, kopie logiczne, WAL i PITR. - 100mysql
Administruje bazami MySQL i MariaDB: konfiguracja replikacji i optymalizacja wydajności przy zarządzaniu wdrożeniami. - 100mysql
Administruje bazami MySQL i MariaDB: konfiguracja replikacji i optymalizacja wydajności przy zarządzaniu wdrożeniami. - 100mysql
Administruje bazami MySQL i MariaDB: konfiguracja replikacji i optymalizacja wydajności przy zarządzaniu wdrożeniami.