Add design and product documentation

DESIGN.md

@@ -0,0 +1,17 @@
+# Design — SignalDesk AI
+
+## Direction
+
+Confident B2B SaaS with a precise cobalt accent, strong product evidence, and restrained technical depth. Avoid generic gradient startup styling.
+
+## System
+
+- Reuse semantic Tailwind tokens and existing shadcn primitives.
+- Favor clear hierarchy, compact product screenshots, honest metrics, and one dominant action.
+- Use generous whitespace on marketing pages and denser rhythm only inside dashboard surfaces.
+- Motion explains state changes; respect reduced motion and avoid decorative looping effects.
+- Desktop and mobile must preserve the same content priority and keyboard-visible focus.
+
+## Intentional patterns
+
+Fine separator rules and cobalt side accents are allowed when they communicate grouping or status rather than decoration.

PRODUCT.md

@@ -0,0 +1,22 @@
+# Product — SignalDesk AI
+
+Status: approved baseline. Update through a reviewed diff when product intent changes.
+
+## Audience and job
+
+B2B support leaders need to understand incoming demand, automate repetitive resolution work, and prove service quality without hiding decisions behind AI.
+
+## Primary journeys
+
+1. Understand the product and its operational value from the launch page.
+2. Inspect a realistic support dashboard with queue, quality, automation, and escalation evidence.
+3. Request a demo with enough context for a useful sales handoff.
+
+## Non-goals
+
+- No fake live integrations, payments, or unsupported performance claims.
+- No consumer chatbot positioning.
+
+## Success criteria
+
+The value proposition is clear above the fold, dashboard examples remain credible, and every primary page leads naturally to a demo decision.