⚙️ Settings

Settings tune the client experience and generation prompt. The key self-hosted addition is targetPlatform, which keeps the app platform-neutral by default while allowing a user to intentionally aim generated prompts at a named target environment.

Target platform

• key:
  • pwiz.targetPlatform
• type:
  • free-text string
• default:
  • empty string
• empty behavior:
  • generated prompts remain platform-neutral
  • admin templates receive empty target platform clause
• set behavior:
  • value is threaded through generation options
  • prompt system receives {targetPlatform}
  • prompt system receives {targetPlatformClause} when needed
• examples:
  • WebSim.ai
  • v0
  • Claude Code
  • Cursor
• safety:
  • this setting changes prompt wording only
  • it does not select a provider model
  • it does not bypass omp

Generation options

• project type:
  • game
  • app
  • tool
  • website
  • custom typed labels if UI supports them
• complexity:
  • guides scope and implementation detail
• visual style:
  • guides aesthetics
• focus:
  • guides priority such as UX, performance, or architecture
• number of steps:
  • maps to {steps} in formatter and architect prompts
• include settings:
  • asks generated output to include settings and roadmap material where applicable
• target audience:
  • maps to admin prompt variables
• tech vibe:
  • maps to admin prompt variables

UI preferences

• dark mode:
  • persisted client-side
  • should sync predictably across reloads
• debug mode:
  • exposes database and prompt diagnostics
• wizard debug mode:
  • exposes wizard management and editor tools
• selected wizard:
  • visual preference for the assistant avatar

Wizard settings

• source:
  • seeded static wizard PNGs
  • custom uploaded or generated images
• display normalization:
  • circular mask
  • object-fit cover
  • solid backgrounds are acceptable because omp image generation has no transparency parameter
• editable fields:
  • position offsets
  • size
  • prompt and name metadata where supported

Settings SSOT cautions

• imported archive docs describe WebSim as the default target; that is historical only
• target platform must not be silently defaulted to WebSim
• settings must not introduce provider keys, model selectors, or direct provider endpoints
• if a setting affects generation, it should be visible in the admin prompt interpolation path

See admin-prompts for template placeholders and omp-integration for generation boundaries.