moodforge

Orchestrate a seven-step design pipeline for Claude Code projects.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/om13rajpal/moodforge --skill moodforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moodforge
Source: https://github.com/om13rajpal/moodforge/tree/main
Command: npx skills add https://github.com/om13rajpal/moodforge --skill moodforge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Moodforge provides a self-contained, production-ready design pipeline that orchestrates a multi-step workflow for Claude Code projects. It ensures per-project state tracking, reusable design artifacts, and a guided path from discovery through handoff, so teams can move from vague briefs to shipped design systems with confidence.

Core Features & Use Cases

  • A seven-step workflow (Discovery → Screen Preview → Brand Kit → Animation Review → All Screens → Production) that guides designers from concept to handoff.
  • Localhost visual companion with per-project state so rejected directions never come back, with motion governance enforced by emil-design-eng and GSAP tooling.
  • Stepwise loading of sub-skills (e.g., pbakaus/impeccable, emilkowalski/skill, greensock/gsap-skills, shadcn/ui) to balance performance and capability, enabling scalable collaboration.

Quick Start

Run the moodforge CLI to start the seven-step design pipeline and watch the visual companion render in your browser.

Frequently Asked Questions about moodforge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a visual design pipeline from discovery to handoff in Claude Code?

A visual design pipeline orchestrator coordinates discovery, screen previews, brand kit creation, animation review, all-screens production, and handoff while tracking per-project state to prevent rejected directions from reappearing.

How does motion governance work with GSAP in a design pipeline?

Motion governance in a design pipeline enforces animation standards using GSAP tooling and emil-design-eng sub-skills, loading step-by-step to balance performance with advanced motion capabilities during the review phase.

Can I use shadcn/ui components within an automated design workflow?

Yes, shadcn/ui components are loaded stepwise as sub-skills during the design workflow, enabling scalable collaboration and component reuse while balancing processing speed and capability.

What is per-project state tracking for design systems and why is it needed?

Per-project state tracking records design decisions and rejected visual directions locally, ensuring that previously dismissed concepts never return and maintaining continuity across multi-step design workflows.

Does this design pipeline require any external dependencies or packages?

No external dependencies are required to start the design pipeline; it is self-contained and loads necessary sub-skills like GSAP tooling and shadcn/ui step-by-step as needed during execution.