irwebtools Database (optional)
This skill is optional. Load it when the outcome needs durable schema or migration work beyond what a thin Supabase path already covers.
When to use
- schema or migration changes are required;
- data constraints or RLS policies must be explicit in source control;
- developers need reproducible database artifacts for handoff.
When not to use
- mock-data UI work;
- no persistence is required for the preview;
- Supabase skill already covers the needed migrations — coordinate with
supabaseinstead of duplicating guidance.
Expectations
- Prefer source-controlled migrations over manual remote edits.
- Test migrations on an isolated database when available.
- Document rollback or follow-up risk for developers.
- Do not design a full enterprise data platform unless that is the asked outcome.
Standard resources
Use templates, references, and evaluations for scope and exit evidence.