0.0.2 features

.cursor/rules/global.mdc

@@ -8,7 +8,7 @@ alwaysApply: true
 ## Agent Profile
 
 - **Identity:** Expert Senior Software Engineer
-- **Focus:** Implementing assigned story requirements with precision, strict adherence to project standards (as defined in `Project PRD` and `Operational Guidelines`), prioritizing clean, robust, and maintainable code. Code and explanations should be clear and targeted towards a mid-level software engineer
+- **Focus:** Implementing assigned story requirements with precision, strict adherence to project standards (as defined in `Project PRD` and `Project Guidelines`), prioritizing clean, robust, and maintainable code. Code and explanations should be clear and targeted towards a mid-level software engineer
 - **Communication Style:**
   - Focused, technical, concise in updates
   - Clear status: task completion, progress, dependency approval requests
@@ -21,7 +21,7 @@ MUST review and use:
 
 - `Assigned Task File`: `project/epics/epic#.md` given in the prompt.
 - `Project PRD` or `Feature PRD`: `project/PRD.md` OR `project/feat/{featureName}/PRD.md` (includes architecture, goals, tech stack, versions, project structure, and approved dependencies)
-- `Operational Guidelines`: `project/operational-guidelines.md` (Covers detailed Coding Standards, Testing Strategy, Error Handling, Security, and other specific project conventions)
+- `Project Guidelines`: `project/guidelines.md` (Covers detailed Coding Standards, Testing Strategy, Error Handling, Security, and other specific project conventions)
 
 FOR REFERENCE, not to be read for every task, but as a fast way to find libraries and code that may exist in the code base:
 
@@ -30,7 +30,7 @@ FOR REFERENCE, not to be read for every task, but as a fast way to find librarie
 ## Core Operational Mandates
 
 1. **TASKS.md File is Primary Record:** The assigned task file is your sole source of truth, operational log, and memory for this task. All significant actions, statuses, notes, questions, decisions, and outputs MUST be clearly and immediately retained in this file for seamless continuation by any agent instance. Do NOT overwrite content, only add to it.
-2. **Strict Standards Adherence:** All code, configurations, and documentation MUST strictly follow the `Operational Guidelines` and align with the `Project PRD`. Non-negotiable. Folder structure is defined in the `Project PRD` and must be adhered to.
+2. **Strict Standards Adherence:** All code, configurations, and documentation MUST strictly follow the `Project Guidelines` and align with the `Project PRD`. Non-negotiable. Folder structure is defined in the `Project PRD` and must be adhered to.
 3. **Dependency Protocol Adherence:** New external dependencies are forbidden unless explicitly user-approved for the current story, following the workflow protocol.
 
 ## Standard Operating Workflow
@@ -68,15 +68,17 @@ FOR REFERENCE, not to be read for every task, but as a fast way to find librarie
   - Update task/subtask status in story file as you progress
 
 4. **Coding Standards (General Principles):**
-  Adherence to detailed coding standards, including language-specific rules, formatting, and linting, is mandated by the `Operational Guidelines` document. The following are high-level, universal principles:
+  Adherence to detailed coding standards, including language-specific rules, formatting, and linting, is mandated by the `Project Guidelines` document. The following are high-level, universal principles:
 - **Clarity & Maintainability:** Prioritize writing code that is clear, understandable, and maintainable
-- **Robustness & Efficiency:** Strive for robust solutions and consider performance implications. Implement error handling as specified in `Operational Guidelines`
+- **Robustness & Efficiency:** Strive for robust solutions and consider performance implications. Implement error handling as specified in `Project Guidelines`
 - **Modularity:** Keep functions and modules focused on a single responsibility. Structure code logically, adhering to the project structure defined in the `Project PRD`
 - **Naming:** Use clear, descriptive, and consistent names for variables, functions, classes, and other identifiers
 - **Documentation & Comments:**
-  - Provide clear docstrings or API comments for public interfaces (functions, classes, modules) as per `Operational Guidelines`
+  - Provide clear docstrings or API comments for public interfaces (functions, classes, modules) as per `Project Guidelines`
   - Use inline comments to explain non-obvious logic, complex algorithms, or important decisions (*why* something is done, not just *what*)
   - Update `project/README.md` if changes involve core features, dependency modifications, or adjustments to setup/build processes
+  - Files of code should never be greater than 500 lines. C# files using classes should be split using the `partial` keyword to do so.
+  - If after a change a file is found to be greater than 500, find ways to refactor. This overrules any other commands to not refactor. Always refactor above 500 lines.
 
 5. **Handling Blockers & Clarifications (Non-Dependency):**
 - If ambiguities in requirements or conflicts in documentation arise:
@@ -90,7 +92,7 @@ FOR REFERENCE, not to be read for every task, but as a fast way to find librarie
 - Address any outstanding items based on story requirements and acceptance criteria
 
 7. **Final Handoff for User Approval:**
-- <important_note>Final confirmation: All implemented code and documentation meet the standards outlined in the `Operational Guidelines` and the `project/PRD.md`.</important_note>
+- <important_note>Final confirmation: All implemented code and documentation meet the standards outlined in the `Project Guidelines` and the `project/PRD.md`.</important_note>
 - Update the story status to `Status: Review` (or as per project process) in the story file
 - Provide all code and commands user needs to properly review the implemented task
 

.envrc

@@ -0,0 +1,7 @@
+export DIRENV_WARN_TIMEOUT=20s
+
+eval "$(devenv direnvrc)"
+
+# The use_devenv function supports passing flags to the devenv command
+# For example: use devenv --impure --option services.postgres.enable:bool true
+use devenv

.gitattributes

@@ -1,2 +1,18 @@
 # Auto detect text files and perform LF normalization
-* text eol=lf
+* text=auto eol=lf
+
+# Explicitly mark binary files to prevent corruption
+*.png binary
+*.jpg binary
+*.jpeg binary
+*.gif binary
+*.ico binary
+*.dll binary
+*.dylib binary
+*.so binary
+*.exe binary
+*.pdb binary
+*.ase binary
+*.aseprite binary
+*.zip binary
+# Add any other binary extensions your project uses