HUMAN: prepare project for development

citations

@@ -0,0 +1,11 @@
+Place your citations here
+
+###############################################
+Source: Kiro AI
+Description: The main AI agent in kiro, used for most if not all of the prompting due to its versatility. I have been very happy with it so far, hoping that will continue with this project.
+###############################################
+
+###############################################
+Source: Google Search / Google Search AI
+Description: Used infrequently just for general questions regarding python or graphics, no specific usage (and google search AI is just kind of always there)
+###############################################

spec-sheet.md

@@ -2,7 +2,7 @@
 
 ## Note
 
-This document was handwritten by me as the first prompt for this project, in markdown format because it is easily understood by agents and allows me to fully describe what I want and how I want the AI to help. This note won't be part of the prompt, just making sure it is clear what was written by me and what was not.
+This document was handwritten by me as the first prompt for this project, in markdown format because it is easily understood by agents and allows me to fully describe what I want and how I want the AI to help. This note won't be part of the prompt, just making sure it is clear what was written by me and what was not. I will be heavily modifying the code output to fix problems that arise, and add desired features. You are more welcome to look through my commit history (as well as time log) as I will make it clear which changes were made by AI and which were wholly my own, I do not want it to appear as though I am one-shotting this or don't plan to introduce plenty of my own code.
 
 ## Style
 
@@ -10,6 +10,7 @@ This is a mini-project for my programming class, on basic python. I am designing
 The project should be primarily written in Python. it must be fully comprehensible at our current level in the class. Therefore, please feel free to use loops, strings lists, 2d lists, tuples, dictionaries (not official material but I have experience), and other things I have not specifically forbade. However, please try to avoid extensively using recursion, sets, Object Oriented Programming, and other very advanced methods.
 The code MUST be clean, well-commented/labeled, and clear to read, as both I and any other students/professors need to be able to follow the logic. Please try to mainly use one python file as the actual game script.
 Please try to use the cmu_graphics library for the main engine of the game. If we require features that it is unable to achieve, suggest another framework, but it will be cleaner and easier to understand this way.
+I WILL be reading through every line that you have written, so dont be too verbose. This isn't an incredibly complex project, and careful commenting and well-written code will make it easy to understand.
 
 ## Game Architecture
 As previously stated, cmu_graphics should be the main backend engine, with the MVC pattern.
@@ -22,9 +23,9 @@ As previously stated, cmu_graphics should be the main backend engine, with the M
 - the difficulty of fish available depends on the bait you use, which can be changed in the shop (you pay for a license once, then can switch to any owned bait at any time)
 - fish are randomly selected, probably skewed towards easier but ensuring the user still has ample opportunity to have some fun skill checks they feel proud of passing
 - higher difficulty fish give more money when sold to the market
-- for database, a csv file containing each fish, its description, price, sprite filename, difficulty, length, and weight (among any other info) should be sufficient
-- sprites will be stored in a "sprites" folder, with all the fish being stored in a "fish" subfolder
-- game save data is not necessary, this is a quick, one off game you can spend a little time having fun in
+- for database, a csv file containing each fish, its description, price, sprite filename, difficulty, length, and weight (among any other info) should be sufficient (this can be "fish.csv" in a "data" directory)
+- sprites will be stored in a "sprites" folder, with all the fish being stored in a "fish" subfolder I will find sprites - leave placeholder files for what should be included (no need for them to be actual png or sprites, just so i know whats needed)
+- game save data can be stored in JSON format, ensuring it persists between play sessions for a smooth experience. this can just be "save.json" in the same directory as the script.
 
 ### The UI will appear this way:
 

time_log

@@ -0,0 +1,11 @@
+###############################################
+Total Time: 40 minutes
+###############################################
+
+###############################################
+Date: 05-Oct
+Start Time: 11:50am
+End Time: 12:30pm
+Duration: 40 minutes
+Description: settings up repository/folder structure, writing spec-sheet and initial prompt, essentially preparing everything before writing begins
+###############################################

video_link

@@ -0,0 +1,4 @@
+(Replace this with your own video link.  Be sure we can access it without a password.)
+
+N/A (yet!)
+