Prompt Wizard SSOT

2 min read

🧾 Imported Notes

The archive presented itself as WebWiz Prime, an AI-powered prompt engineering ecosystem originally aimed at WebSim.ai. The self-hosted port retargets that concept to Prompt Wizard and local omp generation.

Archive product claim

  • name in archive:
    • WebWiz Prime
    • WebSim Prompt Wizard
  • stated purpose:
    • turn simple ideas into structured development prompt sequences
    • provide community blueprint sharing and discovery
    • provide AI chat assistance
    • provide customizable wizard avatars through Fabric.js
    • use persistent database integration
    • use React architecture
  • archive assessment:
    • architecture grade: A minus, 87 of 100
    • praised React migration and feature set
    • flagged missing testing, TypeScript, and stronger error boundaries
    • flagged incomplete CSS consolidation and prop drilling

PIMP audit first fix

  • highest-return fix:
    • global Error Boundary plus fallback UI
  • intended impact:
    • prevent white-screen crashes
    • report genuine runtime errors
  • related current page:

Imported diagrams

The archive’s mermaid file contained four diagrams:

  • original app dependency graph:
    • index.html to AppWrapper.jsx
    • AppWrapper.jsx to WebsimSocket Init
    • App.jsx to reducer, UI state hook, input, results, overlays
    • overlays to settings, docs, debug drawer, blueprint gallery, wizard editor
  • flaw taxonomy:
    • critical: no error boundaries, CORS failures, localStorage race
    • major: prop drilling, no memoization, no code splitting, admin confirm blocking
    • minor: many CSS files, no TypeScript, no tests, accessibility gaps, naming inconsistency
  • proposed context architecture:
    • AppProvider for room and notifications
    • components consume context instead of prop drilling
  • generation error flow:
    • validate idea
    • call LLM API
    • handle timeout
    • parse JSON
    • post-process prompts
    • optionally generate Mermaid
    • save history

Reconciliation

  • diagrams are useful as archive forensics
  • WebsimSocket Init is now a known residue, not a desired local architecture component
  • safe fallback for invalid JSON is rejected by the self-hosted port; failed JSON must produce a real error
  • WebSim API examples in imported docs are historical and must not be copied into current app docs

See docs-vs-reality for mismatch details and index for current target architecture.