The personal finance app for everyone
Taskmaster Stubbing (#2313)
Josh Pigford07ca33f2f44d
diff --git a/.cursor/rules/cursor_rules.mdc b/.cursor/rules/cursor_rules.mdcnew file mode 100644index 00000000..7dfae3de--- /dev/null+++ b/.cursor/rules/cursor_rules.mdc@@ -0,0 +1,53 @@+---+description: Guidelines for creating and maintaining Cursor rules to ensure consistency and effectiveness.+globs: .cursor/rules/*.mdc+alwaysApply: true+---++- **Required Rule Structure:**+ ```markdown+ ---+ description: Clear, one-line description of what the rule enforces+ globs: path/to/files/*.ext, other/path/**/*+ alwaysApply: boolean+ ---++ - **Main Points in Bold**+ - Sub-points with details+ - Examples and explanations+ ```++- **File References:**+ - Use `[filename](mdc:path/to/file)` ([filename](mdc:filename)) to reference files+ - Example: [prisma.mdc](mdc:.cursor/rules/prisma.mdc) for rule references+ - Example: [schema.prisma](mdc:prisma/schema.prisma) for code references++- **Code Examples:**+ - Use language-specific code blocks+ ```typescript+ // ✅ DO: Show good examples+ const goodExample = true;++ // ❌ DON'T: Show anti-patterns+ const badExample = false;+ ```++- **Rule Content Guidelines:**+ - Start with high-level overview+ - Include specific, actionable requirements+ - Show examples of correct implementation+ - Reference existing code when possible+ - Keep rules DRY by referencing other rules++- **Rule Maintenance:**+ - Update rules when new patterns emerge+ - Add examples from actual codebase+ - Remove outdated patterns+ - Cross-reference related rules++- **Best Practices:**+ - Use bullet points for clarity+ - Keep descriptions concise+ - Include both DO and DON'T examples+ - Reference actual code over theoretical examples+ - Use consistent formatting across rules\ No newline at end of filediff --git a/.cursor/rules/self_improve.mdc b/.cursor/rules/self_improve.mdcnew file mode 100644index 00000000..40b31b6e--- /dev/null+++ b/.cursor/rules/self_improve.mdc@@ -0,0 +1,72 @@+---+description: Guidelines for continuously improving Cursor rules based on emerging code patterns and best practices.+globs: **/*+alwaysApply: true+---++- **Rule Improvement Triggers:**+ - New code patterns not covered by existing rules+ - Repeated similar implementations across files+ - Common error patterns that could be prevented+ - New libraries or tools being used consistently+ - Emerging best practices in the codebase++- **Analysis Process:**+ - Compare new code with existing rules+ - Identify patterns that should be standardized+ - Look for references to external documentation+ - Check for consistent error handling patterns+ - Monitor test patterns and coverage++- **Rule Updates:**+ - **Add New Rules When:**+ - A new technology/pattern is used in 3+ files+ - Common bugs could be prevented by a rule+ - Code reviews repeatedly mention the same feedback+ - New security or performance patterns emerge++ - **Modify Existing Rules When:**+ - Better examples exist in the codebase+ - Additional edge cases are discovered+ - Related rules have been updated+ - Implementation details have changed++- **Example Pattern Recognition:**+ ```typescript+ // If you see repeated patterns like:+ const data = await prisma.user.findMany({+ select: { id: true, email: true },+ where: { status: 'ACTIVE' }+ });++ // Consider adding to [prisma.mdc](mdc:.cursor/rules/prisma.mdc):+ // - Standard select fields+ // - Common where conditions+ // - Performance optimization patterns+ ```++- **Rule Quality Checks:**+ - Rules should be actionable and specific+ - Examples should come from actual code+ - References should be up to date+ - Patterns should be consistently enforced++- **Continuous Improvement:**+ - Monitor code review comments+ - Track common development questions+ - Update rules after major refactors+ - Add links to relevant documentation+ - Cross-reference related rules++- **Rule Deprecation:**+ - Mark outdated patterns as deprecated+ - Remove rules that no longer apply+ - Update references to deprecated rules+ - Document migration paths for old patterns++- **Documentation Updates:**+ - Keep examples synchronized with code+ - Update references to external docs+ - Maintain links between related rules+ - Document breaking changes+Follow [cursor_rules.mdc](mdc:.cursor/rules/cursor_rules.mdc) for proper rule formatting and structure.diff --git a/.gitignore b/.gitignoreindex eeb5e8f2..95c60508 100644--- a/.gitignore+++ b/.gitignore@@ -70,4 +70,36 @@ node_modulescompose.yml-plaid_test_accounts/\ No newline at end of file+plaid_test_accounts/++# Added by Claude Task Master+# Logs+logs+*.log+npm-debug.log*+yarn-debug.log*+yarn-error.log*+dev-debug.log+# Dependency directories+node_modules/+# Environment variables+.env+# Editor directories and files+.vscode+*.suo+*.ntvs*+*.njsproj+*.sln+*.sw?+*.roo*+# OS specific+# Task files+tasks.json+tasks/+*.mcp.json+scripts/+.cursor/mcp.json+.taskmasterconfig+.windsurfrules+.cursor/rules/dev_workflow.mdc+.cursor/rules/taskmaster.mdc