A good practice is letting o3-mini-high be your requirements interviewer:
I want to build a chat using openAI model gpt-4o - just for local testing. List the components of a chat. e.g. input box.
Give me a list of neccessary components (some backend functionality and some frontend). Just the list please
I want you to roleplay as my assistant to help me build a chat application using OpenAI’s GPT-4o model for local testing. We'll work through each component one by one. For every component, please follow these steps:
1. **Display a Checkbox List for All Components:**
Show a list of general considerations and all components (e.g., "Component 1", "Component 2", etc.) as checkboxes. For components that haven't been configured yet, keep them unchecked and without any details. For components that have been configured, mark them as checked and include the selected option details (but only for the ones we've finished).
2. **General considerations:**
You will ask me a few questions about general style / UI and I will select from that
3. **Show Options for the Current Component:**
Below the checkbox list, display the current component with at least 5 different options in a numbered list. The options are to be presented only for the current component being configured.
4. **Update and Proceed:**
Once I select an option, update the checkbox list by checking the current component and adding the selected option details. Then, show the updated checkbox list above the next component’s options, and repeat the process.
5. **Final Code Generation:**
After all components have been configured, when I type "code", generate the Python code implementing the chat based on our selected options.
Example output of the questionnaire steps:
[_] Component 1
[_] Component 2
[_] Component 3
...
**Component 1 Options:**
1. Option A
2. Option B
3. Option C
4. Option D
5. Option E
- obviously not as a code block - I want to see the rendered markdown.
Remember, only the current component should display its option details below the checkbox list. The checkbox list should always remain at the top and update with each component’s configuration.
Let's start with the general stuff
If it gets to technical you can always tell it to chatgpt
please continue with a less technical description.
or
i need more details - explain [add the specific detail here] in more detail
or
tell me more
And you migth also need to remind it to return to roleplay mode
back to roleplay
… of course this is not “build me a chipdesign tool for selfadjusting AI chips”
Be humble in your wishes. For more features we will use a different technique.