Repo clean-up (high level) Stability, efficiency & future-proofing.

Prompt

Title: Repo clean-up (high level) Stability, efficiency & future-proofing. Prompt: I'm planning on giving my ai model a prompt to improve my overall Repo, since i've added a lot of content and functionality recently, but I'm uncertain about the bloat, efficiency, stability and organisation of my repo as a whole. I'd like to know how to best tackle this. This is the prompt I came up with, let me know how I can improve this prompt: Add to to-do actions (in no particular order): 1) Focus hard on getting an "import layer" very clean and organised file-structure-wise and tampermonkey script to import character sheet to usage in modules sync link. This entire process needs to be very stable and smooth, any data the modules need needs to be available ad-hoc whenever possible. Grabbing syncing and loading everything from browsing to backend (or profile layer) needs to get a thorough coding session. 2) Bug audit, text redaction audit, many visual and textual mistakes left at places, alignments of texts in different modules GUI's, artifacts. 3) And honestly just a general refactoring of the entire codebase. We have been implementing a lot of different things, there are now many instructional files, to-do lists, rules, architecture, etc. I want to reduce all of this to what is essential for succes. Performance, stability and modularity are the core principles of this repo, together with accurate calculations based on real world (game mechanics). So essentially, I see these six very important strategic layers that shape the entire repo (in no particular order of importance): 1) Game-core mechanics (These formula's, data and information/facts drive the simulation engines) 2) + handling modularity 3) Front-end GUI + Interaction + dashboarding (visual & UIX). 4) Game-sync profile layer (Grabbing/acquiring/syncing/loading all live-website profile data, the backbone that enables relevant real-world simulations based on actual player stats & data). 5) Game-engines, the backbone for any kinds of modules, artifacts, optimizers, Simulators, reinforcement learning trainers, etc. 6) AI skills that help our agents navigate this complex repo in an efficient manner and helping agents deliver excellent quality stable coding, without bloatware. 7) Nuances, Standardized design choices, and elements throughout all the multiple facets of the repo and cross-layered choices. (like themes, CSS, wording, handling of interactions, developer/user preferences in all kinds of things from minimalism to hover-over information, all these little things that shape the nuances of our interaction with the software.) 8) The back-end that handle the performance management of the more demanding simulations and tasks that are less suited for running through the browsers.