| name | using-bundles-forge |
| description | Use when starting any conversation involving bundle-plugins — blueprinting, scaffolding, authoring, auditing, testing, optimizing, or releasing. Also use when feeling unsure which bundles-forge skill applies |
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
How to Access Skills
In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded — follow it directly.
In Cursor: Use the Skill tool.
In Gemini CLI: Skills activate via the activate_skill tool. See references/gemini-tools.md for tool mapping.
In Codex: Skills are discovered from . See for tool mapping.
