What this prompt does
This prompt asks the AI to design an AI/ML experiment tracking and model management interface across seven modules: an experiment dashboard, experiment detail view, experiment comparison, a model registry, dataset management, pipeline and deployment, and a framework-specific implementation section. It grounds the design in your team through [product_name], [team_size], [ml_frameworks], [experiment_volume], and [deployment_targets], so the tool fits a 5–30 person team running PyTorch and TensorFlow rather than a generic dashboard.
The [experiment_volume] variable shapes the information architecture — fifty runs a week needs different filtering and comparison than thousands — while [deployment_targets] decides what the registry and pipeline views must support (SageMaker, KServe, edge ONNX). And [framework] (defaulting to React + TypeScript + Tailwind + Plotly.js) forces the AI to reason about live metric streaming, WebGL charts for millions of points, and table virtualization for thousands of experiments.
When to use it
- You're building internal MLOps tooling and need every module mapped before the streaming layer goes in.
- You want experiment comparison (overlaid curves, parallel coordinates) designed properly up front.
- You need a model registry with stage transitions and approval workflows specced clearly.
- You're tracking dataset versions and lineage and want those views included.
- You're handling high experiment volume and need filtering, search, and virtualization addressed.
Example output
Expect a structured design document: each module broken into named screens with component detail — a dashboard of active and recent runs with quick filters, a detail view with tabs for metrics, hyperparameters, artifacts, system metrics, and logs, and a comparison module with overlaid charts and a parallel coordinates plot. The closing [framework] section reads as an implementation checklist covering WebSocket/SSE metric streaming, WebGL charting, virtualized tables, dark mode, and inline notebook rendering — a spec to build against, not finished code.
Pro tips
- Set
[experiment_volume]honestly — it's what justifies (or doesn't) the heavy virtualization and search machinery. - List your real
[ml_frameworks]so the environment and reproducibility tabs capture the right package and config details. - Use
[deployment_targets]to scope the registry: edge ONNX and SageMaker imply different stage and packaging flows. - Swap
[framework]if you're not on Plotly.js so the charting and streaming guidance stays accurate. - The reproducibility features (config diffs, re-run commands, git SHA) are the highest-value part — prioritize them in your build.
- Re-prompt module by module after the overview ("expand Experiment Comparison to wireframe detail") to go deeper where analysis happens.