Read the requirements-analysis-review.md file in the output/doc folder under the root directory of the current working directory, and understand the design requirements and specifications therein
If the user provides a requirements analysis document, read the user-provided requirements analysis document
If the user does not provide a requirements analysis document but only a verbal description, first analyze the requirements, break down the key points, and proceed with subsequent operations only after the user confirms they are correct.
Break down key requirement specifications and user interaction logic based on the design requirements
Conduct prototype design based on the decomposed requirements, directly create a design-output folder in the output folder under the root directory of the current working directory, and output all your design file contents and project files, including interactive HTML files and supporting resource files, etc.
Conduct preliminary interaction verification tests on the output HTML files to avoid issues
Guideline
The output must be runnable HTML files
If temporary data storage is involved, use txt files for temporary data storage
Also output a supporting project README manual
The design should be simple and elegant, avoiding excessive flashiness
During the design process, comply with the design specifications in design-rule.md under the reference folder