kami
3d5e05c1fb
Threads reasoning_content across inference calls and journal renders, filters markdown noise out of L3 repo-knowledge retrieval, adds PlanLinter H3 checks, and tightens filesystem tool output/dir-listing behavior surfaced by prior live QA (see project_readloop_campaign memory).
22 lines
655 B
Markdown
22 lines
655 B
Markdown
# Web UI Design Specification
|
|
|
|
## Aesthetic
|
|
- **Theme**: Soft Rounded + Blue Accent.
|
|
- **Consistency**: Should align with the TUI layout plan.
|
|
|
|
## Layout
|
|
- **Sidebar**: Centralized navigation.
|
|
- **Main Area**: Dynamic content based on selection.
|
|
- **Event Log**: Easily accessible (Source of Truth).
|
|
|
|
## Components
|
|
- **Cards**: For task summaries, status updates.
|
|
- **Badges**: For status (e.g., `CLAIMED`, `PENDING`, `COMPLETED`).
|
|
- **Progress Bars**: For multi-step task progress.
|
|
- **Service Layer**: Placeholders for `apps/server` endpoints.
|
|
|
|
## UX Priorities
|
|
- Clear hierarchy.
|
|
- Intuitive navigation.
|
|
- Avoid clutter (maintain information density).
|