File Upload System

About this workflow

Build real file uploads with validation, progress, storage, and display - files must survive refresh.

What happens when you run it

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

   Runs flow-file-upload-system-1-define-upload-requirements on Claude Sonnet 4.6
2. 2
   A proper upload surface: picker, drag-drop, validation, and progress.

   Runs flow-file-upload-system-2-build-the-upload-ui on Claude Sonnet 4.6
3. 3
   The server must receive, validate, store, and record the file for real.

   Runs flow-file-upload-system-3-implement-backend-storage on Claude Sonnet 4.6
4. 4
   Users must see their files after refresh - the proof uploads are real.

   Runs flow-file-upload-system-4-list-and-display-uploaded-files on Claude Sonnet 4.6
5. 5
   Deletion must remove both the record and the stored file.

   Runs flow-file-upload-system-5-add-delete-with-confirmation on Claude Sonnet 4.6
6. 6
   Verify the full upload lifecycle including hostile inputs.

   Runs flow-file-upload-system-6-upload-qa-pass on Claude Sonnet 4.6

Best for

• •Recurring tasks you currently copy-paste between tools.
• •When a single prompt isn't enough — you need a chain where output(n) feeds prompt(n+1).
• •Fork and adapt if your inputs differ materially from the author's use case.

Models used