flux-schema

Design normalized database schemas with 3NF, constraints, and reversible migrations.

69|8|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/tonone-ai/tonone --skill flux-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flux-schema
Source: https://github.com/tonone-ai/tonone/tree/main/team/flux/skills/flux-schema
Command: npx skills add https://github.com/tonone-ai/tonone --skill flux-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and build database schemas that are properly normalized, scalable, and easy to migrate, reducing data anomalies and maintenance costs.

Core Features & Use Cases

  • Normalization to at least 3NF with clear entity relationships.
  • Enforced constraints, indexes, and audit timestamps (created_at, updated_at).
  • Guidance for migrations and schema evolution across Prisma, Alembic, Drizzle, or raw SQL workflows.

Quick Start

Describe your data entities and relationships, and ask Flux to design a normalized schema with migrations.

Frequently Asked Questions about flux-schema

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

FAQPage Schema
How do I design a normalized database schema to prevent data anomalies?

To design a normalized database schema, you enforce 3NF normalization with clear entity relationships, proper indexing, and NOT NULL constraints, which reduces data anomalies and maintenance costs.

What is the best way to manage database schema migrations across different frameworks?

Managing database migrations is best handled by generating reversible migration scripts, which ensures schema evolution across Prisma, Alembic, Drizzle, or raw SQL workflows without breaking data integrity.

Does this schema design approach work with analytics databases and transactional systems?

Yes, this schema design approach works for analytics databases and transactional systems, enforcing audit timestamps like created_at and updated_at to ensure reliable data models for any project scale.

How do I enforce data integrity constraints in a relational schema?

You enforce data integrity constraints in a relational schema by applying NOT NULL restrictions, proper indexes, and 3NF normalization rules to guarantee reliable data models and prevent update anomalies.

When do I need 3NF normalization for my database design?

You need 3NF normalization for your database design when your transactional system or analytics database requires robust entity relationships, strict constraints, and reversible migrations to maintain data integrity.