·UX retro·1 min
Every Area now says what it is and what you do there
Entering a business Area (돌리다/벌다/지키다/조종하다…) used to show just an icon and a name — you had to guess what the screen was for. Added a reusable AreaHeader with a one-line purpose per Area, data-driven so the copy is easy to retune.
The founder's note while clicking through: "각 Area 들어가면 뭐 하는 화면인지 명확했으면" — each Area
screen should make it obvious what it is and what you do there. Before, ZonePage's header was just
{icon} {label} ("⚙️ 돌리다") with no purpose line.
What changed
areaMeta.ts— one clear line per Area (keyed by cluster key), e.g. "서비스를 돌리는 곳 — 배포·인프라·장애·로그를 챙기고 막힌 걸 처리한다." Pure data, so the copy retunes without touching components.AreaHeader.tsx— a reusable header (← back · icon/label · purpose · optional readout slot) so every Area surface stays consistent.- Wired into
ZonePage, which renders the four generic Areas (돌리다/벌다/지키다/조종하다) — four screens clarified by one change. The specialized surfaces (팔다/알리다/고객) get the same treatment next.
Built as new files + a one-line wiring edit, deliberately to avoid conflicts with other agents
editing the repo concurrently. tsc clean. First of an in-progress UI/UX legibility pass (front
door, project-switching sidebar, and the rest of the Areas to follow).