Enforce database governance rules across Supabase projects.
npx skills add https://github.com/taikiwt/sitecue --skill database-rules
Please help me install this Agent Skill. Skill: Database Rules Source: https://github.com/taikiwt/sitecue/tree/main/.agent/skills/database Command: npx skills add https://github.com/taikiwt/sitecue --skill database-rules
This Skill enforces absolute rules for database governance across Supabase projects, preserving SSOT, improving change control, and strengthening data access policies.
Review the rules and align your project with SSOT, migration governance, and secure data access.
High-intent search queries and answers about installing and using this skill.
To enforce strict database rules for safe migrations in Supabase, you must require local testing and explicit migration files while forbidding direct edits to production schemas or data rules. This ensures controlled change management.
The single source of truth for database schema governance is the schema references and types themselves. Avoiding hard-coded values across code and migrations maintains consistent data management and absolute SSOT alignment.
To set up Row Level Security (RLS) policies for per-user data access in Supabase, enable RLS and apply explicit access control rules. This provides clear guidance for controlling secure per-user data handling workflows.
Yes, you can use these database governance rules for your product team's deployment workflow. They apply directly to developers, DBAs, and product teams during schema design, deployment, and data handling procedures.
You should not make direct edits to production database schemas because it breaks migration discipline. Requiring explicit migration files ensures safe migration procedures, preserving change control and strict data security compliance.
MakisuoInstall and configure a local ClickHouse environment with clickhousectl.
jonnabioAutomate database migrations, schema changes, and query optimization.
FlexNetOSExecute predefined test scenarios in CI/CD environments.
HainrixzAudit database access control, PII exposure, encryption, and SQL injection risks.
