aiox-data-engineer

Design Supabase and PostgreSQL schemas with RLS policies and migration plans.

Updated May 25, 2026
One-click install
npx skills add https://github.com/FelipeMaines/ProjetoWeb --skill aiox-data-engineer-felipemaines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-data-engineer
Source: https://github.com/FelipeMaines/ProjetoWeb/tree/main/.claude/skills/AIOX/agents/data-engineer
Command: npx skills add https://github.com/FelipeMaines/ProjetoWeb --skill aiox-data-engineer-felipemaines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the challenge of designing and operating secure, performant database schemas without risking unsafe migrations, broken RLS rules, or inefficient queries.

Core Features & Use Cases

  • Database schema architecture: Model domains, define tables/relationships, and structure data foundations around access patterns.
  • Supabase/PostgreSQL security (RLS): Design and validate RLS policies with correctness focused on least-privilege behavior.
  • Safe operations & migrations: Create migration plans, apply changes with snapshots/rollback strategy, seed data idempotently, and run smoke tests.
  • Performance and observability: Analyze query performance, identify hot paths, and ensure schema/index choices match real usage.

Quick Start

Ask the AI to design your database schema and RLS policies for a Supabase project, then provide a safe migration plan with a snapshot and rollback approach.

Frequently Asked Questions about aiox-data-engineer

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

FAQPage Schema
How do I design secure database schemas with Supabase RLS policies?

Design secure database schemas by modeling domains and defining tables, then validate Supabase RLS policies to enforce least-privilege access and defense-in-depth security. This ensures data access patterns remain correct and restricted across your PostgreSQL architecture.

What is the best way to execute zero-downtime PostgreSQL schema migrations?

Execute zero-downtime PostgreSQL schema migrations by creating snapshot-first migration plans with rollback strategies. Apply changes using idempotent operations and run smoke tests to verify data integrity and prevent unsafe schema evolution.

How does query optimization work for production PostgreSQL databases?

Query optimization for production PostgreSQL databases works by analyzing query performance using explain/analyze-driven analysis. It identifies hot paths and ensures schema and indexing choices align with real usage to tune database performance effectively.

Can I use this database architecture approach for existing Supabase projects?

You can use this database architecture approach for existing Supabase projects to refactor data modeling and configure RLS validation. It applies snapshot-first safety and idempotent operations to ensure secure, performant schema evolution without breaking current workflows.

Why are my Supabase RLS rules not working as expected?

Supabase RLS rules may fail due to incorrectly configured least-privilege behavior or missing defense-in-depth security validation. Validate your RLS policies against actual access patterns and ensure schema relationships enforce correct data isolation.

When do I need snapshot-first safety for database schema migrations?

You need snapshot-first safety for database schema migrations when applying changes to production PostgreSQL systems. It enables rollback strategies and ensures zero-downtime schema evolution by verifying idempotent operations before full execution.