database-designer

Design normalized database schemas and migration templates for CakePHP multi-tenant applications.

2|Updated Oct 19, 2025

Search Tags:#design #database #multi-tenant #migrations #schema #normalization #CakePHP

Ready to run

npx skills add https://github.com/masanao-ohba/claude-manifests --skill database-designer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database-designer
Source: https://github.com/masanao-ohba/claude-manifests/tree/main/skills/php-cakephp/database-designer
Command: npx skills add https://github.com/masanao-ohba/claude-manifests --skill database-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps design robust database schemas and migration workflows for PHP/CakePHP applications, including multi-tenant architectures, ensuring consistency and scalability.

Core Features & Use Cases

Schema and migration design tailored to CakePHP, including multi-tenant patterns.
Patterns for shared vs. per-tenant databases, and normalization best practices.
Migration skeletons and example tables for typical business domains.

Quick Start

Provide a project context (tenant model, data domains) and request a CakePHP migration plan with table definitions and sample migration skeletons.

Frequently Asked Questions about database-designer

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

FAQPage Schema

How do I design a multi-tenant database schema for a CakePHP application?▼

A multi-tenant database schema for CakePHP requires choosing between tenant isolation patterns like shared schemas or per-tenant databases. The design process involves applying 3NF normalization and generating migration skeletons using the CakePHP Migrations plugin.

What is the best way to structure CakePHP migrations for SaaS projects?▼

Structuring CakePHP migrations for SaaS projects involves creating migration templates that support your multi-tenant architecture. You generate migration skeletons with table definitions for typical business domains while maintaining 3NF normalization and tenant isolation.

When do I need per-tenant databases versus a shared database schema?▼

You need per-tenant databases versus a shared schema when your SaaS project requires stricter tenant isolation. Per-tenant databases offer stronger data boundaries, while shared schemas simplify maintenance across a single CakePHP codebase.

Can I use CakePHP migrations to enforce 3NF normalization across business domains?▼

Yes, you can use CakePHP migrations to enforce 3NF normalization by defining table structures that eliminate data redundancy. The design process provides example tables for typical business domains to guide schema normalization within your migration plan.

What context do I need to provide to generate a multi-tenant migration plan?▼

To generate a multi-tenant migration plan, you must provide your project context including the tenant model and data domains. This input allows the generation of a complete CakePHP migration plan with table definitions and sample migration skeletons.