Skip to main content

Formats

PRPM supports multiple AI tool formats, allowing you to install packages for different IDEs and development environments.

Supported Formats

Format Aliases

Some formats have aliases for compatibility:
  • claude.mdclaude
  • gemini.md → installs GEMINI.md (Gemini markdown); gemini installs Gemini CLI commands into .gemini/commands

Cursor Format Details

The cursor format supports multiple subtypes:
  • Rules (subtype: rule): Project guidelines in .cursor/rules/*.mdc with MDC frontmatter (description, globs, alwaysApply)
  • Slash Commands (subtype: slash-command): Custom commands in .cursor/commands/*.md
  • Hooks (subtype: hook): Event-triggered scripts configured in hooks.json
  • Plugins (subtype: plugin): Bundles of rules, skills, agents, commands, hooks, and MCP servers defined by a .cursor-plugin/plugin.json manifest
Plugins are the most comprehensive package type for Cursor, containing multiple components in a single distributable unit. The plugin.json manifest requires only a name field and optionally includes description, version, author, keywords, logo, and paths to component directories.
Cursor plugins are available via the Cursor Marketplace. See the official plugin docs for full details.

Copilot Format Details

The copilot format supports three subtypes:
  • Rules (subtype: rule): Path-specific instructions in .github/instructions/*.instructions.md
  • Chat Modes (subtype: chatmode): Custom chat modes in .github/chatmodes/*.chatmode.md
  • Skills (subtype: skill): Reusable task-specific capabilities in .github/skills/<name>/SKILL.md
Skills are discovered by Copilot based on context and loaded when relevant. Each skill requires:
  • A name field (lowercase, hyphens for spaces, max 64 chars)
  • A description field (max 1024 chars)
  • Markdown body with detailed instructions
Skills require VS Code Insiders with the chat.useAgentSkills setting enabled.

Gemini Format Details

The gemini format supports two subtypes:
  • Slash Commands (subtype: slash-command): Custom commands defined in .toml files, installed to .gemini/commands/
  • Extensions (subtype: extension): Full extensions with MCP servers and context files, installed to .gemini/extensions/<name>/gemini-extension.json
Extensions support:
  • MCP (Model Context Protocol) server configurations
  • Custom context files
  • Tool exclusions
  • Experimental settings

MCP Format Details

The mcp format is for MCP (Model Context Protocol) server packages. Use subtype: tool. When installed, PRPM reads the mcpServers object from your package’s JSON file and merges each server entry into the user’s editor config. This works across 11 editors — Claude Code, Cursor, VS Code, Codex, Windsurf, Gemini, Kiro, OpenCode, Trae, Amp, and Zed. Your package file should be a JSON file with a mcpServers object:
mcp-server.json
See the MCP Servers guide for full publishing and installation details.

Installing for Specific Formats

Auto-detect format from your project:
Specify a format explicitly:

Format Detection

PRPM auto-detects the format based on your project structure:
  • .claude/ directory → claude
  • .cursor/ directory → cursor
  • .continue/ directory → continue
  • .windsurf/ directory → windsurf
  • .kiro/ directory → kiro
  • .agents/ directory → agents.md
  • .ruler/ directory → ruler
  • .opencode/ directory → opencode
  • .factory/ directory → droid
  • .trae/ directory → trae
  • .aider/ or CONVENTIONS.md file → aider
  • .zencoder/ directory → zencoder
  • .replit/ directory or .replit file → replit
  • .mcp/ directory → mcp

File Installation Paths

Each format has a standard installation path:

Multi-Format Packages

Some packages support multiple formats. PRPM will install the appropriate version based on your environment:

Next Steps

Packages

Learn more about packages

Publishing Guide

Publish multi-format packages