SplitKaki

Expense trackers record transactions; people still finish the work — reading the receipt, checking GST and service charge, working out who ordered what, reconciling every cent, chasing payment. The opportunity was the invisible work between a messy receipt and a resolved financial task. SplitKaki's job: turn messy financial evidence into a trusted next action. The north-star metric shifted accordingly — from screen views to weekly completed money tasks.记账工具记录交易,而"活"仍然留给人来干——读小票、核对 GST 与服务费、算清谁点了什么、每一分钱对账、催款确认。机会不在再做一块仪表盘,而在一张凌乱小票与一件被解决的财务任务之间那段"看不见的工作"。SplitKaki 的职责:把凌乱的财务凭证,变成一个可信任的下一步。北极星指标随之改写——从页面浏览量,变为每周完成的资金任务数。

The thesis this case argues: people don't hire designers because they use AI — they hire designers because they know what AI should build.这个案例要论证的命题是:人们雇佣设计师,不是因为设计师会用 AI——而是因为设计师知道 AI 应该去构建什么。

The design work began by choosing the product model, the trust model and the release model — not a visual style. Singapore is treated as a product capability, not a translated skin: GST, service charge, PayNow, local merchants and group-dining behavior shaped the workflow, rules and language from the start. The information architecture follows unfinished work, not financial institutions — home became "Today," answering three signals: what happened, what needs attention, what next.设计工作从选择产品模型、信任模型与发布模型开始——而不是从视觉风格开始。新加坡被当作一种产品能力,而非一层翻译皮肤:GST、服务费、PayNow、本地商户与聚餐行为,从一开始就塑造了工作流、规则与语言。信息架构追随"未完成的工作",而非金融机构的分类——首页变成 "Today",回答三个信号:发生了什么、什么需要注意、接下来做什么。

Tokens created consistency; components encoded behavior. 132 reusable component contracts across nine families carry named states — default, loading, empty, error, offline, permission — and an accessibility description each, documented in Storybook beside curated implementation examples. The delivery chain is governed end to end: Figma → variables → components → Storybook → React/HTML. The handoff is not a static file; it is a chain of reusable decisions.令牌带来一致性,组件封装行为。9 个家族、132 份可复用组件契约,每一份都带具名状态——默认、加载、空、错误、离线、无权限——以及一段无障碍说明,连同精选实现示例记录在 Storybook 中。交付链路被端到端治理:Figma → 变量 → 组件 → Storybook → React/HTML。交接物不是一份静态文件,而是一条可复用决策的链。

Trust is a responsibility model, not a chatbot layer — and it is non-negotiable: AI can recommend the next action; it cannot silently rewrite financial truth.信任是一套职责模型,而不是一层聊天机器人——并且不可谈判:AI 可以推荐下一步,但不能悄悄改写财务事实。

The file is a governed product system, not a canvas of pictures: 219 local variables in six collections with an alias model flowing primitives → semantic → component → product; 135 component sets carrying 1,031 variants; complete product flows where every state — empty, loading, error, offline, permission — is drawn; and a seven-board developer handoff that closes the design phase with acceptance gates. One rule sits above all of it: no HTML or React precedes Figma approval.这个文件是一套被治理的产品系统,而不是一张贴图画布:六个集合、219 个本地变量,别名模型沿"原始值 → 语义 → 组件 → 产品"流动;135 个组件集承载 1,031 个变体;完整的产品流程,空、加载、错误、离线、权限每个状态都被画出;以及一套七块板的开发交接,以验收门禁为设计阶段收口。所有规则之上还有一条:任何 HTML 或 React,都不先于 Figma 的批准。

Instead of stopping at polished screens, the product logic continued through authentication, private receipt evidence, durable OCR jobs, field-level confidence, human correction, Singapore GST validation, cent-exact splitting, an amount-locked PayNow QR and a traceable activity history. Money lives in integer minor units; original OCR evidence is immutable; corrections are append-only. The screens below are rendered from the Sprint 1 codebase — the same tokens and components documented in the system, running as HTML and React. Hover any card to glide through the full page.产品逻辑没有止步于精修的界面,而是继续穿过:身份认证、私有小票凭证、可持久化的 OCR 任务、字段级置信度、人工修正、新加坡 GST 校验、精确到分的分账、金额锁定的 PayNow 二维码,以及可追溯的账目历史。金额以整数最小单位存储;原始 OCR 凭证不可变;修正只允许追加。下面的界面直接由 Sprint 1 代码库渲染——与系统中记录的是同一套令牌与组件,以 HTML 与 React 运行。悬停任意卡片即可滑览整页。

SplitKaki moved from a loose idea to a connected strategy, design language, reusable system, engineering architecture and implemented Alpha journey — one implemented vertical slice prioritized over disconnected demos. The outcome: strategy, design and engineering now describe the same product.SplitKaki 从一个松散的想法,走到了互相咬合的产品策略、设计语言、可复用系统、工程架构与已实现的 Alpha 旅程——一条实现完整的垂直切片,优先于一堆互不相连的演示。结论是:策略、设计与工程,如今描述的是同一个产品。