Package Creator

Create Packmind packages—logical collections of standards, commands, and skills that can be distributed together.

About Packages

A Package groups related artifacts by technology, domain, team, or architectural layer. Instead of managing individual items, packages let you distribute related content as a single unit.

Examples: frontend, backend-api, nestjs, e2e

Prerequisites

Verify packmind-cli is available:

packmind-cli --version

If not installed:

npm install -g @packmind/cli
packmind-cli login

Workflow

Step 1: Check Existing Packages

List existing packages to identify naming conventions:

packmind-cli install --list

Review the output to:

• Avoid duplicate or conflicting names
• Follow existing naming conventions (lowercase, kebab-case slugs)
• Understand how packages are organized in this workspace

Step 2: Confirm with User

Before creating, confirm the package details:

Package name: <name>
Description: <description or "none">

Proceed?

Wait for explicit user approval.

Step 3: Create the Package

Run the CLI command:

packmind-cli packages create "<name>" --description="<description>" --origin-skill=create-package

Or without description:

packmind-cli packages create "<name>" --origin-skill=create-package

Expected Output

On success:

Created: <slug>
You can see it at: https://<host>/packages/<slug>
You can install it with: packmind-cli packages install <slug>

Naming Guidelines

• Name: Human-readable, can include spaces (e.g., "Backend API")
• Slug: Auto-generated from name, lowercase with hyphens (e.g., "backend-api")
• Collision handling: If slug exists, server auto-increments (e.g., "frontend-2")

Troubleshooting

Next Steps

After creating a package, content can be added via:

1. MCP tools: Use packageSlugs parameter when creating standards/commands
2. Web interface: Navigate to the package URL and add items manually