Cursor Composer Workflows

Overview

Structure Composer work around explicit planning, small reviewed diffs, test evidence, and rollback rather than unattended multi-file generation.

Prerequisites

• A bounded issue, affected-file inventory, repository rules, and test commands.
• A recoverable branch and reviewer for material architectural, security, or data changes.

Instructions

1. Request a plan and non-goals before any edits.
2. Apply one coherent slice at a time, review the diff, and run its focused checks.
3. Keep human decisions for API, security, migration, and dependency changes.
4. Commit validated slices and revert/split failures rather than accepting a broad repair.

Output