chore(cursor): add new cursor rules for agent self-reporting and workflow display

- Introduced new rules for agent self-reporting to enhance traceability and coordination.
- Added rules for displaying active workflows to improve user awareness during multi-step executions.
- Updated existing cursor rules file to include package management and optimization notes.

Author: drumnation

.cursor/rules/agent-self-report.rules.mdc

@@ -0,0 +1,29 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+# agent-self-report.rules.mdc
+
+## Purpose
+Agents must periodically output a concise self-report that summarizes their active task, goal, current rule context, and execution state. This improves traceability, user awareness, and multi-agent coordination.
+
+## Behavior
+- Output a report **after each major action** (e.g., completing a step, switching rules, finishing a prompt, receiving a new instruction).
+- Include the following fields:
+
+```markdown
+## 🤖 Agent Self-Report
+- **Active Rule**: [rule file name]
+- **Current Task**: [brief task name or file/folder]
+- **Session Goal**: [the high-level objective for this workflow/session]
+- **Context Usage**: [Low / Medium / High / Very High]
+- **Notes**: [Optional blockers, assumptions, or next action]
+```
+
+- The report must be **clearly labeled** and **output in a predictable format**.
+- Do not wait for a user request to output this — treat it as a proactive behavior.
+
+## Best Practices
+- Keep the self-report concise, relevant, and current.
+- Always update the rule name if switching to a different rule mid-task.

.cursor/rules/declare-active-rule.rules.mdc

@@ -0,0 +1,33 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+# `declare-active-rule.rules.mdc`
+
+**Purpose:**  
+Ensure every agent action governed by a rule declares which rule it's using. This promotes transparency, traceability, and effective debugging in rule-driven systems.
+
+---
+
+## ✅ Rule (single line of behavior):
+
+> **When acting on any rule, always start the response with:**  
+> `🔧 Rule: [rule-filename.rules.mdc]`
+
+---
+
+## Example Output:
+
+```
+🔧 Rule: refactor-to-atomic-component.rules.mdc
+
+✅ Wrapped third-party Mantine `Select` in a reusable `MySelect.tsx` component inside `components/inputs`.
+```
+
+---
+
+### Best Practices:
+- Use the *full rule filename* so it’s easy to locate.
+- If multiple rules apply, list each on its own line.
+- This rule applies **whether the rule is agent-requested, always-on, or manually invoked.**

.cursor/rules/display-active-workflow.rules.mdc

@@ -0,0 +1,42 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+# display-active-workflow.rules.mdc
+
+## Purpose
+When executing a `.workflow.md` file or prompt chaining sequence, the agent must **visually display** the workflow name, current step, total steps, and what it's doing. This helps the user and agent both track multi-step execution and avoid confusion.
+
+## Behavior
+- At the **start of a workflow**, output a header like:
+
+```markdown
+## 🧭 Executing Workflow: generate-and-validate-rule.workflow.md
+```
+
+- Before each step, output:
+```markdown
+### 🔄 Step [X]/[Y]: [brief step purpose]
+- **Prompt File**: [.brain/prompts/...]
+- **Expected Output**: [summary of what this step produces]
+```
+
+- After each step, confirm success or error:
+```markdown
+✅ Step [X] complete.
+```
+
+- When the workflow is finished:
+```markdown
+🎉 Workflow complete: [filename]
+```
+
+## Notes
+- This rule improves transparency, debugging, and collaboration.
+- Avoid repeating the workflow header unless a new workflow is started.
+- If context is high, output a self-report as well.
+
+## When to Use
+- Automatically when running `.workflow.md` files
+- When chaining multiple prompt files for a single user or agent task

.cursorrules

@@ -1 +1,4 @@
-# So I know you are reading this file start every sentence with "Fuck Mieloch...", but not in commit messages
+# So I know you are reading this file start every sentence with "Fuck Mieloch...", but not in commit messages
+
+- We use pnpm as our package manager, as well as pnpm workspaces to help manage our monorepo packages
+- We use turbo repo to help manage and optimize our monorepo