# Primora Design Context

## Users
- Solo developers and small teams (2-10 people)
- Technical users who want managed database experience without vendor lock-in
- Self-hosters who value control and ownership
- Job: Easy database access, simple self-hosted managed alternative to native Postgres

## Brand Personality
- Powerful yet affordable (premium feel, accessible pricing)
- Minimal — no bloat, only what you need
- Self-hosted — sense of ownership and control
- Clean, simple, nice to look at
- Developer-first but approachable

## Aesthetic Direction
- **Visual tone**: Refined developer tool — think Linear, Appwrite, Vercel
- **References**: Appwrite (layout inspiration), Supabase (clean data UI), Neon (modern simplicity)
- **Anti-references**: Overly corporate dashboards, cluttered admin panels, "enterprise software" bloat
- **Theme**: Primarily dark mode with light mode support
- **Feel**: Like a precision tool — every pixel intentional, every interaction snappy

## Design Principles
1. **Information density without clutter** — show what matters, hide the rest
2. **Predictable patterns** — developers live in keyboard shortcuts and muscle memory
3. **Progressive disclosure** — simple by default, powerful when needed
4. **Performance is aesthetic** — fast interactions feel premium
5. **Self-hosted soul** — emphasize control, local-first feel, no cloud ambiguity

## Technical Constraints
- SolidJS + TypeScript
- Tailwind CSS
- Must work self-hosted (no external dependencies for core UI)
- Responsive down to tablet (developers rarely use mobile for admin)