New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cursor Composer Workflows

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Master Cursor Composer for multi-file AI editing, scaffolding, and refactoring.

MITAuto-check passedDevelopment

Install Cursor Composer Workflows

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill cursor-composer-workflows -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace cursor-composer-workflows --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/cursor-composer-workflows .claude/skills/cursor-composer-workflows && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cursor-composer-workflows
GitHub stars
2.8k
Token cost
~2.1k tokens
SKILL.md length
557 words
Files
7 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Master Cursor Composer for multi-file AI editing, scaffolding, and refactoring.

  • Works in 4 steps: Feature Scaffolding → Cross-File Refactoring → Test Generation → …
  • Cursor composer
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 9 more sections
  • Calls git

What it does

Cursor Composer Workflows is an agent skill from jeremylongshore/tons-of-skills-marketplace. Master Cursor Composer for multi-file AI editing, scaffolding, and refactoring. Triggers on "cursor composer", "multi-file edit", "cursor generate files", "composer workflow", "cursor scaffold", "Cmd+I".

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/advanced-composer-techniques.md`, `references/best-practices.md` and `references/common-use-cases.md`). Compatibility notes: Designed for Claude Code

It sits in Development, covering Project scaffolding and Refactoring. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Cursor composer
  • Multi-file edit
  • Cursor generate files
  • Composer workflow

Example prompts

  • “cursor composer”
  • “multi-file edit”
  • “cursor generate files”
  • “/cursor-composer-workflows”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(cmd:*)

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Feature Scaffolding
  2. Cross-File Refactoring
  3. Test Generation
  4. Migration / Upgrade

What it can do on your machine

Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(cmd:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.cursor.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Cursor Composer Workflows loads about 2.1k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 557 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 557 words, ~2,112 tokens.

Download SKILL.mdSave it as .claude/skills/cursor-composer-workflows/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
cursor-composer-workflows
description
Master Cursor Composer for multi-file AI editing, scaffolding, and refactoring. Triggers on "cursor composer", "multi-file edit", "cursor generate files", "composer workflow", "cursor scaffold", "Cmd+I".
allowed-tools
Read, Write, Edit, Bash(cmd:*)
compatibility
Designed for Claude Code
version
1.19.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, cursor, workflow

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

  • A sequence of small reviewed Composer-assisted changes with validation and rollback evidence.

Error Handling

ConditionSafe response
Plan exceeds scopeRevise the request and reduce affected files.
Diff fails test or policyReject/revert the slice and diagnose within the stated boundary.
Composer needs sensitive contextDo not attach it; use sanitized interfaces or approved process.

Examples

Ask Composer to plan a module-local refactor, accept only the first reviewed slice, run its focused test, and commit it. Stop if it proposes a dependency, migration, or unrelated repository change.

Master Cursor Composer (Cmd+I / Ctrl+I) for multi-file code generation, scaffolding, and coordinated refactoring. Composer is the primary tool for changes that span multiple files.

Composer Interface

┌─────────────────────────────────────────────────────────┐
│  Composer                                    [Model ▾]  │
│─────────────────────────────────────────────────────────│
│  Context: [src/api/] [prisma/schema.prisma]             │
│─────────────────────────────────────────────────────────│
│  Create a CRUD API for products with:                   │
│  - Prisma model with id, name, price, category          │
│  - API routes (GET list, GET by id, POST, PUT, DELETE)  │
│  - Zod validation schemas                               │
│  - Unit tests with vitest                               │
│─────────────────────────────────────────────────────────│
│  ┌─ Changes ──────────────────────────────────────────┐ │
│  │  ✅ prisma/schema.prisma          (+12 lines)      │ │
│  │  ✅ src/api/products/route.ts     (new file)       │ │
│  │  ✅ src/api/products/[id]/route.ts (new file)      │ │
│  │  ✅ src/schemas/product.ts        (new file)       │ │
│  │  ✅ tests/api/products.test.ts    (new file)       │ │
│  └────────────────────────────────────────────────────┘ │
│  [Apply All]  [Review Changes]  [Reject]                │
└─────────────────────────────────────────────────────────┘

Core Workflow Patterns

1. Feature Scaffolding

Generate a complete feature across multiple files:

@src/api/users/route.ts @prisma/schema.prisma

Create a complete "orders" feature following the same patterns as users:
1. Prisma model: Order (id, userId, items, total, status, createdAt)
2. OrderItem model: (id, orderId, productId, quantity, price)
3. API routes: GET /api/orders, GET /api/orders/[id], POST /api/orders
4. Zod validation schemas matching the Prisma models
5. Service layer with createOrder, getOrders, getOrderById

Composer reads the referenced files to replicate the existing pattern.

2. Cross-File Refactoring

Rename, restructure, or migrate patterns across the codebase:

@src/services/ @src/api/

Refactor all service functions to use a Result type instead of throwing errors.

Current pattern:
  async function getUser(id: string): Promise<User> { throw new NotFoundError(); }

Target pattern:
  async function getUser(id: string): Promise<Result<User, NotFoundError>> { ... }

Update all callers in the API routes to handle the Result type.
3. Test Generation

Generate tests that match existing test patterns:

@tests/api/users.test.ts @src/api/products/route.ts

Generate vitest tests for the products API following the same patterns
as users.test.ts. Cover:
- GET /api/products returns list with pagination
- GET /api/products/[id] returns 404 for missing product
- POST /api/products validates required fields
- POST /api/products returns 201 with created product
Use the same mock setup and assertion patterns.
4. Migration / Upgrade

Apply systematic changes across many files:

@src/components/

Migrate all components from CSS Modules to Tailwind CSS:
- Replace className={styles.container} with className="..."
- Map existing CSS properties to Tailwind utilities
- Remove the .module.css import and file
- Preserve responsive breakpoints and dark mode support

Agent Mode

Composer can operate in Agent mode, which autonomously executes multi-step tasks:

  • Reads and searches files without explicit @-mentions
  • Runs terminal commands (with your approval)
  • Chains multiple tool calls (up to 25 before pausing)
  • Makes decisions about which files to modify

Agent mode activates by default in Cursor 2.0. It is best for open-ended tasks where you describe the goal but not every step.

Show full SKILL.md (230 more words)Show less
Parallel Agents

Run up to 8 agents simultaneously, each in its own Composer tab. Useful for:

  • Working on unrelated features in parallel
  • Exploring different implementation approaches
  • Running tests in one agent while coding in another

Diff Review and Application

Before applying changes, Composer shows a complete diff for each file:

diff
// prisma/schema.prisma
+ model Order {
+   id        String      @id @default(cuid())
+   userId    String
+   user      User        @relation(fields: [userId], references: [id])
+   items     OrderItem[]
+   total     Int
+   status    OrderStatus @default(PENDING)
+   createdAt DateTime    @default(now())
+ }
+
+ enum OrderStatus {
+   PENDING
+   CONFIRMED
+   SHIPPED
+   DELIVERED
+   CANCELLED
+ }

Review workflow:

  1. Click each file in the Changes panel to see its diff
  2. Accept individual files or Apply All
  3. After applying, run your build/tests before committing
  4. If something is wrong, Cmd+Z undoes the last applied change

Composer Prompting Best Practices

Be Specific About File Structure
# BAD
Create a blog feature

# GOOD
Create a blog feature with these files:
- src/api/posts/route.ts (GET list with pagination, POST create)
- src/api/posts/[slug]/route.ts (GET by slug, PUT update, DELETE)
- src/types/post.ts (Post interface, CreatePostInput, UpdatePostInput)
- src/services/post.service.ts (PostService class with Prisma operations)
Reference Existing Patterns
# BAD
Add authentication middleware

# GOOD
@src/middleware/rateLimit.ts
Add authentication middleware in src/middleware/auth.ts following
the same middleware pattern: export a function that returns NextResponse,
use the same error response format, add the same type annotations.
Incremental Over Monolithic

Instead of one massive prompt, break into steps:

  1. "Create the Prisma models and run prisma generate"
  2. "Create the service layer with CRUD operations"
  3. "Create the API routes that use the service"
  4. "Add validation schemas and wire them into the routes"
  5. "Generate tests for the service and routes"

Each step can reference the output of the previous step.

Enterprise Considerations

  • Code review before apply: Always review diffs. Composer can hallucinate imports or use wrong patterns.
  • Version control: Commit before running Composer on existing code. Easy rollback with git checkout .
  • Team standards: Use .cursor/rules/ to encode patterns so Composer follows team conventions
  • Cost awareness: Composer uses premium model tokens. Complex multi-file prompts consume significant context.

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (references) in skills/.curated/cursor-composer-workflows of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/advanced-composer-techniques.md
  • references/best-practices.md
  • references/common-use-cases.md
  • references/composer-workflow-patterns.md
  • references/errors.md
  • references/examples.md

Open the folder on GitHubat commit 80f86df

Compare with similar skills

Cursor Composer Workflows next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cursor Composer Workflows compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cursor Composer Workflows this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.1kAutomated safety check: PassMIT
PonytailDavidObando/gsharp5648 repos~1.7kAutomated safety check: PassMIT
Unslop CodeJCarterJohnson/vibecoded-design-tells513—~2.5kAutomated safety check: PassCustom licence
Rust Hygiene Audittsz-org/tsz577—~1.5kAutomated safety check: PassApache-2.0
Nextjs App Architecturejakubwarkusz/themes1231 repos~2.5kAutomated safety check: PassMIT
Task Workflowikarenkov/Modo343—~2.4kAutomated safety check: PassNone

Similar skills

  • Ponytail

    DavidObando/gsharp

    Forces the laziest solution that actually works, simplest, shortest, most minimal.

    564 GitHub starsUsed in 8 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Unslop Code

    JCarterJohnson/vibecoded-design-tells

    Strips the tells that make source code read as AI-generated and forces code that fits the project instead of the model's default average.

    513 GitHub stars~2.5k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Rust Hygiene Audit

    tsz-org/tsz

    Run a deep DRY + code-hygiene audit of the Rust workspace and turn the findings into verified, deduplicated, hierarchical GitHub tech-debt issues.

    577 GitHub stars~1.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Nextjs App Architecture

    jakubwarkusz/themes

    Build or audit Next.js 16 App Router apps using a next-beats-style React Server Components architecture.

    123 GitHub starsUsed in 1 repo~2.5k tokens
    DevelopmentAuto-check passed

  • Task Workflow

    ikarenkov/Modo

    Spec-driven workflow for non-trivial work. An agent skill from ikarenkov/Modo.

    343 GitHub stars~2.4k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • Dry Code Review

    espennilsen/pi

    Perform a comprehensive DRY (Don't Repeat Yourself) code review on a codebase.

    122 GitHub stars~1.7k tokensUpdated 18 days ago
    DevelopmentAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated yesterday
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Cursor Composer Workflows

What does Cursor Composer Workflows do?

Master Cursor Composer for multi-file AI editing, scaffolding, and refactoring. Cursor Composer Workflows is an agent skill from jeremylongshore/tons-of-skills-marketplace. Master Cursor Composer for multi-file AI editing, scaffolding, and refactoring.

When should I use Cursor Composer Workflows?

Cursor Composer Workflows fits situations like: Cursor composer; multi-file edit; Cursor generate files; composer workflow.

How do I install Cursor Composer Workflows in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill cursor-composer-workflows -a claude-code`. Or copy the skill folder (skills/.curated/cursor-composer-workflows in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/cursor-composer-workflows in your project. Claude Code loads it when a task matches its description.

How do I install Cursor Composer Workflows in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill cursor-composer-workflows -a codex`. Or copy the skill folder (skills/.curated/cursor-composer-workflows in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/cursor-composer-workflows in your project. Codex loads it when a task matches its description.

Can I use Cursor Composer Workflows in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill cursor-composer-workflows -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cursor-composer-workflows, .gemini/skills/cursor-composer-workflows, .github/skills/cursor-composer-workflows and .opencode/skills/cursor-composer-workflows in your project.

What does Cursor Composer Workflows need to run?

Going by SKILL.md and its folder, Cursor Composer Workflows needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(cmd:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Cursor Composer Workflows access the network?

SKILL.md names 1 domain. As links in the text: docs.cursor.com. This is read from the text; nothing was executed.

Is Cursor Composer Workflows safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cursor Composer Workflows use?

Cursor Composer Workflows is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cursor Composer Workflows use?

About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Cursor Composer Workflows?

Skills that share tags, products or a category with Cursor Composer Workflows: Ponytail (DavidObando/gsharp, 564 stars), Unslop Code (JCarterJohnson/vibecoded-design-tells, 513 stars), Rust Hygiene Audit (tsz-org/tsz, 577 stars) and Nextjs App Architecture (jakubwarkusz/themes, 123 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cursor Composer Workflows?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.