Files
browser/openspec/changes/polish-platform-interaction-design/proposal.md
T
2026-07-11 14:56:10 +08:00

2.2 KiB

Why

The console now has real API-backed coverage and automated browser acceptance, but the current interaction polish still depends on scattered page-level choices instead of explicit acceptance criteria. This change converts UI dissatisfaction into a concrete platform_web polish contract so the next implementation can improve usability without drifting into a generic SaaS dashboard or changing product scope.

What Changes

  • Define accepted interaction/design criteria for the required first-party areas: 首页、服务器管理、插件市场、用户管理、AI 提供商管理.
  • Define server detail workflow polish for lifecycle controls, logs, config, plugin controls, AI assistant, and operation history.
  • Require responsive desktop/mobile walkthrough coverage and no visible overlap, clipped text, unreadable panels, or inaccessible control states.
  • Require the polish to preserve the existing black mecha default theme, magical-girl alternate theme, translucent game-operations surfaces, grouped navigation, and shared theme primitives.
  • Require compatibility with the automated browser acceptance suite so visual/interaction polish does not weaken API-backed route proof or safety scanning.
  • No breaking product behavior, API, authorization, plugin, run, billing, cloud-host, or provider-marketplace changes are expected.

Capabilities

New Capabilities

  • platform-interaction-design-polish: Defines accepted interaction and visual polish requirements for platform_web first-party console areas, server detail workflows, responsive behavior, theme preservation, browser walkthrough evidence, and automated acceptance compatibility.

Modified Capabilities

  • None.

Impact

  • Affected roots: platform_web/, platform_web documentation, and OpenSpec delivery stream files.
  • Expected implementation areas: shared theme surfaces/classes, route/page layouts, command affordances, responsive behavior, state feedback, browser walkthrough evidence, and test coverage.
  • Validation impact: requires cd platform_web && npm run typecheck && npm test && npm run build, automated browser acceptance against the local debug stack, scripts/check-structure.sh, and openspec validate polish-platform-interaction-design --strict.