Stats
Actions
Available In
Tags
Plugin
forge
Meta-plugin that creates production-grade Claude Code plugins through a 4-phase pipeline: internet research, clarifying questions, architecture blueprint, and full code generation. Learns from every build to improve future plugin quality.
What's Inside
Agents5
forge-architect
/forge-architect
Plugin architecture designer for the Plugin Forge. Creates detailed blueprints including directory trees, data schemas, hook event maps, agent rosters, and skill inventories. Invoke after research is complete and user requirements are clarified. <example> user: Design the architecture for my logging plugin assistant: [delegates to forge-architect to create a complete blueprint] </example>
forge-generator
/forge-generator
Code generation engine for the Plugin Forge. Writes all plugin files based on approved blueprints: manifests, hooks, handlers, agents, skills, data schemas, bin tools, and install scripts. Invoke after a blueprint has been approved. <example> user: Generate the plugin based on the approved blueprint assistant: [delegates to forge-generator to write all files] </example>
forge-learner
/forge-learner
Pattern mining and learning specialist for the Plugin Forge. Analyzes build history, research cache, and validation results to extract reusable patterns and improve future plugin generation. Invoke when asked to review past builds or extract learnings. <example> user: What have we learned from past plugin builds? assistant: [delegates to forge-learner to mine patterns from build history] </example>
forge-researcher
/forge-researcher
Internet research specialist for the Plugin Forge. Searches the web, GitHub repos, plugin marketplaces, and documentation to find existing solutions, patterns, and best practices before building a new plugin. Invoke when starting a new plugin build or when the user asks to research a plugin concept. <example> user: I want to build a plugin for automated code review assistant: [delegates to forge-researcher to search for existing code review plugins] </example>
forge-validator
/forge-validator
Plugin structure and quality validator for the Plugin Forge. Checks that a generated plugin follows all Claude Code plugin conventions, has valid JSON and YAML, proper frontmatter, correct paths, and no common mistakes. Invoke after plugin generation or when asked to validate a plugin. <example> user: Validate the plugin I just created assistant: [delegates to forge-validator to check plugin structure and quality] </example>
Skills8
add-component
/add-component
Add a new component (hook, agent, skill, MCP server, bin tool, or output style) to an existing Claude Code plugin. Use when asked to extend, enhance, or add functionality to a plugin that already exists.
blueprint
/blueprint
Architecture blueprint phase for plugin creation. Designs the complete plugin structure including directory tree, data schemas, hook event map, agent roster, and skill inventory. Use after research and clarification phases are complete.
dashboard
/dashboard
View Plugin Forge build history, statistics, and system health. Use when asked about forge status, past builds, or plugin generation stats.
forge
/forge
Create a production-grade Claude Code plugin from scratch through a 4-phase pipeline: research, clarify, blueprint, generate. Use when asked to build, create, or scaffold a new Claude Code plugin. Automatically invoked when user says "create a plugin", "build a plugin", "scaffold a plugin", or "forge a plugin".
generate
/generate
Generation phase for plugin creation. Writes all plugin files based on an approved blueprint. Creates manifest, hooks, handlers, agents, skills, data schemas, bin tools, and install script. Use after blueprint approval.
Stats
Version1.0.1
LanguagePython
Stars1
MaintenanceGood
LicenseMIT
Last Commit
Added
Available In
Safety Signals
Caution
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
