## Design Context

### Users
oh-my-pr is for developers and engineering teams who want pull requests to keep moving without manually babysitting review comments, CI failures, merge conflicts, docs follow-ups, and release prep. They are comfortable with GitHub, local CLIs, tokens, logs, branches, and coding agents. They use the app as a local-first operator console to understand what automation is doing, decide where human judgment is needed, and get PRs closer to merge-ready.

### Brand Personality
The brand personality is autonomous, high-level dashboard, and extreme simplicity. The interface should feel calm, senior, and developer-native: confident enough to run background automation, transparent enough to earn trust, and simple enough that the main state of every PR is obvious at a glance.

### Aesthetic Direction
Design dark-first only. The product UI should stay dense, monochrome, terminal-adjacent, and operational: bordered panes, compact controls, small metadata labels, JetBrains Mono, low decoration, and restrained status color only where it clarifies state. Linear and Superhuman are the best references: fast, focused, refined, and quiet. Avoid the enterprise-software feel of Jira, Confluence, Microsoft Teams, and ServiceNow: no heavy chrome, cluttered navigation, noisy cards, corporate gradients, or committee-designed settings surfaces.

Accessibility is not a design driver for now beyond preserving the existing baseline of readable contrast and keyboard-usable controls where practical.

### Design Principles
1. Make automation visible. Show what the agent is doing, why it is doing it, and what state each PR or feedback item is in.
2. Keep the interface high-level first. Prioritize scan-friendly dashboards, clear lifecycle state, and operator confidence over exhaustive configuration on the main surface.
3. Practice extreme simplicity. Add the smallest surface that solves the workflow, avoid speculative controls, and remove visual noise before adding polish.
4. Preserve the local developer-tool feel. Use compact density, mono typography, neutral tokens, sharp or minimal radius, and direct copy.
5. Use color sparingly for meaning. Reserve green, amber, red, and similar accents for status, warnings, and success signals; keep the rest neutral and dark-first.
