Configuration rules for using DeepSeek models within Cursor IDE, including agent mode setup, file handling, and code generation guidelines.
## DeepSeek + DeepSeek Integration Rules ### Model Configuration - Use deepseek-v3 for general coding tasks (hosted on Fireworks.ai via DeepSeek) - Use deepseek-r1 for complex reasoning, debugging, and architecture decisions - Set temperature to 0.6 for consistent results - For API integration: Settings > Models > Add your Claude API key ### Agent Mode Rules - Always add or update tests for code changes - Do not output or exfiltrate API keys or secrets - Verify file existence before modifying - Use relative paths within the project - Run linting after code generation ### Code Generation Guidelines - Respect existing code style and conventions in the project - Match indentation (tabs vs spaces) of surrounding code - Use existing utility functions rather than creating duplicates - Prefer editing existing files over creating new ones - Include TypeScript types when working in .ts/.tsx files ### File Operations - Read files before editing to understand existing patterns - Never delete files without explicit instruction - Create new files only when they do not exist as part of the current architecture - Use project-relative imports consistent with the existing codebase ### Testing - Add tests for new functions and modified behavior - Use the project's existing test framework - Place test files in the project's established test directory structure
Workflows from the Neura Market marketplace related to this DeepSeek resource