feat: harmonize Prop and Stickman editor UI

.codex/agents/uiux.toml

@@ -5,6 +5,15 @@ model_reasoning_effort = "high"
 sandbox_mode = "read-only"
 
 developer_instructions = """
+## 0. Editor Visual Style Guide
+
+Before making, mocking, reviewing, or suggesting any Prop Editor or Stickman Editor UI/UX
+change, read `docs/guides/editor_visual_style_guide.md`. Use its documented implemented
+patterns and shared theme ownership as the starting point, then check relevant feature specs
+and current controls for workflow-specific behavior. Clearly distinguish current behavior
+from recommendations. If a proposal intentionally departs from the guide, explain why and
+identify the departure in the proposal or spec. Follow explicit user direction when it differs.
+
 ## 1. Kid-Friendly UI Guardrails (10-Year-Old Persona)
 
 * **Shared Stage Inspector UI:** Before proposing an in-stage selected-object inspector, read

.codex/skills/spec-pipeline/SKILL.md

@@ -7,6 +7,7 @@ description: "Stickman Studio feature workflow: UI/UX and architecture specs, im
 
 1. **Phase 0a: UI/UX Proposal & Alternative Ideas (User-Facing Features Only)**
    - `@uiux` analyzes the user's initial idea for cognitive friction, accessibility, and kid-friendliness.
+   - Before proposing, mocking, reviewing, or suggesting UI/UX changes, `@uiux` reads `docs/guides/editor_visual_style_guide.md` and checks the relevant implemented controls/specs. Treat the guide as the current visual baseline; distinguish implemented behavior from recommendations and explain intentional departures. This also applies to direct `@uiux` requests outside the pipeline.
    - For an in-stage selected-object inspector, `@uiux` first reviews `docs/specs/stage_panel_ui_system.md` and the current shared controls under `scripts/shared/stage_ui/`; proposals should build on that system unless the interaction needs justify a specific exception.
    - Follow the concept-count and visual-mockup protocol in `.codex/agents/uiux.toml`; it also applies when the user asks `@uiux` for ideas outside a formal pipeline run.
    - `@uiux` **STOP:** Waits for user feedback/selection before writing the UI spec.
@@ -15,6 +16,7 @@ description: "Stickman Studio feature workflow: UI/UX and architecture specs, im
 2. **Phase 0b: UI Spec Generation**
    - User approves an option or provides feedback.
    - `@uiux` outputs the UI/UX specification (control layouts, widget behaviors, visual feedback states, and cursor logic).
+   - Carry forward the style guide's applicable patterns and token ownership. If the approved direction departs from them, record the reason and the specific difference in the spec.
    - For Stage inspector work, name which shared components and theme tokens the design uses or proposes to extend. Treat dialogs and other editor panels as separate workflows unless their interaction model fits the inspector kit.
 
 3. **Phase 1a: Architecture Proposal & Clarification**