mysql-lamp-legacy

Enforce modern MySQL/MariaDB schema standards in legacy LAMP stacks.

2|1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/sraloff/gravityboots --skill mysql-lamp-legacy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mysql-lamp-legacy
Source: https://github.com/sraloff/gravityboots/tree/main/.agent/skills/mysql-lamp-legacy
Command: npx skills add https://github.com/sraloff/gravityboots --skill mysql-lamp-legacy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy LAMP projects often face MySQL/MariaDB schema drift, fragile quoting, and compatibility quirks that slow development and risk data integrity.

Core Features & Use Cases

  • Schema hygiene: enforce InnoDB usage, utf8mb4 encodings, and strict date handling.
  • Schema migrations: maintain consistent identifiers with proper quoting and case handling across environments.
  • Operational guidance: provides best practices for indexes, foreign keys, and performance tuning in legacy apps.

Quick Start

Run the MySQL-LAMP Legacy skill to guide you through checking and aligning your legacy MySQL schemas with modern standards.

Frequently Asked Questions about mysql-lamp-legacy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a legacy MySQL schema to use InnoDB and utf8mb4?

Migrate a legacy MySQL schema to InnoDB and utf8mb4 by enforcing modern best practices for engine choices and character encodings. This skill provides actionable steps to align your database with strict data integrity standards.

What causes schema drift in legacy LAMP stack databases?

Schema drift in legacy LAMP databases occurs due to fragile quoting, compatibility quirks, and inconsistent environments. This skill solves these challenges by imposing constraints and ensuring proper identifier quoting across development and production.

Can I use this schema maintenance guidance for WordPress and Drupal?

Yes, you can apply this schema maintenance guidance to WordPress, Drupal, or custom PHP apps. It supports LAMP stacks across development and production environments to enforce consistent database standards.

What is the best way to handle foreign keys in legacy MariaDB databases?

The best way to handle foreign keys in legacy MariaDB databases is by following operational guidance for indexes and performance tuning. This ensures safe migrations and proper constraint enforcement within your existing LAMP stack.

Why does strict date handling fail in my legacy MySQL database?

Strict date handling fails in legacy MySQL databases due to outdated schema configurations and compatibility quirks. This skill solves the problem by enforcing modern strict date standards and providing actionable alignment steps.