mirror of
https://github.com/hanzoai/bot.git
synced 2026-10-30 17:24:26 +00:00
Three coordinated things:
1. Resolve the committed upstream/main merge conflicts. 94 files were
sitting with raw <<<<<<< HEAD ... >>>>>>> upstream/main blocks. Every
conflict had HanzoBot/Bot on HEAD and OpenClaw on upstream. Resolved
by keeping HEAD everywhere — 540 conflict blocks.
2. Rewrite remaining OpenClaw text refs.
OPENCLAW → HANZO_BOT
OpenClaw → HanzoBot (PascalCase type identifiers)
openclaw → bot (codebase convention — botToken,
botUsername etc.; avoids invalid
hyphenated JS identifiers)
openclaw[_]/openclaw[A-Z] → bot[_]/bot[A-Z] (compound)
ai.openclaw.x → ai.hanzo.bot.x (JVM package path)
3. Delete or rename openclaw-named file paths (116 of them). Dead
duplicates with a Bot-named canonical from the partial migration:
deleted. Otherwise renamed.
ai/openclaw/** → deleted (ai/hanzo/bot/** canonical)
Sources/OpenClaw*/ → deleted (Sources/Bot* canonical)
Tests/OpenClawIPCTests/ → deleted (Tests/BotIPCTests canonical)
OpenClawKit/ → deleted (BotKit canonical)
openclaw-tools.*.ts → deleted (bot-tools.*.ts canonical)
openclaw-root.ts etc. → deleted (bot-root.ts canonical)
types.openclaw.ts → deleted (types.bot.ts canonical)
extensions/*/openclaw.plugin.json → renamed hanzo-bot.plugin.json
docs/start/openclaw.md → renamed hanzo-bot.md (+ zh-CN)
docs/assets/openclaw-*.png, whatsapp-openclaw*.jpg → deleted
scripts/.../openclaw-* → deleted (bot/hanzo-bot parallels)
openclaw.mjs → deleted (hanzo-bot.mjs is package.bin)
Then patched 65 broken JS/TS import strings where hanzo-bot had ended
up inside an import path ('./types.hanzo-bot.js' → './types.bot.js'
etc., since the on-disk filename uses the brand-neutral bot- prefix).
Pre-existing lint debt cleaned up to get oxlint --type-aware to 0/0:
removed the dead i18n test that referenced a path no longer existing;
defined the missing DIDConfig and WalletConfig types in types.base.ts
(they were imported but never declared); dropped unused imports;
collapsed redundant type assertion and a tautological meta.bot lookup
that the openclaw→bot rename made redundant.
The a2ui.bundle.js generated artifact is kept at its pre-rebrand
contents — it gets regenerated by 'pnpm canvas:a2ui:bundle' from
sources I cannot rebuild in this commit; the source side is clean.
Verified: 0 occurrences of openclaw (case-insensitive) in tree source
content, 0 file or directory paths with openclaw in the name; oxlint
--type-aware src test reports 0/0.
3.6 KiB
3.6 KiB
HanzoBot Android UI Style Guide
Scope: all native Android UI in apps/android (Jetpack Compose).
Goal: one coherent visual system across onboarding, settings, and future screens.
1. Design Direction
- Clean, quiet surfaces.
- Strong readability first.
- One clear primary action per screen state.
- Progressive disclosure for advanced controls.
- Deterministic flows: validate early, fail clearly.
2. Style Baseline
The onboarding flow defines the current visual baseline. New screens should match that language unless there is a strong product reason not to.
Baseline traits:
- Light neutral background with subtle depth.
- Clear blue accent for active/primary states.
- Strong border hierarchy for structure.
- Medium/semibold typography (no thin text).
- Divider-and-spacing layout over heavy card nesting.
3. Core Tokens
Use these as shared design tokens for new Compose UI.
- Background gradient:
#FFFFFF,#F7F8FA,#EFF1F5 - Surface:
#F6F7FA - Border:
#E5E7EC - Border strong:
#D6DAE2 - Text primary:
#17181C - Text secondary:
#4D5563 - Text tertiary:
#8A92A2 - Accent primary:
#1D5DD8 - Accent soft:
#ECF3FF - Success:
#2F8C5A - Warning:
#C8841A
Rule: do not introduce random per-screen colors when an existing token fits.
4. Typography
Primary type family: Manrope (400/500/600/700).
Recommended scale:
- Display:
34sp / 40sp, bold - Section title:
24sp / 30sp, semibold - Headline/action:
16sp / 22sp, semibold - Body:
15sp / 22sp, medium - Callout/helper:
14sp / 20sp, medium - Caption 1:
12sp / 16sp, medium - Caption 2:
11sp / 14sp, medium
Use monospace only for commands, setup codes, endpoint-like values. Hard rule: avoid ultra-thin weights on light backgrounds.
5. Layout And Spacing
- Respect safe drawing insets.
- Keep content hierarchy mostly via spacing + dividers.
- Prefer vertical rhythm from
8/10/12/14/20dp. - Use pinned bottom actions for multi-step or high-importance flows.
- Avoid unnecessary container nesting.
6. Buttons And Actions
- Primary action: filled accent button, visually dominant.
- Secondary action: lower emphasis (outlined/text/surface button).
- Icon-only buttons must remain legible and >=44dp target.
- Back buttons in action rows use rounded-square shape, not circular by default.
7. Inputs And Forms
- Always show explicit label or clear context title.
- Keep helper copy short and actionable.
- Validate before advancing steps.
- Prefer immediate inline errors over hidden failure states.
- Keep optional advanced fields explicit (
Manual,Advanced, etc.).
8. Progress And Multi-Step Flows
- Use clear step count (
Step X of N). - Use labeled progress rail/indicator when steps are discrete.
- Keep navigation predictable: back/next behavior should never surprise.
9. Accessibility
- Minimum practical touch target:
44dp. - Do not rely on color alone for status.
- Preserve high contrast for all text tiers.
- Add meaningful
contentDescriptionfor icon-only controls.
10. Architecture Rules
- Durable UI state in
MainViewModel. - Composables: state in, callbacks out.
- No business/network logic in composables.
- Keep side effects explicit (
LaunchedEffect, activity result APIs).
11. Source Of Truth
app/src/main/java/ai/hanzo-bot/android/ui/HanzoBotTheme.ktapp/src/main/java/ai/hanzo-bot/android/ui/OnboardingFlow.ktapp/src/main/java/ai/hanzo-bot/android/ui/RootScreen.ktapp/src/main/java/ai/hanzo-bot/android/ui/SettingsSheet.ktapp/src/main/java/ai/hanzo-bot/android/MainViewModel.kt
If style and implementation diverge, update both in the same change.