Flows workflow logoFlows
MongoDB Data Model Plan
0/5 steps0%

Step 2 of 5

Decide embed vs reference

The core MongoDB decision, made per relationship with reasoning.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule
Design the collections. For each relationship decide embed vs reference using: read-together data embeds (if bounded and owned); independently-queried, unbounded, or shared data references. Document each decision with its reason and the risk if wrong. Define every collection's document shape with field types, the owner field (userId) on user data, and createdAt/updatedAt.
Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

Collection shapes with justified embed/reference decisions.

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent