database-schema-designer

What This Skill Does

The database-schema-designer skill is a comprehensive architectural assistant for OpenClaw AI, specifically engineered to streamline the end-to-end database lifecycle. It excels at translating high-level functional requirements into normalized, production-ready relational database schemas. Beyond simple table creation, the tool automates the generation of complex infrastructure components, including ORM-specific migration scripts (Drizzle, Prisma, TypeORM, and Alembic), language-specific data models (TypeScript, Python), and database-level security protocols such as Row-Level Security (RLS) policies. It enforces best practices for enterprise-grade applications, including multi-tenancy architecture, soft-delete implementation, audit logging, and indexing strategies to ensure optimal query performance. By visualizing schema relationships via Mermaid diagrams, it provides both technical implementation details and conceptual clarity for backend teams.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal or command interface: clawhub install openclaw/skills/skills/alirezarezvani/database-schema-designer Ensure your local environment is configured to interact with the ClawHub registry.

Use Cases

• Rapid Prototyping: Quickly generate a full schema from a user story or product requirement document.
• Refactoring: Analyze existing legacy schemas and suggest normalization improvements or performance-enhancing composite indexes.
• Standardization: Ensure all team projects follow consistent patterns for soft deletes, audit trails, and optimistic locking.
• Full-Stack Bridging: Automatically generate TypeORM or Prisma definitions that match your SQL migrations, reducing the gap between database and application layers.
• Security Hardening: Implement organization-wide RLS policies for multi-tenant SaaS platforms to prevent data leakage between customers.

Example Prompts

1. "I am building a SaaS for fitness tracking. Generate a normalized PostgreSQL schema with multi-tenancy using an organization_id, add audit columns to every table, and include a Prisma migration schema."
2. "Review this schema for my task manager and suggest indexes for frequent lookups on the project_id and status columns, then write the SQL for a soft-delete policy."
3. "Design a database structure for a polymorphic notification system that can handle emails, SMS, and push notifications, including a Mermaid diagram of the entity relationships."

Tips & Limitations

• Normalization: Always provide context about the scale of data expected, as over-normalization can sometimes conflict with read-heavy performance requirements.
• Framework Choice: Specify your ORM early in the prompt to ensure the generated migration files align with your project's existing tech stack.
• Security: While the tool generates robust RLS templates, always audit generated policies against your application's actual authentication mechanism.
• Limitations: The skill assumes a relational model. It is not currently optimized for NoSQL document stores or graph databases.