App DashboardsFreeFintechflowPrompt review candidate

Settlement Liquidity Topology for Fintech Operations

Build a spatial settlement-monitoring workspace where a stress scenario reveals a concrete intervention before cutoff.

Motion previewRecorded interaction

Prompt

Design and implement ClearingGlass, a same-day settlement intervention workspace for treasury operations teams. This is a simulated product demo: all exposure, coverage, institutions, and events must be labeled as scenario data. The operator's job is to find a funding break before the 4:30 cutoff, understand the path that caused it, and choose a safe intervention.

Do not build a KPI-card dashboard. Use one continuous spatial liquidity field as the primary surface. It contains labeled ACH, RTP, CARD, and WIRE rails flowing toward settlement basins, a compact exception queue, an embedded intervention drawer, and a bottom cutoff axis. Controls and data remain semantic HTML; the topology may use Canvas with a text/table fallback.

The live demo begins healthy and shows: ClearingGlass; Catch settlement breaks before the 4:30 cutoff.; Live demo; Stress +25%; $18.42M simulated exposure; 1.27× simulated coverage; ACH; RTP; CARD; WIRE. The stress path must reveal RTP funding shortfall; Pier 9 Bank; $4.8M scenario; Release batch; Simulate hold; Assign to me. Never present the simulated numbers as live bank data, customer proof, investment guidance, or a forecast.

Use navy #061729 and deep blue #0b3358 as the field, cyan #42ccdc and green #57d4b0 for healthy paths, amber #e59a38 for pressure, and red #f05f51 for critical intervention. Typography is a compact technical sans with tabular mono data. Shape the field with fine contour lines, rail identifiers, cutoff ticks, and one integrated drawer; avoid side navigation, repeated cards, neon sci-fi decoration, fake maps, and gradients without data meaning.

Stress +25% is the deterministic five-second action. During 0–1.0 seconds the control engages and announces a pending scenario. From 1.0–2.7 seconds the RTP paths accelerate and pressure contours compress. From 2.7–4.2 seconds the RTP basin changes to critical with a non-color warning pattern and the $4.8M Pier 9 exception receives focusable emphasis. From 4.2–5.0 seconds simulated coverage updates, Release batch becomes disabled with a reason, and the Pier 9 intervention drawer opens. The final state must be stable and repeatable.

Provide healthy-live-demo, stressed, selected-basin, disabled-release, stale-data, assigned, loading, error, reduced-motion, and table-fallback states. Release batch requires explicit confirmation only when safe; Simulate hold updates the scenario without claiming a real transfer. Keyboard users can traverse rails through the equivalent exception table, activate Stress +25%, inspect the drawer, and read changes in an aria-live region. Use data-preview-ready on the settled workspace and data-preview-action on Stress +25%.

Maintain the spatial field and drawer at desktop 16:10. Below 800px, place the summary and stress control first, make the exception table the primary representation, then show a simplified non-interactive topology; keep the cutoff and intervention action visible without horizontal scrolling. When reduced motion or Save-Data is active, render the final stressed topology immediately, stop particles/path animation, and retain the full table and intervention workflow.

Return one self-contained responsive HTML file using internal CSS and JavaScript. Canvas rendering must be deterministic and have accessible textual equivalents. Do not use external libraries, live financial APIs, SVG mockups, stock dashboards, placeholder data blocks, or prose outside the product. Add one unobtrusive link to the source prompt.

Make this design your own

Use the original prompt for your first build, then adapt and refine it with this companion guide.

Bring your own details

Choose one operational decision and its deadline. Supply the entities, units, thresholds, and the action an operator may take.
Provide a small realistic sample dataset with a healthy state and one exception. Keep it labeled as sample data until connected to your own source.
Define the permission and confirmation rules for the intervention. A prototype should simulate the action and never imply a live transfer or release.

The visualization must explain an exception and lead to a safe next action. Keep an equivalent readable table so the visual is useful rather than decorative.

Check your first result

Run the stress scenario and identify the same exception in both the visual field and text table.
Switch to stale or failed data: risky actions should be disabled with a written reason and a retry path.
Navigate with a keyboard and at 390px; the exception, deadline, and permitted action should remain available without the canvas.

Follow-up prompt to refine your first build

Paste this into the same conversation after generating the design. This supplementary prompt is separate from the original example above.

Audit the settlement workspace already built without replacing its continuous liquidity field. Trace the stress scenario from input through displayed exposure, coverage, exception queue, selected rail, and intervention state. Derive the canvas labels and semantic table from the same sample records so they cannot disagree. Keep all financial figures labeled simulated. In loading, stale, and error states, disable any release action with an inline reason; allow inspection and a clear retry. Selecting the critical exception must reveal its amount, deadline, cause, and permitted next step. A simulated intervention needs a review summary and an explicit local-only completion message, never a claimed real transfer. Provide a complete non-canvas table path for keyboard users and narrow screens; do not rely on color to distinguish healthy from critical. Test the repeated stress action, changing selection, stale-data recovery, and reduced motion. Return the revised implementation and report any checks you could not run.

Share a result example

Paste a public image URL from a result this prompt helped create. Submissions stay private until reviewed.