File Upload System
0/6 steps0%

Step 1 of 6

Define upload requirements

Decide file types, limits, and storage before writing upload code.

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

Prompt Capsule
Define the file upload spec. Specify: allowed file types (e.g. jpg/png/pdf) and max size; where files are stored for this MVP (server uploads directory, database, or object storage) and the tradeoff; the file record model (id, owner, filename, storedPath/url, mimetype, size, uploadedAt); unique storage naming to prevent collisions; and which users can see/delete which files.
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

A storage decision plus a complete file record model and limits.

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