diff --git a/ai-docs/AGENTS.md b/ai-docs/AGENTS.md
new file mode 100644
index 000000000..6f3aadb3c
--- /dev/null
+++ b/ai-docs/AGENTS.md
@@ -0,0 +1,566 @@
+# Contact Center Widgets - AI Agent Guide
+
+## Purpose
+
+This is the main orchestrator for AI assistants working on this repository. It routes you to the correct templates and documentation based on the developer's task.
+
+---
+
+## Quick Start
+
+**When developer provides a task, follow this workflow:**
+
+1. **Understand the task** - Identify what type of work is needed
+2. **Route to appropriate template** - Use modular templates for guidance
+3. **Generate/fix code** - Follow established patterns
+4. **Update documentation** - Keep ai-docs in sync with code changes
+5. **Ask for review** - Confirm completion with developer
+
+---
+
+## Step 1: Identify Task Type
+
+**Ask developer:** "What do you need help with?"
+
+### Task Types
+
+**A. Create New Widget**
+- Developer wants to build a completely new widget from scratch
+- **Route to:** [templates/new-widget/00-master.md](./templates/new-widget/00-master.md)
+- **Follow:** All 7 modules (pre-questions → validation)
+- **⚠️ MANDATORY FIRST STEP:** Collect design input (see below)
+
+**B. Fix Bug in Existing Widget**
+- Developer reports a bug or issue in existing code
+- **Route to:** [templates/existing-widget/bug-fix.md](./templates/existing-widget/bug-fix.md)
+- **Follow:** Bug fix workflow with root cause analysis
+
+**C. Add Feature to Existing Widget**
+- Developer wants to enhance existing widget with new functionality
+- **Route to:** [templates/existing-widget/feature-enhancement.md](./templates/existing-widget/feature-enhancement.md)
+- **Follow:** Feature addition workflow with backward compatibility
+
+**D. Generate/Update Documentation Only**
+- Developer needs documentation for existing code
+- **Route to:** [templates/documentation/create-agent-md.md](./templates/documentation/create-agent-md.md) and [templates/documentation/create-architecture-md.md](./templates/documentation/create-architecture-md.md)
+- **Follow:** Documentation templates (reusable for all packages)
+
+**E. Understanding Architecture**
+- Developer needs to understand how something works
+- **Read:** Package's `ai-docs/AGENTS.md` (usage) and `ai-docs/ARCHITECTURE.md` (technical details)
+- **Available for:** station-login, user-state, store, cc-components, cc-widgets, ui-logging, test-fixtures
+
+---
+
+## ⚠️ CRITICAL RULES - Always Follow
+
+### 1. Circular Dependency Prevention
+
+**NEVER create these imports:**
+
+```typescript
+// ❌ WRONG - Circular dependencies
+import { Widget } from '@webex/cc-widgets';      // In widget package code
+import { Widget } from '@webex/cc-widget-name';  // In cc-components code
+```
+
+**ALWAYS use this pattern:**
+
+```typescript
+// ✅ CORRECT - Proper dependency flow
+// In widget code:
+import { Component } from '@webex/cc-components';
+import store from '@webex/cc-store';
+import { withMetrics } from '@webex/cc-ui-logging';
+
+// In cc-widgets aggregator (ONLY):
+import { Widget } from '@webex/cc-widget-name';
+```
+
+**Dependency Flow (One Direction Only):**
+
+```
+cc-widgets → widget packages → cc-components → store → SDK
+```
+
+**Validation Before Code Generation:**
+
+- [ ] Widget does NOT import from `@webex/cc-widgets`
+- [ ] cc-components does NOT import from any widget packages
+- [ ] All imports follow one-directional flow
+- [ ] No circular references between packages
+
+**If circular dependency is detected → STOP and refactor imports immediately.**
+
+### 2. Mandatory Design Input (For New Widgets)
+
+**STOP! Before generating ANY new widget code, collect design input.**
+
+#### Required Input (ONE of these):
+
+1. **Figma Link/File**
+   - Share Figma link or file
+   - LLM will extract design tokens, components, interactions
+
+2. **Screenshot/Mockup**
+   - Upload image of desired widget UI
+   - LLM will analyze colors, layout, components, spacing
+
+3. **Design Specification**
+   - Provide detailed specs:
+     - Colors (hex/RGB or Momentum tokens)
+     - Layout structure (flex/grid)
+     - Components needed (Button, Icon, Avatar, etc.)
+     - Typography (sizes, weights)
+     - Interactions (hover, click states)
+
+#### If Design Input Provided:
+
+**Analyze and document:**
+- **Colors:** Extract hex/RGB values or Momentum tokens
+- **Components:** Identify Momentum UI components to use
+- **Layout:** Grid, flex, spacing patterns (8px/0.5rem grid)
+- **Typography:** Sizes, weights (Momentum typography scale)
+- **Interactions:** Buttons, hover states, transitions
+
+#### If NO Design Input:
+
+**ASK THE USER:**
+
+```
+⚠️ Design Input Required
+
+I cannot generate a widget without visual design reference. This ensures:
+- UI matches your design system
+- Correct Momentum components are used
+- Proper styling and theming
+
+Please provide ONE of:
+1. Figma link/file
+2. Screenshot of desired UI
+3. Detailed design specification (colors, layout, components)
+
+Once provided, I'll analyze it and generate the widget accordingly.
+```
+
+**DO NOT proceed without design input.**
+
+---
+
+## Step 2: Load Context
+
+**Before generating code, load appropriate context:**
+
+### Always Read (Minimal Context)
+1. **Pattern documentation** - [patterns/](./patterns/) folder
+   - [typescript-patterns.md](./patterns/typescript-patterns.md) - Type safety, naming conventions
+   - [react-patterns.md](./patterns/react-patterns.md) - Component patterns, hooks
+   - [mobx-patterns.md](./patterns/mobx-patterns.md) - State management with observer HOC
+   - [web-component-patterns.md](./patterns/web-component-patterns.md) - r2wc patterns
+   - [testing-patterns.md](./patterns/testing-patterns.md) - Jest, RTL, Playwright
+
+2. **Package documentation** - If working on existing widget
+   - `packages/contact-center/{widget-name}/ai-docs/AGENTS.md` - Usage and API
+   - `packages/contact-center/{widget-name}/ai-docs/ARCHITECTURE.md` - Technical details
+
+### Conditionally Read
+
+**If using SDK APIs:**
+- Scan: [contact-centre-sdk-apis/contact-center.json](./contact-centre-sdk-apis/contact-center.json)
+- Find available methods, events, types
+- Check method signatures before using
+
+**If modifying store:**
+- Read: `packages/contact-center/store/ai-docs/AGENTS.md`
+- Read: `packages/contact-center/store/ai-docs/ARCHITECTURE.md`
+
+**If creating/using components:**
+- Read: `packages/contact-center/cc-components/ai-docs/AGENTS.md`
+
+**If working with metrics/logging:**
+- Read: `packages/contact-center/ui-logging/ai-docs/AGENTS.md`
+
+---
+
+## Step 3: SDK API Consultation (Before Code Generation)
+
+**Before using ANY SDK method, consult the SDK knowledge base.**
+
+### Process
+
+#### 1. Identify Required SDK Functionality
+
+Based on widget requirements, list needed operations:
+- Making calls? → Search: "call", "dial", "telephony", "outdial"
+- Fetching agents? → Search: "agent", "buddy", "team"
+- Managing tasks? → Search: "task", "interaction", "contact"
+- Checking state? → Search: "state", "status", "presence"
+
+#### 2. Search SDK Knowledge Base
+
+**File:** [contact-centre-sdk-apis/contact-center.json](./contact-centre-sdk-apis/contact-center.json)
+
+**Search Strategy:**
+- Use keyword search in JSON
+- Look for method names, descriptions
+- Check similar/related methods
+
+#### 3. Verify API Signature
+
+For each method found, confirm:
+- ✅ Method name (exact spelling)
+- ✅ Parameters (names, types, required vs optional)
+- ✅ Return type
+- ✅ Error conditions
+- ✅ Usage notes
+
+#### 4. Use Correct Access Pattern
+
+```typescript
+// ✅ CORRECT - Via store
+await store.cc.methodName(params);
+
+// ❌ WRONG - Direct SDK import
+import sdk from '@webex/contact-center';
+await sdk.methodName(params);
+```
+
+#### 5. Add Error Handling
+
+```typescript
+try {
+  const result = await store.cc.methodName(params);
+  // Handle success
+  props.onSuccess?.(result);
+} catch (error) {
+  console.error('SDK error:', error);
+  props.onError?.(error);
+}
+```
+
+### Example: OutdialCall Widget
+
+**Requirement:** Make outbound call
+
+**SDK Search:** "outdial", "call", "dial"
+
+**Found:** `startOutdial(destination: string, origin: string)`
+
+**Usage:**
+
+```typescript
+const handleDial = async (phoneNumber: string) => {
+  try {
+    await store.cc.startOutdial(phoneNumber, 'WidgetName');
+    props.onDial?.(phoneNumber);
+  } catch (error) {
+    console.error('Outdial failed:', error);
+    props.onError?.(error);
+  }
+};
+```
+
+### Common SDK Operations
+
+- **Agent State:** `store.cc.setAgentState(state, reasonCode)`
+- **Task Accept:** `task.accept()`
+- **Task Hold:** `task.hold()`
+- **Task End:** `task.end()`
+- **Events:** `store.cc.on('eventName', handler)`
+
+---
+
+## Step 4: Architecture Pattern
+
+**All code must follow this pattern:**
+
+```
+Widget (observer HOC)
+  ↓
+Custom Hook (business logic)
+  ↓
+Presentational Component (pure UI)
+  ↓
+Store (MobX singleton)
+  ↓
+SDK (Contact Center API)
+```
+
+**Key Rules:**
+- Widget NEVER calls SDK directly (use hook)
+- Component NEVER accesses store (receives props)
+- Always use `observer` HOC for widgets
+- Always use `runInAction` for store mutations
+- Always wrap with ErrorBoundary
+- Always apply withMetrics HOC for exports
+
+---
+
+## Step 5: Generate/Fix Code
+
+**Follow the template you were routed to in Step 1**
+
+**During code generation:**
+1. Follow pattern documentation strictly
+2. Reference existing widgets for examples
+3. Use proper TypeScript types (no `any`)
+4. Include error handling
+5. Add loading/error states
+6. Write tests alongside code
+
+---
+
+## Step 5.5: Functionality Validation (CRITICAL)
+
+**After generating code, VERIFY functionality layer by layer.**
+
+### Validation Checklist
+
+#### 1. SDK Integration ✓
+
+- [ ] SDK methods exist in [contact-centre-sdk-apis/contact-center.json](./contact-centre-sdk-apis/contact-center.json)
+- [ ] Parameters match SDK signature exactly
+- [ ] Accessed via `store.cc.methodName()` (not direct import)
+- [ ] Error handling present (try/catch)
+- [ ] Success callbacks fire
+- [ ] Error callbacks fire
+
+**If method not found or signature mismatch → FIX before proceeding**
+
+#### 2. Store Integration ✓
+
+- [ ] Observable data accessed correctly
+- [ ] `runInAction` used for mutations
+- [ ] No direct store property assignments
+- [ ] Store subscriptions cleaned up (useEffect return)
+
+#### 3. Event Flow ✓
+
+**Trace each user interaction:**
+
+1. User action (click, input) → Event handler called?
+2. Handler → State update triggered?
+3. State update → Re-render triggered?
+4. Re-render → UI updated correctly?
+
+**If ANY step fails → Debug and fix**
+
+#### 4. Data Flow ✓
+
+**Trace data through ALL layers:**
+
+```
+User Action (UI)
+  ↓
+Widget Handler (index.tsx)
+  ↓
+Hook Method (helper.ts)
+  ↓
+Store/SDK Call
+  ↓
+Response/Observable Update
+  ↓
+Hook State Update
+  ↓
+Component Props
+  ↓
+UI Render
+```
+
+**Verify each transition is correct.**
+
+#### 5. UI Visual Validation ✓
+
+**Compare with design input:**
+
+- [ ] Colors match (or use Momentum tokens)
+- [ ] Spacing matches (8px/0.5rem grid)
+- [ ] Components match design
+- [ ] Layout matches (flex/grid structure)
+- [ ] Typography matches (sizes, weights)
+- [ ] Interactions work (hover, click, etc.)
+
+**If visual doesn't match → Update styling**
+
+#### 6. Import Validation ✓
+
+**Check for circular dependencies:**
+
+```bash
+# In widget code, search for:
+grep -r "from '@webex/cc-widgets'" src/
+# Should return: NO MATCHES
+
+# In cc-components, search for:
+grep -r "from '@webex/cc-.*-widget'" packages/contact-center/cc-components/src/
+# Should return: NO MATCHES
+```
+
+**If any matches found → Refactor imports**
+
+#### 7. Compiler Test ✓
+
+```bash
+yarn build
+# Expected: NO ERRORS
+```
+
+**Common errors:**
+- Missing types → Add type definitions
+- Import errors → Check paths and exports
+- Circular dependencies → Refactor imports
+- Syntax errors → Fix code
+
+**Fix ALL compiler errors before completing.**
+
+---
+
+## Step 6: Update Documentation
+
+**CRITICAL: After any code change, check if documentation needs updates**
+
+**Ask developer:** "The code changes are complete. Do I need to update any documentation?"
+
+### Documentation to Consider
+
+**If new widget created:**
+- Generated via templates (AGENTS.md + ARCHITECTURE.md)
+
+**If widget modified:**
+- Update: `packages/contact-center/{widget-name}/ai-docs/AGENTS.md` (if API changed)
+- Update: `packages/contact-center/{widget-name}/ai-docs/ARCHITECTURE.md` (if architecture changed)
+- Add: New examples to AGENTS.md (if new use cases)
+- Update: Troubleshooting in ARCHITECTURE.md (if new issues discovered)
+
+**If store modified:**
+- Update: `packages/contact-center/store/ai-docs/AGENTS.md`
+- Update: `packages/contact-center/store/ai-docs/ARCHITECTURE.md`
+
+**If component library modified:**
+- Update: `packages/contact-center/cc-components/ai-docs/AGENTS.md`
+
+**If new pattern established:**
+- Update: Relevant pattern file in [patterns/](./patterns/)
+
+**If architecture changed:**
+- Update: Relevant architecture documentation as needed
+
+---
+
+## Step 7: Validation & Review
+
+**Before marking task complete:**
+
+1. **Run validation checks**
+   - Tests pass: `yarn test:unit`
+   - Linting passes: `yarn test:styles`
+   - Build succeeds: `yarn build`
+
+2. **Code quality checks**
+   - Follows patterns
+   - No layer violations
+   - Error handling present
+   - Types are correct
+
+3. **Documentation checks**
+   - AGENTS.md updated if needed
+   - ARCHITECTURE.md updated if needed
+   - Examples work
+
+4. **Ask developer for review:**
+   - "Task complete. Would you like to review the changes?"
+   - "Should I make any adjustments?"
+   - "Is the documentation clear?"
+
+---
+
+## Repository Structure
+
+```
+ccWidgets/
+├── packages/contact-center/
+│   ├── station-login/          # Widget with ai-docs/
+│   ├── user-state/             # Widget with ai-docs/
+│   ├── task/                   # Widget package
+│   ├── store/                  # MobX store with ai-docs/
+│   ├── cc-components/          # React components with ai-docs/
+│   ├── cc-widgets/             # Web Component wrappers with ai-docs/
+│   ├── ui-logging/             # Metrics utilities with ai-docs/
+│   └── test-fixtures/          # Test mocks with ai-docs/
+├── widgets-samples/
+│   └── cc/
+│       ├── samples-cc-react-app/       # React sample
+│       └── samples-cc-wc-app/          # Web Component sample
+├── playwright/                 # E2E tests
+└── ai-docs/
+    ├── AGENTS.md              # This file
+    ├── RULES.md               # Repository rules
+    ├── patterns/              # Repo-wide patterns
+    ├── templates/             # Code generation templates
+    └── contact-centre-sdk-apis/  # SDK API reference
+```
+
+---
+
+## Common Questions to Ask
+
+**Before starting any work:**
+- "What component/widget are you working on?"
+- "Is this a new widget, bug fix, or enhancement?"
+- "Do you have design specifications (Figma, screenshots)?"
+
+**During code generation:**
+- "Should I add/update tests?"
+- "Do you want examples in documentation?"
+- "Should I update the sample apps?"
+
+**After code generation:**
+- "The code is complete. Should I update documentation?"
+- "Would you like to review before I mark this complete?"
+- "Should I check for any other impacted components?"
+
+---
+
+## SDK Knowledge Base
+
+**Location:** [contact-centre-sdk-apis/contact-center.json](./contact-centre-sdk-apis/contact-center.json)
+
+**Contents:**
+- All exposed SDK APIs (methods, events, types)
+- Method signatures and parameters
+- Event names and data structures
+- Links to SDK source code (next branch)
+
+**Usage:**
+- Scan JSON when using SDK methods
+- Search for API by name or functionality
+- Check parameter types and return values
+- Verify event names before subscribing
+
+**Note:** This JSON is TypeDoc output from @webex/contact-center SDK
+
+---
+
+## Success Criteria
+
+**Code generation/fix is successful when:**
+- ✅ Follows architecture pattern (Widget → Hook → Component → Store → SDK)
+- ✅ Uses patterns correctly (TypeScript, React, MobX, WC)
+- ✅ Includes proper error handling
+- ✅ Has tests with good coverage
+- ✅ Documentation is updated (if code changed)
+- ✅ Works in both sample apps (React + WC)
+- ✅ No console errors or warnings
+- ✅ Passes validation checks
+- ✅ Developer approves changes
+
+---
+
+## Related Documentation
+
+- **Repository Rules:** [RULES.md](./RULES.md)
+- **Templates Overview:** [templates/README.md](./templates/README.md)
+
+---
+
+_Last Updated: 2025-11-26_
diff --git a/ai-docs/README.md b/ai-docs/README.md
new file mode 100644
index 000000000..e2aa8d3bc
--- /dev/null
+++ b/ai-docs/README.md
@@ -0,0 +1,196 @@
+# Contact Center Widgets
+
+Monorepo for Webex Contact Center UI widgets built with React, MobX, and Web Components.
+
+---
+
+## Overview
+
+```json
+{
+  "name": "@webex/contact-center-widgets",
+  "type": "Yarn Workspace Monorepo",
+  "purpose": "Contact center UI widgets for Webex"
+}
+```
+
+---
+
+## Technologies
+
+- **TypeScript** - Type-safe development ([tsconfig.json](../tsconfig.json))
+- **React 18** - Functional components with hooks
+- **MobX** - Centralized state management (singleton pattern)
+- **Web Components** - Framework-agnostic consumption via r2wc
+- **Testing** - Jest (unit) + Playwright (E2E)
+- **Build** - Webpack + Babel
+
+---
+
+## Components
+
+### Active Widgets
+
+**station-login** - Agent login with team and device selection
+- Location: `packages/contact-center/station-login/`
+- Docs: [ai-docs/](../packages/contact-center/station-login/ai-docs/)
+
+**user-state** - Agent state management with timer and idle codes
+- Location: `packages/contact-center/user-state/`
+- Docs: [ai-docs/](../packages/contact-center/user-state/ai-docs/)
+
+### Shared Packages
+
+**store** - Centralized MobX state (singleton)
+- Location: `packages/contact-center/store/`
+- Docs: [ai-docs/](../packages/contact-center/store/ai-docs/)
+
+**cc-components** - React UI primitives
+- Location: `packages/contact-center/cc-components/`
+
+**cc-widgets** - Web Component wrappers
+- Location: `packages/contact-center/cc-widgets/`
+
+### Future Widgets
+
+<!-- TODO: Task widgets (IncomingTask, TaskList, CallControl, CallControlCAD, OutdialCall) -->
+
+---
+
+## Component Dependencies
+
+```plantuml
+@startuml
+!define COMPONENT_BG #E3F2FD
+!define STORE_BG #FFF3E0
+
+component "station-login" COMPONENT_BG
+component "user-state" COMPONENT_BG
+component "task widgets" COMPONENT_BG #F5F5F5
+
+component "store\n(Singleton)" STORE_BG
+component "cc-components" COMPONENT_BG
+component "cc-widgets" COMPONENT_BG
+
+"station-login" --> store : uses
+"station-login" --> "cc-components" : uses
+"user-state" --> store : uses
+"user-state" --> "cc-components" : uses
+"task widgets" ..> store : uses
+"task widgets" ..> "cc-components" : uses
+
+"cc-widgets" --> "station-login" : wraps
+"cc-widgets" --> "user-state" : wraps
+"cc-widgets" ..> "task widgets" : wraps
+
+note right of store
+  MobX singleton
+  Store.getInstance()
+end note
+
+note right of "cc-widgets"
+  r2wc wrappers
+  Custom elements
+end note
+
+@enduml
+```
+
+**Pattern:** Widget → Hook → Component → Store
+
+---
+
+## Build Commands
+
+```bash
+# Install dependencies
+yarn install
+
+# Build all packages
+yarn build
+
+# Build specific package
+yarn workspace @webex/cc-station-login build
+
+# Watch mode
+yarn workspace @webex/cc-station-login build:watch
+```
+
+---
+
+## Test Commands
+
+```bash
+# Run all tests
+yarn test
+
+# Run specific package tests
+yarn workspace @webex/cc-station-login test
+
+# Run E2E tests
+yarn test:e2e
+
+# Run specific E2E suite
+npx playwright test suites/station-login-user-state-tests.spec.ts
+```
+
+---
+
+## Development Workflow
+
+1. **Choose component** to work on
+2. **Read component docs** in `packages/*/ai-docs/`
+3. **Follow repo patterns** in `ai-docs/patterns/`
+4. **Make changes** following component `RULES.md`
+5. **Write tests** (unit + E2E)
+6. **Build and verify**
+
+---
+
+## Architecture Overview
+
+**Three-Layer Pattern:**
+```
+Widget (Observer) → Custom Hook (Business Logic) → Component (UI) → Store (State)
+```
+
+**Key Patterns:**
+- **Singleton Store** - `Store.getInstance()` for centralized state
+- **Observer Components** - `observer()` HOC for MobX reactivity
+- **Custom Hooks** - Business logic encapsulation (e.g., `useStationLogin`)
+- **Error Boundaries** - All widgets wrapped with error handling
+- **Web Components** - r2wc for framework-agnostic consumption
+
+**For detailed architecture, see:**
+- [Store Documentation](../packages/contact-center/store/ai-docs/)
+
+---
+
+## Documentation Structure
+
+**Repository Patterns:**
+- `ai-docs/patterns/` - TypeScript, MobX, React, Web Components, Testing patterns
+
+**Component Documentation:**
+- `packages/*/ai-docs/README.md` - API and usage
+- `packages/*/ai-docs/OVERVIEW.md` - Architecture and design
+- `packages/*/ai-docs/EXAMPLES.md` - Code examples
+- `packages/*/ai-docs/RULES.md` - Component conventions
+- `packages/*/ai-docs/diagrams/` - Visual flows
+
+## For AI Assistants
+
+See [AGENTS.md](./AGENTS.md) for AI navigation guidance, task-based workflows, and best practices.
+
+---
+
+## Links
+
+- **Repository Rules:** [RULES.md](./RULES.md)
+- **Root Package:** [package.json](../package.json)
+- **TypeScript Config:** [tsconfig.json](../tsconfig.json)
+- **Playwright Config:** [playwright.config.ts](../playwright.config.ts)
+
+---
+
+_Last Updated: 2025-11-23_
diff --git a/ai-docs/RULES.md b/ai-docs/RULES.md
new file mode 100644
index 000000000..eb09c01c6
--- /dev/null
+++ b/ai-docs/RULES.md
@@ -0,0 +1,54 @@
+# Repository Rules & Design Patterns
+
+## Architectural principles
+
+- Clear layering: Widgets → UI components (`cc-components`) → Store (MobX) → SDK/backends (where applicable).
+- Web Components are thin wrappers over React widgets via r2wc.
+
+## Naming & structure
+
+- Mirror code structure in docs under `ai-docs/`.
+- Keep widget folders self-contained with `agent.md`, `architecture.md`, `README.md`.
+
+## Components & APIs
+
+- Strongly typed props and public surfaces (`index.ts` per package/widget).
+- Co-locate types with components (e.g., `*.types.ts`).
+
+## Error handling
+
+- Surface user-friendly errors in UI; avoid swallowing exceptions. <!-- TODO: add error boundary patterns if present -->
+
+## Accessibility & i18n
+
+- Ensure keyboard and screen-reader support in components. <!-- TODO: confirm a11y utilities -->
+
+## Styling & theming
+
+- Keep component styles modular (`.scss` or `.css` in component folders). <!-- TODO: document design tokens if any -->
+
+## Performance budgets
+
+- Prefer memoization for derived values; avoid unnecessary re-renders; batch updates with MobX where needed.
+
+## Security
+
+- Do not log PII or credentials. Sanitize user-provided inputs.
+
+## Observability
+
+- Use `ui-logging` helpers (`withMetrics`, `metricsLogger`) for metrics and logs.
+
+## Testing standards
+
+- Unit/component tests per package under `tests/`.
+- E2E tests in `playwright/` with suites and helpers.
+
+## Review & contribution
+
+- Follow patterns in `ai-docs/patterns/*.md`.
+- Keep docs in sync when APIs change.
+
+<!-- TODOs -->
+
+