docs(design): add two-accent system, selective mono, and dark mode decisions

Decisions from plan-design-review and plan-eng-review:
- Two-accent system: amber = state (nav, pills), blue = action (buttons)
- JetBrains Mono selective: codes/numbers only, text uses DM Sans
- Dark mode now in scope for Commit 0.5
- Add TODOS.md with deferred P2 items

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Claude Agent
2026-03-27 11:09:42 +00:00
parent 9f2fd24d93
commit c6d69ac0e0
2 changed files with 23 additions and 2 deletions

View File

@@ -42,14 +42,17 @@
| Label/uppercase | 12px | 500 | Display | Column headers, section labels (letter-spacing: 0.04em) |
| Body | 14px | 400 | Body | Paragraphs, descriptions |
| UI/Button | 13px | 500 | Body | Buttons, nav links, form labels |
| Data cell | 13px | 400 | Data | Table cells, order IDs |
| Data cell | 13px | 400 | Data | Codes, IDs, numbers, sums, dates (NOT text names — those use Body font) |
| Data small | 12px | 400 | Data | Timestamps, secondary data |
| Code/mono | 11px | 400 | Data | Inline code, debug info |
## Color
### Approach: Restrained with warm accent
### Approach: Two-accent system (amber state + blue action)
Every admin tool is blue. This one uses amber — reads as "operational" and "attention-worthy."
- **Amber (--accent):** Navigation active state, filter pill active, accent backgrounds. "Where you are."
- **Blue (--info):** Primary buttons, CTAs, actionable links. "What you can do."
- Primary buttons (`btn-primary`) stay blue for clear action hierarchy.
### Light Mode (default)
```css
@@ -316,3 +319,6 @@ Tables with 8+ columns and hundreds of rows need every pixel of width.
| 2026-03-27 | Warm tones throughout | Off-white (#F8F7F5) instead of clinical gray. Warm black text instead of blue-gray. Makes the tool feel handcrafted. |
| 2026-03-27 | Glowing status dots for errors | Problems glow (box-shadow), success is calm. Operator's eye is pulled to rows that need action. Inspired by subagent's "LED indicator" concept. |
| 2026-03-27 | Full mobile design | Bottom nav, card-based order views, touch-optimized gestures. Supports quick-glance usage from phone. |
| 2026-03-27 | Two-accent system | Blue = action (buttons, CTAs), amber = state (nav active, filter active). Clear hierarchy. |
| 2026-03-27 | JetBrains Mono selective | Mono font only for codes, IDs, numbers, sums, dates. Text names use DM Sans for readability. |
| 2026-03-27 | Dark mode in scope | CSS variables + toggle + localStorage. All DESIGN.md dark tokens implemented in Commit 0.5. |

15
TODOS.md Normal file
View File

@@ -0,0 +1,15 @@
# TODOS
## P2: Refactor sync_service.py in module separate
**What:** Split sync_service.py (870 linii) in: download_service, parse_service, sync_orchestrator.
**Why:** Faciliteza debugging si testare. Un bug in price sync nu ar trebui sa afecteze import flow.
**Effort:** M (human: ~1 sapt / CC: ~1-2h)
**Context:** Dupa implementarea planului Command Center (retry_service deja extras). sync_service face download + parse + validate + import + price sync + invoice check — prea multe responsabilitati.
**Depends on:** Finalizarea planului Command Center.
## P2: Email/webhook alert pe sync esuat
**What:** Cand sync-ul gaseste >5 erori sau esueaza complet, trimite un email/webhook.
**Why:** Post-lansare, cand app-ul ruleaza automat, nimeni nu sta sa verifice constant.
**Effort:** M (human: ~1 sapt / CC: ~1h)
**Context:** Depinde de infrastructura email/webhook disponibila la client. Implementare: SMTP simplu sau webhook URL configurabil in Settings.
**Depends on:** Lansare in productie + infrastructura email la client.