docs: define functional discovery and concise copy

2026-06-11 02:46:09 +08:00
parent 47d3b1a6fe
commit 72e7ec0c0b
1 changed files with 26 additions and 0 deletions
@@ -41,6 +41,32 @@ Every design decision must pass these five product-level requirements:
   - Colors need semantic, emotional, accessibility, light/dark, and localization rationale.
   - Each route still needs one memorable product-specific visual or interaction idea; comfort is not permission to become generic.
 ### Functional Discoverability And Copy
 The Today screen is a compact daily workspace. It must reveal the complete core loop without presenting every feature at equal visual strength:
 1. Anchor: today's chosen task and edit action.
 2. Focus: duration, current timer state, and the single P0 action.
 3. Habits: completion count, up to two preview rows, add or view-all action.
 4. Reflect: today's reflection status and write/view action.
 Progress/history and data/privacy tools remain available through their own destinations; they do not compete with today's P0 task.
 Copy rules:
 - Prefer short noun headings: Anchor, Focus, Habits, Reflect.
 - Prefer precise state labels: Not started, 17:42 left, 1 of 3, Not written, Saved.
 - Prefer direct verbs: Edit, Start, Pause, Resume, Add, View all, Write.
 - Remove motivational filler, repeated descriptions, and text that merely explains an obvious icon or control.
 - A module normally contains one heading, one primary value/state, and one action. Supporting copy appears only for error, disabled, privacy, or irreversible decisions.
 Module rules:
 - Make module boundaries clear through spacing, section headers, alignment, dividers, or subtle surface tints.
 - Keep Focus visually dominant; Anchor provides context; Habits and Reflect are secondary; progress decoration is tertiary.
 - Never repeat the same task, timer value, or progress metric in multiple modules on one screen.
 - Show enough function to explain what the app can do, then use progressive disclosure for full lists, history, settings, and detailed input.
 ### Supporting Rules
 1. Coherence without genre constraints