Add Cursor AI coding workflow enhancements

[YashBangeraXR]

Overview

This PR adds comprehensive Cursor IDE integration for enhanced AI coding workflows, including automated planning and command systems.

Changes Made

New Files Added

• .cursor/plans/scientific-calculator-3075674a.plan.md - Detailed implementation plan for scientific calculator feature
• .cursor/commands/pr.md - PR creation command template and workflow

Features Added

• Automated Planning System: Structured planning documents for complex feature implementation
• Command Templates: Reusable command patterns for common development tasks
• Enhanced Workflow: Integration between Cursor IDE and project management

Implementation Details

Scientific Calculator Plan

• Comprehensive 90-line implementation plan
• Follows project C# coding standards (m_ prefix, #region blocks, XML docs)
• Includes interface design, implementation steps, and testing strategy
• Covers trigonometric, logarithmic, power/root, and other scientific operations

PR Command Template

• Structured workflow for creating pull requests
• Includes branch preparation, description writing, and setup steps
• Template for consistent PR creation across the project

Testing

• All existing functionality preserved
• New files follow project structure
• Documentation follows project standards

Breaking Changes

None - this is purely additive functionality.

Related Issues

Enhances the AI coding workflow capabilities as outlined in the project documentation.

Checklist

• Feature: Cursor IDE integration
• Documentation: Command templates and planning system
• Manual testing: Verified file structure and content
• Code review: Follows project C# standards

[Copilot]

Pull Request Overview

This PR adds Cursor IDE integration files to enhance AI coding workflows with automated planning and command systems. The changes introduce structured documentation for implementing a scientific calculator feature and a standardized PR creation workflow.

• Adds comprehensive planning system for feature development
• Introduces command templates for consistent development workflows
• Establishes structured documentation following project C# coding standards

[Copilot]

The suggested test naming convention uses underscores, but C# best practices recommend PascalCase for test method names like MethodNameStateUnderTestExpectedBehavior or using the Given_When_Then pattern.

Suggested change

	- Follow test naming: `MethodName_StateUnderTest_ExpectedBehavior`
	- Follow test naming: `MethodNameStateUnderTestExpectedBehavior` or use the GivenWhenThen pattern in PascalCase (e.g., `GivenInput_WhenAction_ThenExpectedResult`)