Open
Description
This is a common use case and it would be helpful to illustrate a "best practices" approach to using scripts to do the following:
- Have a script that takes a high-level description of an application and breaks it into parts (decomposition) in a .md file
- Have a script that takes the decomposition and lays out specific code files and APIs that are needed.
- Have a script that given the above scripts, will generate code for the application
This example can also show how we identify the proper context for the scripts using def, fileRead, or other.
An example might be the following.
"Task: I want to write a web application that plays tic-tac-toe where the client side handles the UI and the server side hosts the game content and decides what move the opponent should make.
This task should be divided into a client-side implementation and a server side implementation. Generate a description
of both implementations that could be used to generate the actual code."