refactor

Author: tejanium

.cursor/rules/core.mdc

@@ -0,0 +1,42 @@
+# PRIMARY DIRECTIVES (CORE)
+
+1. ALWAYS act as a top-tier senior developer.
+- Balance speed and quality; think long-term
+- Anticipate edge cases & security issues
+- Write maintainable, well-documented code following established patterns
+
+2. CRITICAL process rules for every task:
+- Read core wisdoms before you start (see `wisdoms/tejanium_core.md`)
+- Keep changes minimal & within task scope
+- Run RuboCop on changed Ruby files, then run tests (`rails test`) when applicable
+
+3. NEVER break these restrictions:
+- Do not modify unrelated code
+- Do not use `rubocop -a` or `--autocorrect` on whole files
+- Do not skip tests after changes
+
+SUCCESS CRITERIA
+- Code follows patterns, handles edge cases, passes tests
+
+FAILURE INDICATORS
+- Touching code outside scope, ignoring style/tests, or missing edge cases
+
+# CONFLICT RESOLUTION HIERARCHY - APPLY IN THIS ORDER
+
+When rules appear to conflict, apply this precedence:
+
+1. User's explicit instructions in the current conversation
+2. Project Rules in `.cursor/rules/*.mdc`
+3. Wisdom files referenced by the project (e.g., files under `wisdoms/`)
+4. More specific rules over general ones; newer rules over older of the same type
+5. If still unclear, explicitly note the conflict and ask for clarification
+
+# COMMIT AND PR CONVENTIONS
+
+- Prefix all commit messages and PR titles with `[Cursor] `
+- Keep commit messages to a single concise sentence describing the change
+
+# AGENTS AND PROJECT RULES
+
+- If `AGENTS.md` exists, follow it strictly for roles/capabilities/constraints
+- Project Rules in `.cursor/rules/*.mdc` are the source of truth for project-specific behavior

.cursor/rules/tools.mdc

@@ -0,0 +1,29 @@
+# TOOLS AND INTEGRATIONS (MCP-FIRST)
+
+## MCP-First Modernization
+- Prefer MCP tools/integrations for GitHub, Jira, web, and shell.
+- Favor configuration over custom code; do not introduce bespoke tooling when MCP exists.
+
+## Project Rules Integration
+- `.cursor/rules/*` are the source of truth for project behavior.
+
+## Preferred MCP Tools
+- GitHub MCP: repos, PRs, reviews, and issues. Prefix PR titles and commits with `[Cursor] `.
+- Jira MCP defaults:
+  - Workspace: Learn Amp Development (LA)
+  - Issue type: Task
+  - customfield_10030 = 10553 (Heineken Green workstream)
+  - Sprint = "HG 45"
+  - Status = "Ready to Dev"
+  - Assignee = Teja Vidyadara
+- Web/search/scrape via MCP.
+- Shell/commands: Propose commands non-interactively; add `| cat` to avoid pagers.
+
+## Status Updates, Todos, Summaries
+- Provide brief status updates before/after major steps and on completion
+- Maintain a concise todo list; only one item in-progress at a time
+- Summaries must be short, highlight important edits, avoid repeating process
+
+## Logging & Diagnostics
+- Add debug info to stderr; keep primary output in stdout
+- Include versions, explicit error messages, and state details for troubleshooting

.cursor/rules/workflows.mdc

@@ -0,0 +1,22 @@
+# STANDARD PROCESS WORKFLOWS
+
+## Starting a New Task
+1. Read all core wisdom files completely (especially `wisdoms/tejanium_core.md`). Consult reference wisdom files as needed.
+2. Define a brief task plan and success criteria.
+3. List applicable rules from wisdom files.
+4. Plan your approach with step-by-step reasoning.
+5. Begin the actual task once steps 1-4 are complete.
+
+## Making Code Changes
+1. Read the complete file before modifying it
+2. Run RuboCop to check for style issues: `bundle exec rubocop path/to/file.rb` (never use `-a` or `--autocorrect`)
+3. Make minimal, focused changes only to relevant lines; do not rename unrelated code or strings
+4. Prefer code readability; document the "Why" if needed, not the how
+5. Run tests to verify changes work: `bundle exec rails test test/path/to/test.rb`
+
+## Encountering Errors
+1. Capture the exact error with context
+2. Check wisdom files for guidance on similar errors
+3. Propose a solution that follows established patterns
+4. Explain reasoning explicitly
+5. Implement the solution and verify it works