Execute master Cursor Composer for multi-file AI edits. Triggers on "cursor composer", "multi-file edit", "cursor generate files", "composer workflow", "cursor scaffold". Use when working with cursor composer workflows functionality. Trigger with phrases like "cursor composer workflows", "cursor workflows", "cursor".
Scanned 2/12/2026
Install via CLI
openskills install jeremylongshore/claude-code-plugins-plus-skills---
name: "cursor-composer-workflows"
description: |
Execute master Cursor Composer for multi-file AI edits. Triggers on "cursor composer",
"multi-file edit", "cursor generate files", "composer workflow", "cursor scaffold". Use when working with cursor composer workflows functionality. Trigger with phrases like "cursor composer workflows", "cursor workflows", "cursor".
allowed-tools: "Read, Write, Edit, Bash(cmd:*)"
version: 1.0.0
license: MIT
author: "Jeremy Longshore <jeremy@intentsolutions.io>"
---
# Cursor Composer Workflows
## Overview
This skill helps you master Cursor Composer for multi-file AI edits. It provides workflow patterns for feature generation, scaffolding, refactoring, and incremental building to maximize your productivity with Composer.
## Prerequisites
- Cursor IDE with Composer feature access
- Project workspace with existing code patterns
- Understanding of multi-file editing workflows
- Configured .cursorrules for project standards
## Instructions
1. Open Composer (Cmd+I or Ctrl+I)
2. Describe the files and changes needed
3. Use @-mentions to reference existing patterns
4. Specify file structure preferences
5. Review all proposed changes
6. Apply changes and test
## Output
- Multi-file code generation
- Coordinated feature implementation
- Pattern-consistent scaffolding
- Refactored codebase
## Error Handling
See `{baseDir}/references/errors.md` for comprehensive error handling.
## Examples
See `{baseDir}/references/examples.md` for detailed examples.
## Resources
- [Composer Documentation](https://cursor.com/docs/composer)
- [Multi-File Workflows](https://cursor.com/docs/workflows)
- [Cursor Best Practices](https://cursor.com/docs/best-practices)
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.