adding-new-ai-format

Automate adding new AI editor formats across PRPM types, schemas, converters, and testing.

121|16|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/pr-pm/prpm --skill adding-new-ai-format
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adding-new-ai-format
Source: https://github.com/pr-pm/prpm/tree/main/.claude/skills/adding-new-ai-format
Command: npx skills add https://github.com/pr-pm/prpm --skill adding-new-ai-format

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the complexity and guesswork when adding new AI editor format support to PRPM, providing a complete step-by-step implementation roadmap.

Core Features & Use Cases

  • Comprehensive Integration: Covers all 6 PRPM packages - types, converters, CLI, webapp, registry, and testing.
  • Use Case: Imagine your team needs to add support for a new AI editor like OpenCode. Use this Skill to systematically implement the format across types, schemas, converters, and UI components.
  • Developer Workflow: Provides exact code examples, file locations, and build commands for seamless format integration.

Quick Start

Use this skill to understand the complete process for adding OpenCode format support to PRPM, including schema creation, converter implementation, and registry updates.

Frequently Asked Questions about adding-new-ai-format

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new AI editor format to PRPM?

Adding a new AI editor format to PRPM requires updating TypeScript types, generating JSON schemas with proper `$id` patterns, implementing converters, and wiring canonical types across all 6 packages: types, converters, CLI, webapp, registry, and testing.

What files and packages need updates when integrating a new format like OpenCode?

Format integration spans 6 PRPM packages: update the Format union and FORMATS array in types, create JSON schemas with `additionalProperties` constraints, add format-specific metadata, implement converters, update the CLI and webapp, register in the registry, and add corresponding test coverage.

What schema requirements apply to new AI editor formats in PRPM?

JSON schemas for new formats must include the required `$id` pattern matching PRPM conventions and enforce `additionalProperties` constraints to maintain schema consistency and validation across all supported editor formats.

Can I use this guidance for formats beyond OpenCode and Cursor?

Yes, this systematic approach applies to adding any AI editor format—whether OpenCode, Cursor, Claude, or others—by following the same integration pattern across types, converters, schemas, CLI, webapp, and testing.

What's the complete end-to-end process for format support in PRPM?

End-to-end format support requires defining TypeScript union types, generating conformant JSON schemas, building format-specific converters, wiring canonical type conversions, updating CLI and UI components, registering the format, and implementing comprehensive test coverage.

Do I need converter implementation for each new format added to PRPM?

Yes, adding format support requires implementing converters and canonical type wiring to enable bidirectional translation between the new format and PRPM's internal representation across all integration points.