Skip to main content

Overview

Meta packages are packages that teach AI how to create other packages. They’re “prompts about writing prompts” - expert guidance that helps AI assistants generate high-quality, well-structured PRPM packages. Think of them as:
  • Package creation templates
  • Style guides for AI prompts
  • Best practices for package structure
  • Quality standards enforcement

Why Meta Packages Matter

AI assistants are great at generating content, but they need guidance to produce consistently high-quality packages that follow PRPM conventions. Without meta packages:
  • ❌ Inconsistent package structures
  • ❌ Poor CSO (Context Search Optimization)
  • ❌ Missing required fields
  • ❌ Unclear when to use packages
  • ❌ No real-world examples
With meta packages:
  • ✅ Standardized structure across all packages
  • ✅ Optimized for AI discovery and use
  • ✅ Complete metadata and documentation
  • ✅ Clear triggering conditions
  • ✅ Real examples and patterns

PRPM’s Meta Packages

PRPM uses meta packages to maintain consistency across its own repository. These packages teach AI assistants how to create high-quality packages for each IDE format.

Format-Specific Creation Packages

PRPM provides specialized packages for creating packages in each supported format. Each format has both a Claude skill (for explicit invocation) and a Cursor rule (for intelligent context application). Quick Reference:

Cursor Format

Creating Cursor Rules:
Teaches AI how to create Cursor rules with MDC format, frontmatter fields, rule types (Always Apply, Apply Intelligently, Apply to Specific Files, Apply Manually), and glob patterns.
Creating Cursor Commands:
Teaches AI how to create Cursor slash commands using plain markdown (NO frontmatter), descriptive filenames, and clear actionable instructions.

Claude Code Format

Creating Claude Skills:
Teaches AI how to create Claude Code skills with proper frontmatter, CSO optimization, when to trigger, and real examples.
Creating Claude Agents:
Teaches AI how to create Claude Code agents with persona definition, allowed-tools, model selection, and long-running assistant patterns.
Creating Claude Commands:
Teaches AI how to create Claude Code slash commands with optional frontmatter (allowed-tools, argument-hint, description, model, disable-model-invocation).
Creating Claude Hooks:
Teaches AI how to create Claude Code hooks as executable files (shell scripts, TypeScript) with event handling (session-start, user-prompt-submit, tool-call, assistant-response), JSON I/O, and security best practices.

Other Formats

Continue Rules:
Teaches AI how to create Continue rules with required frontmatter (name field is required), globs, regex, and alwaysApply behavior.
Windsurf Rules:
Teaches AI how to create Windsurf rules using plain markdown with 12K character limit, hierarchical structure, and minimalist approach.
GitHub Copilot:
Teaches AI how to create GitHub Copilot instructions and chatmodes in .github/ directory with markdown format.
Kiro Steering:
Teaches AI how to create Kiro steering files with inclusion modes (always, fileMatch, manual), foundational files (product.md, tech.md, structure.md), and domain organization.
Agents.md:
Teaches AI how to create agents.md files using plain markdown (NO frontmatter) with comprehensive project context documentation.

Legacy Meta Packages

These meta packages provide broader guidance: Slash Command Builder (@prpm/slash-command-builder-skill):
Comprehensive guidance for Claude Code slash commands with multiple reference files (SKILL.md, EXAMPLES.md, FRONTMATTER.md, PATTERNS.md).
Agent Builder (@prpm/agent-builder-skill):
Comprehensive guidance for Claude Code subagents with system prompt design, tool access, model selection, and delegation patterns.

Creating Your Own Meta Package

Example: Package Creator for Python

Let’s create a meta package that teaches AI to generate Python-specific packages:
Why it works: [Explanation]
Why it works: FastAPI calls get_db() automatically, handles cleanup
Save as .claude/skills/python-package-creator/SKILL.md and publish:

Real-World Use Case: PRPM’s Own Development

PRPM uses meta packages to generate its internal packages. Here’s the workflow:

1. Install Meta Package

2. Create Package

3. Publish Package

4. Share with Community

The generated package is now available in the PRPM registry for others to use.

Meta Package Patterns

Pattern 1: Template-Based Generation

Provide a complete template with placeholders:

Pattern 3: CSO Optimization

Teach AI to optimize for searchability:

Pattern 4: Format-Specific Guidance

Different AI editors need different formats:

Advanced: Self-Generating Meta Packages

Meta packages can teach AI to create more meta packages:
This creates a recursive improvement loop:
  1. Meta package teaches AI to create packages
  2. Those packages teach AI domain expertise
  3. Domain expertise helps users solve problems
  4. Users share new patterns back to packages

Testing Meta Packages

Before publishing, test that your meta package actually works:

1. Install the Meta Package

2. Generate a Package

3. Verify Output Quality

  • Proper structure and frontmatter
  • Real, working code examples
  • Clear triggering conditions
  • Good CSO keywords
  • Complete metadata

4. Iterate

If output is poor, improve the meta package’s guidance.

Best Practices

1. Provide Complete Templates

Show exactly what good packages look like, with all sections filled in.

2. Use Real Examples

Don’t use placeholder text. Show actual packages from the registry as examples.

3. Enforce Standards

Include checklists and requirements that AI must follow.

4. Optimize for Discovery

Teach AI to include CSO keywords that users will actually search for.

5. Version Your Guidance

As PRPM evolves, update meta packages to reflect new best practices.

Common Pitfalls

❌ Too Abstract

✅ Specific and Actionable

❌ Generic Examples

✅ Real, Tested Code