cursor-advanced-composer
Advanced Cursor Composer techniques for complex edits. Triggers on "advanced composer","composer patterns", "multi-file generation", "composer refactoring".
When & Why to Use This Skill
This Claude skill optimizes the use of Cursor's Advanced Composer for complex, multi-file code editing and generation. It enables developers to execute large-scale architecture migrations, pattern replication, and coordinated file changes with high precision. By leveraging specific triggers and best practices, it streamlines the development workflow, ensures consistent code patterns, and provides robust quality control for AI-driven software engineering.
Use Cases
- Large-scale Refactoring: Efficiently migrating project architectures or updating coding patterns across dozens of files simultaneously with coordinated edits.
- Feature Scaffolding: Rapidly generating complete feature modules, including UI components, business logic, and API integrations, in a single automated workflow.
- Pattern Replication: Maintaining codebase consistency by replicating existing design patterns and boilerplate across new files using context-aware @-mentions.
- Quality Control & Testing: Ensuring all AI-generated code follows specified naming conventions and includes comprehensive test coverage through incremental application and review.
| name | "cursor-advanced-composer" |
|---|---|
| description | | |
| allowed-tools | "Read, Write, Edit, Bash(cmd:*)" |
| version | 1.0.0 |
| license | MIT |
| author | "Jeremy Longshore <jeremy@intentsolutions.io>" |
Cursor Advanced Composer
Overview
This skill covers advanced Cursor Composer techniques for complex multi-file edits. It provides patterns for coordinated file creation, architecture migrations, pattern replication, and quality control workflows for large-scale code generation.
Prerequisites
- Cursor IDE with Composer feature access
- Understanding of project structure and patterns
- Well-configured .cursorrules file
- Indexed codebase for @-mention references
Instructions
- Open Composer with Cmd+I (Mac) or Ctrl+I (Windows)
- Describe the feature or changes needed
- Reference existing patterns with @-mentions
- Specify file structure and naming conventions
- Review each proposed change before applying
- Apply changes incrementally, testing between phases
Output
- Multiple coordinated file changes
- Generated feature modules with consistent patterns
- Refactored codebase following specified patterns
- Complete test coverage for generated code
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.