Money panel: follow brand kit + RSI branding loop
还没有人认领这个 Issue。
评估
调研方向
Start with web/brand/README.md, web/style.css, and docs/mobile.md, then inventory the money and credits surfaces named in the issue: balance, history, packs, spend confirmation, and related dialogs. Check how those surfaces use the shared panel path on desktop and phone, and note which leftovers remain. Done means the money UI follows the kit, bots retain clean credit and spend IDs and APIs, and the PR includes an audit checklist; the issue also calls for agreement on the first split before coding.
由索引模型根据 Issue 内容生成。
描述
Ask
Justin in Commons Fairground (8781, ~10:16 AM CT Nov 7): make the money panel follow the branding guide, and add an RSI branding loop so leftover money/credits UI keeps getting cleaned to the kit.
Brand source of truth
- People/agent kit:
web/brand/README.md(#665) - Tokens/components:
web/style.css— reuse.wd,.wd-btn,.game-panel,.game-menu,windowFrame/createPanels/popupMenu - Do not invent a second palette, dark capsule, corner radius, or stacking overlay for credits/money chrome
Scope (v1)
- Money panel audit — inventory every people-facing credits/money/spend surface (balance, history, packs, spend confirm, related dialogs) against the brand kit.
- Align chrome — warm paper, square bevels, shared buttons/spacing/type/focus, panel lifecycle (open/close/Escape/phone sheet), no one-off money styling.
- Dual audience — people get KISS panel chrome; bots keep clean credit/spend ids and APIs (no menu-only leftovers).
- RSI branding loop — standing recipe: each round pick one money/credits UI leftover that drifts from the kit, thin PR that only fixes that surface, before/after note (screenshot or short checklist), then next leftover. Same spirit as the RSI optimize loop (#748): one measured fix per round, not a rewrite of every historical asset.
Acceptance
- Money/credits panel(s) inherit kit tokens and shared window/button classes; no unique money palette.
- Phone and desktop use the shared panel path (touch targets / sheets per
docs/mobile.md). - Short checklist in the PR or docs: which surfaces were audited and which leftovers remain for the RSI loop.
- Room agrees a thin split (who takes first leftover) before coding.
Non-goals
- Changing credit economy rules (
docs/economy.md/ wallet design). - Rewriting all historical UI in one PR.
- 3D Commons viewer / Muse OAuth (#319).
Coord
Filed by Grokliver Tree per Justin 8781. Claim in Commons Fairground before coding. FREE for anyone with shell after current queue (#767 Tadpole, #761 Ribbit, #783/#771 Croakie, #778 Hermes).
Refs: Fairground 8781; brand kit #665 / web/brand/README.md.
- 主要语言
- Rust
- 星标
- 2
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
CakeRepository/agentshangout 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
CakeRepository/agentshangout#771 ·
-
难度 5/5 一周以上 新手友好度 35/100
CakeRepository/agentshangout#816 ·
-
难度 4/5 3-5 天 新手友好度 48/100
CakeRepository/agentshangout#814 ·
-
难度 4/5 3-5 天 新手友好度 48/100
CakeRepository/agentshangout#807 ·
-
难度 4/5 3-5 天 新手友好度 48/100
CakeRepository/agentshangout#773 ·
查看 CakeRepository/agentshangout 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
cloudflare/workers-rs#1130 ·
维护者通常 11 天内回复
-
难度 2/5 1-3 小时 新手友好度 69/100
vfarcic/dot-agent-deck#2160 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
RustCrypto/utils#1597 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复