Personal Database Designer

This skill helps users design databases for personal-level projects. It balances simplicity with good design practices, ensuring the database is not over-engineered (avoiding complex enterprise structures) but is robust, normalized, and extensible.

Input

The user will provide:

1. A requirement description, project name, or design document.
2. The target database type (e.g., MySQL, PostgreSQL, SQLite). If not specified, ask or default to a common choice like MySQL or PostgreSQL based on context.

Workflow

1. Analyze Requirements (Implicit & Explicit):
   • If the user provides a detailed requirement, follow it.
   • If the user provides ONLY a project name or a simple sentence (e.g., "Defect Management System"), you MUST infer the core business entities and functional modules based on general domain knowledge.
   • Example: For "Defect Management System", infer tables like users, projects, defects (or issues), comments, attachments.
2. Design Database: Apply the Design Principles below.
3. Generate Output: Produce the Markdown document and SQL.