Claude Project Forge

Production-ready Claude Code plugins for end-to-end software development. One command to forge complete projects with specialized AI agents, professional design systems, and battle-tested patterns.

Available Plugins

frontend-forge

Complete Next.js applications with a single command.

/frontend-forge:forge "SaaS dashboard with authentication" --theme=tech-innovation

One command orchestrates 8 specialized agents through 4 phases: architecture planning → design system generation → code implementation → build verification. Production-ready Next.js 15 apps in minutes.

Stack: Next.js 15, React 19, TypeScript, Tailwind v4, shadcn/ui Features: 10 professional themes, spec-driven development, parallel execution, anti-generic design

---

Coming Soon

• 🔨 backend-forge - FastAPI/Django APIs with authentication and databases
• 🔨 data-forge - ETL pipelines, analytics, and ML workflows
• 🔨 devops-forge - Docker, Kubernetes, CI/CD, and monitoring
• 🔨 mobile-forge - React Native and Flutter development

Installation

Via Marketplace (Recommended)

/plugin marketplace add https://github.com/VincentCourty/claude-project-forge
/plugin install frontend-forge

Manual Installation

cp -r plugins/frontend-forge/agents ~/.claude/agents/
cp -r plugins/frontend-forge/commands ~/.claude/commands/

Philosophy

"Forge" = craft with power and precision.

Each plugin provides:

• Opinionated - Best practices baked in, zero decision paralysis
• Production-ready - Battle-tested patterns, not experimental code
• Comprehensive - Everything for that domain, nothing more
• Composable - Plugins work together seamlessly

Plugin Architecture

Plugins can contain:

• Commands - Slash commands for workflows
• Agents - Specialized sub-agents with domain expertise
• Skills - Model-invoked capabilities (progressive disclosure)
• Hooks - Event handlers for automation
• MCP Servers - External tool integrations

Standard structure:

plugin-name/
├── .claude-plugin/
│   └── plugin.json          # Metadata (name, version, description)
├── commands/                 # Slash commands (optional)
├── agents/                   # Specialized agents (optional)
├── skills/                   # Progressive disclosure (optional)
├── hooks/                    # Event handlers (optional)
└── mcp-servers/             # External integrations (optional)

Quick Example

# Install
/plugin install frontend-forge

# Forge complete e-commerce platform
/frontend-forge:forge "Product marketplace with cart, checkout, and user accounts" --theme=sunset-boulevard

# Result: Complete Next.js app with:
# - All pages, components, API routes implemented
# - Distinctive design system applied
# - TypeScript strict mode passing
# - Production build verified
# - Ready for deployment

Creating Plugins

1. Initialize structure:

   mkdir -p plugins/your-plugin/.claude-plugin
   mkdir -p plugins/your-plugin/{agents,commands,skills,hooks}

2. Add manifest (plugins/your-plugin/.claude-plugin/plugin.json):

   {
     "name": "your-plugin",
     "version": "1.0.0",
     "description": "Your plugin description",
     "author": {"name": "Your Name"},
     "engines": {"claude-code": ">=1.0.0"}
   }

3. Add components (agents, commands, skills, hooks as needed)

4. Document in plugin README.md

5. Test locally before publishing

See individual plugin READMEs and CLAUDE.md for detailed guidelines.

Contributing

Contributions welcome!

1. Fork repository
2. Create plugin following structure above
3. Test thoroughly
4. Submit pull request with clear description

License

MIT

Resources

• Claude Code Documentation
• Plugin Development Guide
• Creating Agents
• Creating Commands

---

Forge your next project with precision and power.