# Product

## Register

product

## Users

Developers and operators running OOMOL Connect locally. They use the console to inspect provider capabilities, configure credentials, run actions, and understand execution results without exposing raw provider secrets to agents.

## Product Purpose

OOMOL Connect is a local connector runtime for AI agents and SDK-style clients. The web console should make runtime state, provider actions, credential readiness, request schemas, examples, and run history easy to inspect and trust.

## Brand Personality

Clear, restrained, professional. The interface should feel like a dependable local developer tool: dense enough for repeated work, calm enough for debugging, and explicit about credentials and execution state.

## Anti-references

Avoid marketing-style hero layouts, decorative gradients, oversized cards, playful affordances, and hidden debugging state. Avoid dense controls that visually disconnect a selected detail from the action browser.

## Design Principles

- Put the task first: search, inspect, debug, and copy examples should be immediate.
- Keep execution state visible: local availability, auth requirement, scopes, and provider context should not be buried.
- Favor familiar controls: use standard product UI patterns for filters, tabs, forms, dialogs, and code examples.
- Preserve scanability: lists, panels, and metadata should stay aligned and predictable under large catalogs.
- Keep the local boundary explicit: the console should reinforce that actions run through the localhost runtime.

## Accessibility & Inclusion

Target WCAG AA contrast for text and controls. Preserve keyboard focus states, readable system fonts, reduced-motion behavior for animations, and responsive layouts that remain usable on narrow screens.
