** A few hours later **… yepz, got to do a reset again and he forgot everything this time and wants to prototype the app again, no matter I say he won’t look into the code base… any workround ? I think the main problem is this, the prototyper should be able to realize there’s a project already and go trough it to get the necessary context instead of trying to start over
** A few minutes later ** I GOT THE WORKAROUND FOLKS! here is what I did:
- although the old prototyper memory was gone, the project was still fine on the backend <>
- first I linked my github account to the source control and .
- pushed the project to github (it then created a new repository named “studio”)
- accessed the studio repo and downloaded an offline version, to be safe…
- cloned the repo to my local machine (something good to have, I’ll be able to work locally in vscode)
- Ok, until now I was just backing up the project, now comes the fun part:
- With your project open in the prototyper, ask for anything, something very simple.
- prototyper will plan, and you can ask him to prototype de app
- he’ll proceed to prototype and delete all your original project files… DON’T FREAK OUT
- when he is done, go to the backend <> and head to the Source Control panel once again
- hit the … from the source control dropdown
- if there are any changes to be committed first go to Changes → Discard All Changes … then confirm
- after that go to Commit → Undo Last Commit … then confirm to undo commit
- … menu again go to Changes → Discard All Changes … then confirm
- if some files are still left, waiting to be Staged:
- … menu again go to Changes → Discard All Changes … then confirm
- if not you successfully reverted the project the new prototyper messed up.
- Delete any temp/cache folder you have like .next
- In my project I also had to delete node_modules and package-lock.json
- reset the project VM
- npm install
- NOW FOR THE LAST PART, let’s talk to the new prototyper:
- Back to the prototyper interface (the magic wand)
- Prompt him: “take a look into the codebase, I’ve made substantial changes to the app we’re working on. let me know what you learned, don’t code anything”
- he’ll then proceed and get to know the project, YES!!! He’ll do it!
- then prompt again to be safe: “ok, for now one we’ll work with this app you just looked at. You’ll for now on disregard the original app idea and code you prototyped. sounds fair ? can you do that ? don’t code, just explain”
- he’ll agree with it, and this will be probably enough to keep his context in check not trying to return to the prototype he first coded
- if he does messes up, revert using the prototyper version control and be sure to prompt him to disregard the original prototype app and work exclusive with the one you ask him to read before sending new task, with time the new context should get stronger in memory.
That’s it! You got your very good and excellent prototyper friend back ready to work on your project again, and in my case, free from previous context, which does more good than bad… just make sure to keep a notepad updated with important information you talk with him, like planning, next features, desired future changes, etc.
NOTE: This will most certainly enable a local uploaded project to also use the prototyper, just follow the same steps.