I'll help you design a database schema. Let me understand your needs:

**About Your App:**
1. What does your app do? (one sentence)
2. What are the main "things" users will create/manage? (e.g., posts, products, orders)
3. Do you need user authentication? (yes/no)
4. Is this multi-tenant (multiple organizations)? (yes/no)
5. What database? (Supabase/PostgreSQL/MySQL, default: Supabase)

**Preferences:**
6. Include soft deletes (deleted_at column)? (yes/no, default: yes)
7. Include audit fields (created_at, updated_at, created_by)? (yes/no, default: yes)
8. Generate RLS policies? (yes/no, default: yes if Supabase)

Once you answer, I will:
- Design tables with proper relationships
- Add appropriate indexes
- Create foreign key constraints
- Generate migration SQL
- Add RLS policies for security
- Provide seed data for testing

Ready? Answer the questions above.

-- Organizations (tenants)
CREATE TABLE organizations (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  name TEXT NOT NULL,
  slug TEXT UNIQUE NOT NULL,
  created_at TIMESTAMPTZ DEFAULT now(),
  updated_at TIMESTAMPTZ DEFAULT now()
);

-- Projects
CREATE TABLE projects (
  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
  organization_id UUID REFERENCES organizations(id) ON DELETE CASCADE,
  name TEXT NOT NULL,
  description TEXT,
  status TEXT DEFAULT 'active',
  created_at TIMESTAMPTZ DEFAULT now(),
  updated_at TIMESTAMPTZ DEFAULT now(),
  deleted_at TIMESTAMPTZ
);

-- And so on for tasks, comments, with full RLS policies...

Also include tables for: file attachments, activity logs, and notifications.

Generate this for MySQL instead, with appropriate syntax changes.