Cursor Rule: Bulk Processing
optics/cursor-rule-bulk-processingFreeUtility
Cursor rule file for bulk processing guidelines.
See it running
Open the demo on optics
optics.agusmayol.com.ar/components/cursor-rule-bulk-processingInstall it
npx shadcn@latest add https://optics.agusmayol.com.ar/r/cursor-rule-bulk-processing.jsonSource
1---2description: Rules for heavy tasks optimization3globs: *4alwaysApply: false5---6# Cursor Heavy Tasks Optimization Rules78## Core Principles910Work directly and efficiently. Complete tasks in the most straightforward way possible without adding unnecessary complexity or intermediate steps.1112## File Operations1314Update files one at a time in sequential order. Never create scripts, automation tools, or batch processors to handle file updates.1516Make direct edits to each file. Open, modify, save. Repeat for the next file.1718When updating multiple files, work through them systematically in a logical order (alphabetical, by directory structure, or by dependency order).1920Avoid creating helper utilities or migration scripts. The overhead of creating and maintaining these tools exceeds the benefit for most tasks.2122## Batch Processing2324Process related changes in batches by type, not by creating automation.2526Example: If updating imports across 20 files, update all imports in file 1, then all imports in file 2, etc. Don't create a script to find and replace imports.2728Group similar edits mentally and apply them consistently across files, but execute them manually.2930## Task Breakdown3132Break large refactoring tasks into logical chunks: files in one directory, then another directory, then another.3334Complete one chunk fully before moving to the next. Don't partially update everything.3536When updating 50+ files, consider breaking the work into multiple sessions rather than creating automation.3738## No Script Creation Policy3940Never suggest creating Python scripts, Node.js scripts, or shell scripts to automate repetitive file changes.4142Never suggest creating temporary utilities, helpers, or tools to process multiple files.4344Never propose regex-based find-and-replace scripts across the codebase.4546The exception: Build tools, linters, or formatters that are permanent parts of the project infrastructure.4748## Efficiency Without Automation4950Use your text editing capabilities directly. You can see and modify multiple files efficiently without scripts.5152Leverage pattern recognition to work faster, but still process files individually.5354Keep track of progress mentally or through comments in chat, not through generated checklists or tracking scripts.5556## When Working with Many Files5758For 5-10 files: Update them all directly, one by one.5960For 10-30 files: Update them in batches of 5-10, taking breaks between batches.6162// … truncated
Files it writes
More from optics
All 79 items| Component | Registry | Kind | Access | Installs | Command |
|---|---|---|---|---|---|
| Cursor Rule: Back Endcursor-rule-back-end | optics | Utilities | Free | no deps | |
| Cursor Rule: Commits Conventioncursor-rule-commits-convention | optics | Utilities | Free | no deps | |
| Cursor Rule: Front Endcursor-rule-front-end | optics | Utilities | Free | no deps | |
| Cursor Rule: Generalcursor-rule-general | optics | Utilities | Free | no deps | |
| Cursor Rule: React Optimizationcursor-rule-react-optimization | optics | Utilities | Free | no deps | |
| Cursor Rule: Web Interface Guidelinescursor-rule-web-interface-guidelines | optics | Utilities | Free | no deps | |
| Get strict contextget-strict-context | optics | Utilities | Free | no deps | |
| Use auto heightuse-auto-height | optics | Utilities | Free | no deps |
