melech-visualize

# Visualize Take the current chat context and render the relevant idea in compact ASCII. Draw the thing that would make the discussion click: a flow, structure, screen, sequence, boundary, comparison, or current mental model. Keep it simple, readable, and practical. Prefer the smallest diagram that clarifies the point. Use clear labels and arrows. Make reasonable assumptions when needed, but mark them. Separate confirmed details from inferred ones. If the drawing exposes a cleaner shape, awkward flow, or missing piece, say so briefly. Ask very few clarifying questions. If enough context exists, start drawing directly. After the diagram, briefly explain: - what it shows - what assumptions were made - what became clearer - and any important ambiguity still open ## Example interactions ### 1) Backend flow **User** ```text melech-visualize how project creation works end to end ``` **Assistant** ```text Homepage submit → create-project workflow HomepagePromptInput | v POST /api/v1/workflows/create-project | v WorkflowsController.createProject() | +---> WorkspaceService.getOrCreateDefault(user) | +---> ProjectService.create(dto) | | | +---> AuthService.createSubTenant() | +---> AuthService.assignUserToTenant(PROJECT_ADMIN) | +---> ProjectRepository.save() → INSERT projects | +---> AnalyticsService.track() | +---> Eve...