Add initial configuration files and update implementation guidelines

Author: regenrek

.cursor/000-base.mdc

@@ -0,0 +1,5 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---

.cursor/rules/modes/implement.mdc

@@ -18,10 +18,8 @@ Follow these guidelines:
 
 2. If you haven't done so read all related cursor rules for the task.
 
-3. Read [feat-agent.mdc](mdc:.cursor/rules/modes/feat-agent.mdc) that you learn about the architecture and how to add a feature.
+3. Procenting the current story `.planr/stories/{{STORY-ID}}`, ensuring you address all acceptance criteria.
 
-4. Proceed with implementing the current story `.planr/stories/{{STORY-ID}}`, ensuring you address all acceptance criteria.
+4. write all infos about updates, fixes, to the "Developer Notes" section in `.planr/stories/{{STORY-ID}}`. Do the same in @roadmap.json in `notes` but keep it for the 10 most important max.
 
-5. write all infos about updates, fixes, to the "Developer Notes" section in `.planr/stories/{{STORY-ID}}`. Do the same in [roadmap.json](mdc:.planr/roadmap.json) in `notes` but keep it for the 10 most important max.
-
-6. ask if you should proceed wit the next story
+5. ask if you shouldthe next story

.cursor/rules/modes/plan.mdc

@@ -4,10 +4,11 @@ globs:
 alwaysApply: false
 ---
 
-You are Olena, a specialized product planner, requirements engineer AI agent. 
+You are Lena, a specialized product planner, requirements engineer AI agent. 
 
 Rules:
 - Writing Style: No fluff, only the essential information—short as possible without losing details.
+- MUST NOT use any bold text. Do not use asterisks (e.g., **text**) or any other form of bold styling in your output.
 
 You have two modes:
 
@@ -23,24 +24,48 @@ Your working directory and file structure:
             {STORY-ID}.md
     roadmap.json # follow this step by step
     assetlist.json # models, sounds, textures
-    prd.md # product requirements document
+    # product requirements document
 ```
 
 <modes>
-    <init>
-        Your task is to create all stories bsed on the [prd.md](mdc:.planr/prd.md) file.
-        
+    <init>      
+ ap_rul         # Phase 1: Requirements & Architecture Setup
+           overall goaraints from PRD.md, SRS.md.
+            - Clarify architecture for the project (no full infrastructure setup needed).
+            
+            # Phase 2: Iterative Feature Development
+                    For each story below, follow these steps:
+
+            1. Technical Spike  
+        f a feasibile to verify assumptions.
+            
+            2. Data Model Design (if needed)  
+            - Define any new tables or fields in Schema.md.  
+            - Add initial data to avoid empty table errors.
+            
+            3. API and Backend (if needed)
+            - Implement or update API endpoints as referenced in 
+            
+            4. Frontend Implementation  
+            - Develop or update user-facing components per prd
+            
+            5. Refine User Experience  
+            - Address usability and consistency issues.
+        </roadmap_rules>
+			
         STEPS:
-        1. Create a story using [story.tpl.md](mdc:.cursor/templates/story.tpl.md) from [prd.md](mdc:.planr/prd.md) in the format `.planr/stories/{STORY-ID}.md`
-        2. Update [roadmap.json](mdc:.planr/roadmap.json) list using [task.tpl.md](mdc:.cursor/templates/task.tpl.md) based on the story
-        3. Proceed with next story
+        1. Review all relevant documents to gather requirements and constraints: @prd.md @tech-stack.md @api.md
+        2. Create a story using @story.tpl.md from the given PRD in the format `.planr/stories/{STORY-ID}.md`
+        3. Update @roadmap.json list using @task.tpl.md based on the story and you MUST follow <roadmap_rules />
+        4. Proceed with next story
     </init>
 
     <add>
         Your task is to create a new story based on the given input
 
         STEPS:
-        1. Create a new story using [story.tpl.md](mdc:.cursor/templates/story.tpl.md) based on the given input and save it to `.planr/stories/{STORY-ID}.md`
-        3. Update [roadmap.json](mdc:.planr/roadmap.json) list using [task.tpl.md](mdc:.cursor/templates/task.tpl.md) based on the story
+        1. Create a new story using @story.tpl.md based on the given input and save it to `.planr/stories/{STORY-ID}.md`
+        3. Update @roadmap.json list using @task.tpl.md based on the story
     </add>
-</modes>
+</modes>
+

.cursor/templates/story.tpl.md

@@ -1,9 +1,3 @@
----
-description: 
-globs: .planr/stories/**/*.md
-alwaysApply: false
----
-
 Use this template to create a new story for tracking in the `docs/stories` directory. 
 
 # User Story: {{ID}} - {{TITLE}}
@@ -27,16 +21,6 @@ As a {{USER_TYPE}}, I want {{FEATURE}} so that {{REASON}}.
    1. - [ ] {Test Subtasks (as needed)}
    2. - [ ] {Subtask}
 
-## ECS Implementation Tasks:
-
-- [ ] Traits: Define marker trait (IsFeature) and data traits with appropriate defaults
-- [ ] Systems: Create system file with proper entity queries and delta time handling
-- [ ] Actions: Add spawn function to actions.ts with all required traits
-- [ ] Renderer: Create component with useTraitEffect for proper entity visualization
-- [ ] Integration: Add system to frameloop.ts in correct order
-- [ ] Startup: Store entity references and implement cleanup in useEffect
-- [ ] Testing: Verify system behavior and ensure proper cleanup 
-
 Note:
 - Use - [x] for completed items
 - Use ~~skipped/cancelled items~~

.cursor/templates/task.tpl.md

@@ -1,9 +1,3 @@
----
-description: use this ALWAYS to create/update a task in json
-globs: .planr/roadmap.json
-alwaysApply: false
----
-
 Use the following JSON to add a task
 
 ```json

.cursorignore

@@ -0,0 +1 @@
+docs/archive