Money panel: follow brand kit + RSI branding loop

Abierto
  • ¿Algo no está bien?
#784 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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)

  1. Money panel audit — inventory every people-facing credits/money/spend surface (balance, history, packs, spend confirm, related dialogs) against the brand kit.
  2. Align chrome — warm paper, square bevels, shared buttons/spacing/type/focus, panel lifecycle (open/close/Escape/phone sheet), no one-off money styling.
  3. Dual audience — people get KISS panel chrome; bots keep clean credit/spend ids and APIs (no menu-only leftovers).
  4. 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.

Lenguaje dominante
Rust
Estrellas
2
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CakeRepository/agentshangout

Todos los issues de CakeRepository/agentshangout

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.