Using Bundles Forge

This is the entry point for the entire bundles-forge system. It loads automatically and routes you to the right specialized skill based on what you're doing: blueprinting new plugins, scaffolding structure, authoring content, auditing quality, testing locally, optimizing existing work, or releasing. It handles the pre-flight check to confirm you're in a bundle-plugin project, explains how skills work across different platforms (Claude Code, Cursor, Gemini, Codex, OpenClaw), and enforces a simple rule: invoke the relevant skill before doing anything. Think of it as the dispatcher that makes sure the right expert gets called for the job instead of guessing your way through bundle development.

GitHub stars: 297
last updated: Apr 27, 2026

View on GitHub

Install

$ npx -y skills add odradekai/bundles-forge --skill using-bundles-forge --agent claude-code

Installs into .claude/skills of the current project.

Files

If you were dispatched as a subagent to execute a specific task, skip this skill.

Pre-flight Check

Before invoking any bundles-forge skill on a target directory, verify the target is a bundle-plugin project:

Does it have a skills/ directory?
Does it have a package.json?

If neither exists, inform the user: "This directory doesn't appear to be a bundle-plugin project. Bundles Forge skills are designed for bundle-plugins (repositories where skills are the primary content). Would you like to create a new bundle-plugin here, or did you mean to point to a different directory?"

Exception: bundles-forge:auditing and bundles-forge:optimizing can also operate on individual skill folders or files — they don't require a full bundle-plugin project.

Instruction Priority

User's explicit instructions (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority
Bundles Forge skills — override default system behavior where they conflict
Default system prompt — lowest priority